Bitcoin Forum
February 21, 2019, 08:58:13 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: How many BottleCaps do you own?
None - 86 (39.8%)
1-1k - 29 (13.4%)
1k-10k - 27 (12.5%)
More than 10k - 74 (34.3%)
Total Voters: 216

Pages: « 1 ... 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 [122] 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 ... 218 »
  Print  
Author Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS  (Read 339600 times)
unick
Sr. Member
****
Offline Offline

Activity: 504
Merit: 254


View Profile
July 06, 2014, 04:27:02 PM
 #2421


EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.


  

I was asking in order to support my theory, were you about at 30 days of age, or more ?

Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur.

I guess the only other thing that needs confirming (I think I have seen this on the explorers already)
Is that stakes that should be receiving more than the cap are being pegged back to 1k and not ignored or rejected
obviously my blocks would have got significantly more than 1k but I am expecting 1k exactly per block

I've had a 5k block of exactly 46 day old, got 1000 CAP on the 4th. if there was no cap, I would of seen 1260 CAP.  if it had a bug, I wouldn' t have seen anything. so I can confirm everything runs smooth.

There is just this mid min/max range threshold before staking that bugs me

Awesome Explorers for Awesome Coins | Show some BTC love here: 1AAYAZgaz2me7hyumexUZzcyGRZEYtCx5C
HoboNickels: hbn.blockx.info | BottleCaps: cap.blockx.info | GrowthCoin: grw.blockx.info
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1550739493
Hero Member
*
Offline Offline

Posts: 1550739493

View Profile Personal Message (Offline)

Ignore
1550739493
Reply with quote  #2

1550739493
Report to moderator
PressF1
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
July 06, 2014, 04:46:41 PM
 #2422


EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.


  

I was asking in order to support my theory, were you about at 30 days of age, or more ?

Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur.

I guess the only other thing that needs confirming (I think I have seen this on the explorers already)
Is that stakes that should be receiving more than the cap are being pegged back to 1k and not ignored or rejected
obviously my blocks would have got significantly more than 1k but I am expecting 1k exactly per block

I've had a 5k block of exactly 46 day old, got 1000 CAP on the 4th. if there was no cap, I would of seen 1260 CAP.  if it had a bug, I wouldn' t have seen anything. so I can confirm everything runs smooth.

There is just this mid min/max range threshold before staking that bugs me

I have seen the 1000 max stake at work as well in the BC. So I guess that's fine. I looked more closely to my stakes and made more precise calculations and must come to the conclusion that my observed minimum is a little larger than earlier estimated: 35 days, never less.

HBN & CAP: F1PressF1PCxEyESGk6Fe1om1RfiHqX5gg
FlungSpun
Sr. Member
****
Offline Offline

Activity: 403
Merit: 251


View Profile
July 06, 2014, 05:14:42 PM
 #2423

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!

Cheesy


Your theory was bang on sir!
unick
Sr. Member
****
Offline Offline

Activity: 504
Merit: 254


View Profile
July 06, 2014, 07:29:18 PM
 #2424

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!

Cheesy


Your theory was bang on sir!

Excellent! Smiley

Hope Tranz reads this. I would love to hear is take on this Wink

Awesome Explorers for Awesome Coins | Show some BTC love here: 1AAYAZgaz2me7hyumexUZzcyGRZEYtCx5C
HoboNickels: hbn.blockx.info | BottleCaps: cap.blockx.info | GrowthCoin: grw.blockx.info
Ense04
Full Member
***
Offline Offline

Activity: 145
Merit: 100


View Profile
July 06, 2014, 07:49:53 PM
 #2425

I received mine as well. Smiley
ryanb
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000



View Profile
July 06, 2014, 08:04:41 PM
 #2426

my CAPS last stake was on 6/28/14 on the old fork.

It has been showing that my coins will  stake within an hour for the past 2 days.

How long do i have to wait for the stake?

https://bitcoinfundingteam.com/ref/SatoshiTeam
turn 0.1 BTC to 80BTC week after week!!!
FlungSpun
Sr. Member
****
Offline Offline

Activity: 403
Merit: 251


View Profile
July 06, 2014, 08:16:14 PM
 #2427

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!

Cheesy


Your theory was bang on sir!

Excellent! Smiley

Hope Tranz reads this. I would love to hear is take on this Wink

He should find it difficult to miss.


I received mine as well. Smiley

So understated, very civilised - go on, let yourself have a little woohoo 
GoldBit89
Hero Member
*****
Offline Offline

Activity: 526
Merit: 500


Its all about the Gold


View Profile
July 06, 2014, 08:19:15 PM
 #2428

I haven't staked yet either despite having held coins forever now.

db.log has this
Code:
Lock table is out of available lock entries

and debug.log has this:
Code:
 ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  received block 0ac317b1ecb264b379c1
  SetBestChain: new best=0ac317b1ecb264b379c1  height=527925  trust=2145786651908  date=  rocessBlock: ACCEPTED


for the db lock try this
https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114

for mempool error, restart the client. we had a big rollback on the 4th and your client still holds old transactions in memory.



my client has been restarted multiple times after the 4th and i am using latest 2.1 client and still have those mempool errors as well as these errors : ERROR: CTxMemPool::accept() : ConnectInputs failed 4e61361746
  ERROR: FetchInputs() : 60f3a93cdc mempool Tx prev not found c03c31f9d8
  stored orphan tx 60f3a93cdc (mapsz 2).

so restarting client does not fix this issue at all.

FTC  6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR  |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU
BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC  LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4
BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61  |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
raskul
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250



View Profile
July 06, 2014, 08:19:23 PM
 #2429

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!

Cheesy


Your theory was bang on sir!

Excellent! Smiley

Hope Tranz reads this. I would love to hear is take on this Wink

He should find it difficult to miss.


I received mine as well. Smiley

So understated, very civilised - go on, let yourself have a little woohoo 

that's like a block party but better  Grin

tips    1APp826DqjJBdsAeqpEstx6Q8hD4urac8a
Tranz
Legendary
*
Offline Offline

Activity: 1442
Merit: 1052


May the force bit with you.


View Profile
July 07, 2014, 12:27:09 AM
 #2430

Hi guys. I looked at the code a bit more and Unick was right on. Old blocks would still need to age 30 days. Newer blocks would begin staking at 15 days.  The discrepancy is with the getweightfromvalue function. It assumes after the fork all blocks that are 15 days min age. But the function that actually allows stakes, would only allow coins that were sent pre fork to start at 30 days. Coins sent to wallet, or staked after the fork should begin to get min age at 15 days.

I will keep a close eye on this to make sure.

Thanks everyone..

HBN: https://bitcointalk.org/index.php?topic=303749.0 hobonickels.info
Personal Donations: F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
Donations to the HBN Fund: EhbNfund4PrRFLHMxsnbGLhP25hizJGHEE or 1LVFtCX4a83dMLjd8S7imKKKC58QaG83kw
Tranz
Legendary
*
Offline Offline

Activity: 1442
Merit: 1052


May the force bit with you.


View Profile
July 07, 2014, 12:33:38 AM
 #2431

I haven't staked yet either despite having held coins forever now.

db.log has this
Code:
Lock table is out of available lock entries

and debug.log has this:
Code:
 ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  received block 0ac317b1ecb264b379c1
  SetBestChain: new best=0ac317b1ecb264b379c1  height=527925  trust=2145786651908  date=  rocessBlock: ACCEPTED


for the db lock try this
https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114

for mempool error, restart the client. we had a big rollback on the 4th and your client still holds old transactions in memory.



my client has been restarted multiple times after the 4th and i am using latest 2.1 client and still have those mempool errors as well as these errors : ERROR: CTxMemPool::accept() : ConnectInputs failed 4e61361746
  ERROR: FetchInputs() : 60f3a93cdc mempool Tx prev not found c03c31f9d8
  stored orphan tx 60f3a93cdc (mapsz 2).

so restarting client does not fix this issue at all.

If a restart doesn't help the mempool erros. You can try to restart the client with -rescan.

You can also try -salvagewallet, this is much more aggressive so please be sure you have a wallet backup and your addressed exported before attempting it.

The other errors regarding FetchInputs, are more normal errors. I get them on all clients, but they do seem to be more prevalent right now with CAPs. As more people get on the right chain and get their clients cleaned up, they should begin to diminish.

HBN: https://bitcointalk.org/index.php?topic=303749.0 hobonickels.info
Personal Donations: F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
Donations to the HBN Fund: EhbNfund4PrRFLHMxsnbGLhP25hizJGHEE or 1LVFtCX4a83dMLjd8S7imKKKC58QaG83kw
raskul
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250



View Profile
July 07, 2014, 04:02:22 AM
 #2432

http://www.thescribe.eu/portfolio/ZIM_XXX_HYP.rar

in case you didn't see HYPE

tips    1APp826DqjJBdsAeqpEstx6Q8hD4urac8a
GoldBit89
Hero Member
*****
Offline Offline

Activity: 526
Merit: 500


Its all about the Gold


View Profile
July 08, 2014, 03:21:27 AM
 #2433

maybe a oddity:

07/08/14 01:04:08 out 1.955578
07/08/14 01:04:08 trying connection 46.164.247.229:7685 lastseen=5.5hrs
07/08/14 01:04:08 AddToWallet dcd74bab3a  new
07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
07/08/14 01:04:08 NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
07/08/14 01:04:08 updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
07/08/14 01:04:08 NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

FTC  6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR  |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU
BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC  LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4
BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61  |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
unick
Sr. Member
****
Offline Offline

Activity: 504
Merit: 254


View Profile
July 08, 2014, 03:58:57 AM
 #2434

maybe a oddity:

07/08/14 01:04:08 out 1.955578
07/08/14 01:04:08 trying connection 46.164.247.229:7685 lastseen=5.5hrs
07/08/14 01:04:08 AddToWallet dcd74bab3a  new
07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
07/08/14 01:04:08 NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
07/08/14 01:04:08 updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
07/08/14 01:04:08 NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

Awesome Explorers for Awesome Coins | Show some BTC love here: 1AAYAZgaz2me7hyumexUZzcyGRZEYtCx5C
HoboNickels: hbn.blockx.info | BottleCaps: cap.blockx.info | GrowthCoin: grw.blockx.info
raskul
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250



View Profile
July 08, 2014, 01:15:15 PM
 #2435

central caverns facebook page updated  Grin please mine your Bottlecaps with us
Website|http://www.centralcavern.uk
NOMP|http://eu.centralcavern.uk:8080
Facebook|https://www.facebook.com/coincount?ref=tn_tnmn
Forum Thread|https://bitcointalk.org/index.php?topic=676478.msg7661479#msg7661479
Bottlecaps|http://cap.centralcavern.uk/index.php?page=dashboard
HoboNickels|http://hbn.centralcavern.uk/index.php?page=dashboard
BTC P2Pool (Amsterdam)|http://eu.centralcavern.uk:9332/static/
VTC P2Pool (Amsterdam)|http://eu.centralcavern.uk:9171

tips    1APp826DqjJBdsAeqpEstx6Q8hD4urac8a
GoldBit89
Hero Member
*****
Offline Offline

Activity: 526
Merit: 500


Its all about the Gold


View Profile
July 09, 2014, 12:23:25 AM
 #2436

maybe a oddity:

  out 1.955578
  trying connection 46.164.247.285 lastseen=5.5hrs
 ddToWallet dcd74bab3a  new
  WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
  NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
  updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
  NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"  WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

Meaning this is just a display overlook in the debug section? Or is it a client wide internal overlook (meaning i thought that the debug section was just that a debug of the whole client and more)?

FTC  6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR  |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU
BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC  LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4
BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61  |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
Tranz
Legendary
*
Offline Offline

Activity: 1442
Merit: 1052


May the force bit with you.


View Profile
July 09, 2014, 12:44:28 AM
 #2437

maybe a oddity:

  out 1.955578
  trying connection 46.164.247.285 lastseen=5.5hrs
 ddToWallet dcd74bab3a  new
  WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
  NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
  updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
  NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"  WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

Meaning this is just a display overlook in the debug section? Or is it a client wide internal overlook (meaning i thought that the debug section was just that a debug of the whole client and more)?

Just 2 lines of code.

And now it is updated!  Cheesy

https://github.com/Tranz5/bottlecaps/commit/06b92fd3e7de615c930d5781a70b9ff70bacb406

HBN: https://bitcointalk.org/index.php?topic=303749.0 hobonickels.info
Personal Donations: F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
Donations to the HBN Fund: EhbNfund4PrRFLHMxsnbGLhP25hizJGHEE or 1LVFtCX4a83dMLjd8S7imKKKC58QaG83kw
Tranz
Legendary
*
Offline Offline

Activity: 1442
Merit: 1052


May the force bit with you.


View Profile
July 09, 2014, 01:03:34 AM
 #2438



Yep. Confirming v2.1 works for me.  Thanks for all your work on this Tranz.  I see a lot of improvements since v1.52.

The only issue I'd like to report is a highlighted message at the top of the Overview page stating that "Info: Minting suspended due to locked wallet" when in fact the wallet is unlocked and staking.



Thanks I actually meant to remove that, as we now have the staking icon.

Removed this message.
https://github.com/Tranz5/bottlecaps/commit/3cd7486ddc2df829583b01671b76f26bc667b314

HBN: https://bitcointalk.org/index.php?topic=303749.0 hobonickels.info
Personal Donations: F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
Donations to the HBN Fund: EhbNfund4PrRFLHMxsnbGLhP25hizJGHEE or 1LVFtCX4a83dMLjd8S7imKKKC58QaG83kw
GoldBit89
Hero Member
*****
Offline Offline

Activity: 526
Merit: 500


Its all about the Gold


View Profile
July 09, 2014, 01:06:27 AM
 #2439

maybe a oddity:

  out 1.955578
  trying connection 46.164.247.285 lastseen=5.5hrs
 ddToWallet dcd74bab3a  new
  WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
  NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
  updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
  NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"  WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

Meaning this is just a display overlook in the debug section? Or is it a client wide internal overlook (meaning i thought that the debug section was just that a debug of the whole client and more)?

Just 2 lines of code.

And now it is updated!  Cheesy

https://github.com/Tranz5/bottlecaps/commit/06b92fd3e7de615c930d5781a70b9ff70bacb406

You rock  Tranz !! Keep up the great work. Thank you.

FTC  6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR  |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU
BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC  LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4
BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61  |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
raskul
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250



View Profile
July 09, 2014, 01:19:56 AM
 #2440

only paying bounties to bottlecaps miners
https://bitcointalk.org/index.php?topic=676478.msg7661479#msg7661479

tips    1APp826DqjJBdsAeqpEstx6Q8hD4urac8a
Pages: « 1 ... 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 [122] 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 ... 218 »
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!