One of the chains went sour at 0:00 hours... at block 64751
Killed the old chain...
Redownload the new chain and continue mining... New block-height should be around 65032+
Backup the old chain, if you believe that the new chain may be incorrect. Though, I do not see any issues with it, at the moment. Just looks like the old chain crapped-out when time rolled-over to midnight, and a new client starting after 0:00 hours began building a chain that actually functions. (Didn't contain the 0:00 failed block.)
Honestly looks like an issue with "Division by zero"... or checkpoint and that roll-over time... Might want to hard-code any block at exactly 0:00:00 hours, to fail, even if it is "valid"... taking the next block after 0:00:00 hours. That, or purposely add 0:00:01 to all blocks less than 23:59:99 in the future, so there is never a division by 0 occurrence. That would cause the block just before midnight to fail, but would remove a check for "zero" on every call... (Just guessing here. it was a block at exactly 0:00:00 though, I was the one who found that block. It is not on the new chain.)
Also note, 50729 block and 52190, and 56526, and 57080, and 57662, or one +/- those blocks, seemed to be giving the chain a little "confusion"... Kept stopping at those blocks, loading the new chain... had to wait forever for those blocks to load. (Could a few of those "reliable connections" be "stuck" and they just don't realize they are stuck? Like my wallet was just happy doing nothing, not reporting an "issue", thinking it was "all OK"... But my cgminers all reported "work not coming fast enough". Which is how I knew the wallet was "acting up"... lol, that, and they seemed to cut me off from the network after an hour.)
Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 191. (Read 388610 times)
August 08, 2013, 03:29:01 AM
August 08, 2013, 03:23:23 AM
Seems my wallet and Cryptsy are not on the same connection either.. lost a few coins.. never got there.
August 08, 2013, 03:14:10 AM
bump ^^^^^
August 08, 2013, 01:09:01 AM
- ATTENTION -
My wallet and epools are in the same fork , verns pool and coinchoose in another
My wallet and epools are in the same fork , verns pool and coinchoose in another
August 07, 2013, 07:24:26 PM
Great coin, cant wait till its worth at least 0.0007 again!!!
It's headed that way again... even with BTC rise... (The more BTC rises, the less we have to sell, to get the same $ ammt. Thus, for those who can spare it, they can settle for less. Still, it will easily climb back over to 0.0015, when the suckers are done mining the new scam-coins, thinking they are going to "get in on the early value"... The new coins all die down fast, and settle-in quick. Doesn't take long for people to realize they are only getting a fraction of the estimated returns, due to orphans and rejections from fast solutions. But it does take some time before they realize it.)
Someone sell toilet-paper and "zombie survival kits", and coffee for CAP, and I will buy them...
Bottlecaps: The only way to survive in the digital apocalypse, is with the right tools. The toilet-paper is rough, the coffee tastes like dirt, but without the "zombie survival kit", you won't be able to wipe the shit off you ass, or stay awake all night, if you ever get attacked by zombies that ate your brains!
A nigga be hanging out in the glow , that's what be happening !
Get your ass back to the hub , also you be needing some radaway.
I dont really foresee zombies being a huge problem in the future .
You are starting to sound like Anonymint { jokes , waiting for Anony Now to find this comment while furiously searching his own name and claim that I'm an NSA counter agent that is planting ideas about our certain Cap currency future. }
August 06, 2013, 11:23:08 PM
Great coin, cant wait till its worth at least 0.0007 again!!!
It's headed that way again... even with BTC rise... (The more BTC rises, the less we have to sell, to get the same $ ammt. Thus, for those who can spare it, they can settle for less. Still, it will easily climb back over to 0.0015, when the suckers are done mining the new scam-coins, thinking they are going to "get in on the early value"... The new coins all die down fast, and settle-in quick. Doesn't take long for people to realize they are only getting a fraction of the estimated returns, due to orphans and rejections from fast solutions. But it does take some time before they realize it.)
Someone sell toilet-paper and "zombie survival kits", and coffee for CAP, and I will buy them...
Bottlecaps: The only way to survive in the digital apocalypse, is with the right tools. The toilet-paper is rough, the coffee tastes like dirt, but without the "zombie survival kit", you won't be able to wipe the shit off you ass, or stay awake all night, if you ever get attacked by zombies that ate your brains!
August 06, 2013, 05:47:43 PM
Great coin, cant wait till its worth at least 0.0007 again!!!
August 06, 2013, 04:59:27 PM
Anyone know what happened to all the pools??? Or is Bottlecaps now switched to just PoS minting?
You can mine CAP at multipool.
Hey Devs, would it be possible for you to merge in the NVC getmhashps function under the getmininginfo method? Or would that not work with your diff adjustment?
Yep it will be included. Just holding off on 1.4.1 for a little longer to get nodes cleared up. Dont want to introduce another change we are sure all is well. I also have had a busy week at work. Im trying to fix a bug bitcoinfx mentioned and will have a newly compiled client soon but not a necessary upgrade
August 06, 2013, 04:56:39 PM
Anyone know what happened to all the pools??? Or is Bottlecaps now switched to just PoS minting?
No pools are up still. PoW minting will be active for 9 years,
Multipool.in , cap.epools.org, bottlecapspool.com are all good choices
August 06, 2013, 04:51:05 PM
Anyone know what happened to all the pools??? Or is Bottlecaps now switched to just PoS minting?
You can mine CAP at multipool.
Hey Devs, would it be possible for you to merge in the NVC getmhashps function under the getmininginfo method? Or would that not work with your diff adjustment?
August 06, 2013, 12:40:30 PM
Anyone know what happened to all the pools??? Or is Bottlecaps now switched to just PoS minting?
August 06, 2013, 12:41:48 AM
So is v1.4.0.0-g32a928e-caps still the latest version and considered stable?
Yes any issues?
August 05, 2013, 11:44:02 PM
That is the one I am using, and it runs fine...
I think 1.4.1 was just going to tackle POS things, now that we are minting POS blocks.
Have not hit a sour spot yet.
I think 1.4.1 was just going to tackle POS things, now that we are minting POS blocks.
Have not hit a sour spot yet.
August 05, 2013, 01:27:41 PM
So is v1.4.0.0-g32a928e-caps still the latest version and considered stable?
August 04, 2013, 11:54:45 PM
Ok, seems to have started again... (Still odd that it seemed to have stopped. Was that like the diff-adj stopping it from releasing too many POS coins in x-days or something?)
60935
60880
60873
60784
60781
60768
60692
60448
These are the latest POS blocks... Big jump from 58088 to 60448, just over 2000 blocks without a POS. (There was a lot of POS just prior, so maybe the system did just make an adjustment, if it didn't break, or hit a sour spot.)
I wish the block explorer would identify the POS vs POW blocks... instead of showing useless info like CAP (Obviously, we know we are looking at CAP. lol.)
Bold it, or highlight it, or create a separate POS explorer that only shows POS blocks.
Talk about bad luck... lol, they keep missing me by two blocks!
60935
60880
60873
60784
60781
60768
60692
60448
These are the latest POS blocks... Big jump from 58088 to 60448, just over 2000 blocks without a POS. (There was a lot of POS just prior, so maybe the system did just make an adjustment, if it didn't break, or hit a sour spot.)
I wish the block explorer would identify the POS vs POW blocks... instead of showing useless info like CAP (Obviously, we know we are looking at CAP. lol.)
Bold it, or highlight it, or create a separate POS explorer that only shows POS blocks.
Talk about bad luck... lol, they keep missing me by two blocks!
August 04, 2013, 11:48:29 PM
45251 oops... lol.. told you my eyes were getting tired... 
But the other one, with 9.999 should still have been 10... is everyone sending 10-coin transactions? Oh, I get it... there was only 9.999 available for stake, because 0.001 was lost as a fee from that block... That was the amount which got staked 9.999 but resulted in 0 gain... (The 0.001 was in another person's possession.)
Like the others I see 10.01 were obviously 20 coins available for stake, so they gained 0.01 from the 20 staked coins, thus 10 = 10.01 after the reward. (10 for the block + 0.01 for the stake-reward)
Any word as to why the staked coins POS stopped after block 58088?
But the other one, with 9.999 should still have been 10... is everyone sending 10-coin transactions? Oh, I get it... there was only 9.999 available for stake, because 0.001 was lost as a fee from that block... That was the amount which got staked 9.999 but resulted in 0 gain... (The 0.001 was in another person's possession.)
Like the others I see 10.01 were obviously 20 coins available for stake, so they gained 0.01 from the 20 staked coins, thus 10 = 10.01 after the reward. (10 for the block + 0.01 for the stake-reward)
Any word as to why the staked coins POS stopped after block 58088?
August 04, 2013, 09:35:04 PM
Updated the list...
POS seems broken... perhaps the last running POS wallet that was working, was the one on that fork... After they got back on the correct chain, that made 100% of the broken code for POS now running? (It seems)
After that block 58088, there have been no more POS blocks. Before that, there was about 10 blocks per 1000 blocks. (Roughly 1% were being produced 1:100)... Now none are being produced. The only connection I see, is that one old program which was still running, on the fork, which is now gone. Leaving us, with all the updated and possibly broken POS code, still running.
Unless, the diff for POS has changed to match normal block diffs... then I would have to manually search every block, one by one, to find the POS blocks. (In previous searches, all POS blocks have shown as diff-0.003)
If it is broken... could it be that the calculation, for some reason, thinks the "update date", is 0-days, and will not start working again until 30 days from the update, before it begins producing POS blocks?
That is the only "glitch" I can think of, which would result in a complete stopping of POS blocks, unless POS was just disabled after that date... or, the "variable" used had a max value of 65536, which is close to 58088... close enough that a calculation for "next after 58088..." in a formula that multiplies that by something, might fail... resulting in something like a rolled-over value of 232 for a next POS, which should have been (58088 + 232 = 58320) after the formula summed-up, but resulted in just 232, which was already done, and thus, would fail block-height by nonce... or something like that.
Has POS been disabled until 1.4.1?
I also found it odd that the block-reward for these two blocks was below 10... they were POS blocks...
45455, 9.999
45252, 3.666
The totals should have been at-least 10... right?
POS seems broken... perhaps the last running POS wallet that was working, was the one on that fork... After they got back on the correct chain, that made 100% of the broken code for POS now running? (It seems)
After that block 58088, there have been no more POS blocks. Before that, there was about 10 blocks per 1000 blocks. (Roughly 1% were being produced 1:100)... Now none are being produced. The only connection I see, is that one old program which was still running, on the fork, which is now gone. Leaving us, with all the updated and possibly broken POS code, still running.
Unless, the diff for POS has changed to match normal block diffs... then I would have to manually search every block, one by one, to find the POS blocks. (In previous searches, all POS blocks have shown as diff-0.003)
If it is broken... could it be that the calculation, for some reason, thinks the "update date", is 0-days, and will not start working again until 30 days from the update, before it begins producing POS blocks?
That is the only "glitch" I can think of, which would result in a complete stopping of POS blocks, unless POS was just disabled after that date... or, the "variable" used had a max value of 65536, which is close to 58088... close enough that a calculation for "next after 58088..." in a formula that multiplies that by something, might fail... resulting in something like a rolled-over value of 232 for a next POS, which should have been (58088 + 232 = 58320) after the formula summed-up, but resulted in just 232, which was already done, and thus, would fail block-height by nonce... or something like that.
Has POS been disabled until 1.4.1?
I also found it odd that the block-reward for these two blocks was below 10... they were POS blocks...
45455, 9.999
45252, 3.666
The totals should have been at-least 10... right?
block 45252 is a normal block with difficulty of 3.666 and reward of 10:
http://bot.webboise.com:2760/block/000000000ee711f81bf5f70cc7b93003f18bd78da89a17f9146e3e33568eae0e
block 45455 is a POS block with 2 transactions attached to it with total value of 9.999
http://bot.webboise.com:2760/block/59fdf92f0bc28a6650c4cc9e8a1fe530f71b06701cf44bb764d19ee8ca950dad
August 04, 2013, 08:56:05 PM
Updated the list...
POS seems broken... perhaps the last running POS wallet that was working, was the one on that fork... After they got back on the correct chain, that made 100% of the broken code for POS now running? (It seems)
After that block 58088, there have been no more POS blocks. Before that, there was about 10 blocks per 1000 blocks. (Roughly 1% were being produced 1:100)... Now none are being produced. The only connection I see, is that one old program which was still running, on the fork, which is now gone. Leaving us, with all the updated and possibly broken POS code, still running.
Unless, the diff for POS has changed to match normal block diffs... then I would have to manually search every block, one by one, to find the POS blocks. (In previous searches, all POS blocks have shown as diff-0.003)
If it is broken... could it be that the calculation, for some reason, thinks the "update date", is 0-days, and will not start working again until 30 days from the update, before it begins producing POS blocks?
That is the only "glitch" I can think of, which would result in a complete stopping of POS blocks, unless POS was just disabled after that date... or, the "variable" used had a max value of 65536, which is close to 58088... close enough that a calculation for "next after 58088..." in a formula that multiplies that by something, might fail... resulting in something like a rolled-over value of 232 for a next POS, which should have been (58088 + 232 = 58320) after the formula summed-up, but resulted in just 232, which was already done, and thus, would fail block-height by nonce... or something like that.
Has POS been disabled until 1.4.1?
I also found it odd that the block-reward for these two blocks was below 10... they were POS blocks...
45455, 9.999
45252, 3.666
The totals should have been at-least 10... right?
POS seems broken... perhaps the last running POS wallet that was working, was the one on that fork... After they got back on the correct chain, that made 100% of the broken code for POS now running? (It seems)
After that block 58088, there have been no more POS blocks. Before that, there was about 10 blocks per 1000 blocks. (Roughly 1% were being produced 1:100)... Now none are being produced. The only connection I see, is that one old program which was still running, on the fork, which is now gone. Leaving us, with all the updated and possibly broken POS code, still running.
Unless, the diff for POS has changed to match normal block diffs... then I would have to manually search every block, one by one, to find the POS blocks. (In previous searches, all POS blocks have shown as diff-0.003)
If it is broken... could it be that the calculation, for some reason, thinks the "update date", is 0-days, and will not start working again until 30 days from the update, before it begins producing POS blocks?
That is the only "glitch" I can think of, which would result in a complete stopping of POS blocks, unless POS was just disabled after that date... or, the "variable" used had a max value of 65536, which is close to 58088... close enough that a calculation for "next after 58088..." in a formula that multiplies that by something, might fail... resulting in something like a rolled-over value of 232 for a next POS, which should have been (58088 + 232 = 58320) after the formula summed-up, but resulted in just 232, which was already done, and thus, would fail block-height by nonce... or something like that.
Has POS been disabled until 1.4.1?
I also found it odd that the block-reward for these two blocks was below 10... they were POS blocks...
45455, 9.999
45252, 3.666
The totals should have been at-least 10... right?
August 04, 2013, 04:02:39 AM
Seems all are 10 reward blocks, split into 5 and 5... 
Here is what I got so far... From the block-explorer... These are the POS blocks I found, diff 0.003 blocks.
None from 60432 to 58089 (Odd) Did it break?
58088, 10.1 (Last POS block I saw)
57977, 10
57780, 9007.448
57681, 10
57677, 10.01
57663, 10
57575, 329.171184
57573, 801.809569
57503, 10
57487, 58.450854
57414, 19.999
57399, 10
57366, 1.41346
57292, 10.01
57081, 37.569746
56760, 10
56734, 10.01
56706, 10.01
56628, 10
56589, 10
56579, 10
56528, 10.151756
56527, 114.495749
55447, 10
55375, 10.01
55286, 10
55173, 10
55042, 10
55025, 12.820391
54760, 10
54596, 10
54467, 10
54411, 182.72393
54115, 19.999
54041, 110.859239
53798, 10
53780, 10
53666, 10
53658, 10
53517, 3541.617183
53434, 10
53395, 10
53036, 10
53018, 10
53002, 26.578504
52727, 10
52721, 23.558961
52685, 10
52533, 17.217816
52490, 10
52401, 10
52296, 10
52191, 10
51866, 24.088814
51746, 10
MISSING (Stopped, eyes tired)
46065, 143.061964
45873, 19.398142
45455, 9.999
45252, 3.666
Might have been more below...
NOTE: Amounts in blocks are for the actual "block transaction", not the reward...
Here is what I got so far... From the block-explorer... These are the POS blocks I found, diff 0.003 blocks.
None from 60432 to 58089 (Odd)
Did it break?58088, 10.1 (Last POS block I saw)
57977, 10
57780, 9007.448
57681, 10
57677, 10.01
57663, 10
57575, 329.171184
57573, 801.809569
57503, 10
57487, 58.450854
57414, 19.999
57399, 10
57366, 1.41346
57292, 10.01
57081, 37.569746
56760, 10
56734, 10.01
56706, 10.01
56628, 10
56589, 10
56579, 10
56528, 10.151756
56527, 114.495749
55447, 10
55375, 10.01
55286, 10
55173, 10
55042, 10
55025, 12.820391
54760, 10
54596, 10
54467, 10
54411, 182.72393
54115, 19.999
54041, 110.859239
53798, 10
53780, 10
53666, 10
53658, 10
53517, 3541.617183
53434, 10
53395, 10
53036, 10
53018, 10
53002, 26.578504
52727, 10
52721, 23.558961
52685, 10
52533, 17.217816
52490, 10
52401, 10
52296, 10
52191, 10
51866, 24.088814
51746, 10
MISSING (Stopped, eyes tired)
46065, 143.061964
45873, 19.398142
45455, 9.999
45252, 3.666
Might have been more below...
NOTE: Amounts in blocks are for the actual "block transaction", not the reward...
August 04, 2013, 03:55:05 AM
I am glad that this coin was able to get back on track so fast...
Now I just wish the POS coins would be more rewarding and less difficult to find/create...
Three days in to "available", and not one single POS block. Not sure what the deal was with the POS being 0 on that one guys find... You would think that at-least it would be the minimum value... 0% of 0 is 0... Hard to get 5% interest on 0, and 5% of 1 coin would have been 0.05 coins... 5% of one block of 10 coins would have been 0.5... Though it did say something about reward showing in the next block... I assume the next POS block, which seems like it might take months to find just one block! (But it says 0 staked coins, so I am still lost.)
Do I have to "not be mining" in order to "be minting"....
I realize that it was said, "you do not have to be mining to mint a POS block"... but was that actually translated into, "you CAN NOT be MINING to MINT a POS block"?
Because I really don't want to stop mining... but if not mining is what creates minted POS blocks... Then I will open up my wallet on a hundred computers and not mine on all of them... lol... That should give me 100 chances, right?
Now I just wish the POS coins would be more rewarding and less difficult to find/create...
Three days in to "available", and not one single POS block. Not sure what the deal was with the POS being 0 on that one guys find... You would think that at-least it would be the minimum value... 0% of 0 is 0... Hard to get 5% interest on 0, and 5% of 1 coin would have been 0.05 coins... 5% of one block of 10 coins would have been 0.5... Though it did say something about reward showing in the next block... I assume the next POS block, which seems like it might take months to find just one block! (But it says 0 staked coins, so I am still lost.)
Do I have to "not be mining" in order to "be minting"....
I realize that it was said, "you do not have to be mining to mint a POS block"... but was that actually translated into, "you CAN NOT be MINING to MINT a POS block"?
Because I really don't want to stop mining... but if not mining is what creates minted POS blocks... Then I will open up my wallet on a hundred computers and not mine on all of them... lol... That should give me 100 chances, right?
As far as I am aware, any POS award under 1 will be rounded to 0. POS must earn at least 1 coin to be awarded anything. So if you POS 10 coins you'll be minting 0.5, but that will round down to 0. If you did 100 you'll have 5. Can anyone confirm/correct this?
Jump to: