Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS

[Armchair Miner]

I performed a clean install of this client v1.3 for Windows. I needed to manually add nodes to begin synching, but once completed, get the error message, "WARNING: Checkpoint is too old. Contact the development team."

I had the same problem. One of the added nodes was the cause of that problem. The problem node has been deleted from the original post and the following currently works:

addnode=186.95.162.209
addnode=70.79.24.157
addnode=70.98.114.229
addnode=188.165.211.65
addnode=199.192.205.46
addnode=176.34.210.88
addnode=70.69.238.84
addnode=70.98.114.237

Good to know. I was not at my pc to verify.

It looks like the node removed was:
addnode=69.85.86.195


I removed this from the .conf file, restarted the client, but the error message was still there. I'll wait for the next version. Everything else seems to work well.

I deleted all except for the wallet and my .conf file (c/w with the revised addnodes) and re-downloaded the blockchain to correct the problem. I was able to re-create the problem on several different computers and cure it.

Okay, I deleted all files except wallet and conf and downloaded the entire blockchain again. I can assure you the problem is still there. I verified again that every ip in addnode is correct. If a new client is released and this is mentioned as a fix and some people still have problems, it's not gonna look good.  Running on Windows XP, virtual mode on Win7, client v1.3.

The only other thing I can think of is that I downloaded the associated dll's from one link, but since the client was not there, I downloaded that from the other link. I don't know if the issue could be in the DLL's, but in that case the update should probably be fine.

I got the same problem, couldn't sync the blockchain with the CAP client, got same WARNING in the bottom left box, followed directions by removing blockchain and redownloading it. Alas, now the CAPs in the wallet are showing unconfirmed, and the same WARNING persists. The next step is to notify the developers, it says. So there.

[Armchair Miner]

...continued

Created bottlecaps.conf file in the ...\Roaming\BottleCaps directory with this content:

addnode=186.95.162.209
addnode=70.79.24.157
addnode=70.98.114.229
addnode=188.165.211.65
addnode=199.192.205.46
addnode=176.34.210.88
addnode=70.69.238.84
addnode=70.98.114.237

restarted CAP client

and the CAP in the wallet now show confirmed. As well as new CAPs came in, also confirmed.

The only problem left, the checkpoint WARNING still persists.

[Damnsammit]

Been mining other stuff lately...

What's the deal with the client?  I haven't updated yet.  Should I?

[butjust41day]

No worries about the client. Apparently it just needs updating on a regular basis (with new checkpoints) to maximize security until the network gets more established. A new client will be released soon. The current client works just fine with the warning. we'll just see that warning every now and again as time goes on.

[BitJohn]

Hey  I have to say the transaction may have gone though ....

I'm blowing my own whistle here guys but Nibble is about the release one of the most stable clients currently out there

https://bitcointalk.org/index.php?topic=216637.0

Team digitalindustry nearly took Nibble PoS , I'm glad we did not bloat the client and , we are using an ultra low fee structure .

Feel free to come download have a look , we intend to show you how effective management can provide security and all that the end user wants .

A rising price and security , PoS provides no security against someone with no "stake motive" , the biggest threat to an active Cryptocurrency team is not stakeholders , but  Government agencies of course , that work directly for commercial fiat banking interests ,  none of this is addressed by PoS , and look at the fee structure , and client bloat ?

The user wants a Secure cryptocurrency with an efficient client , low fees , that is now/soon Nibble .

The time to be fixing this stuff is now, when if attacked we can roll back the BC , we know any attacker now  has not " stake motive " .

Proof of stake is a bonus in defending the currency there was no attack on bottlecaps. Not sure why your posting nibble in other coin threads. Proof of Stake is the safest bet for any alt. The other big question it answers is what happens when all the coins are mined.....On that note Bitcoin will not have the issue as I believe the fees would support it as the tech to mine Bitcoin will improve and the money behind it will keep it going probably true with a couple other PoW coins as well. But for smaller alts proof of stake is the way to go. How does Nibble answer this question? How is Nibble more secure?

[flound1129]

Hi can you please add multipool to the pool list:

https://www.multipool.in 0% fee pplns

Thanks!

[John Eden]

Looking into issues now. Will update when i have all the info. Chain is back on track form what i can see

[eBit]

Is anyone else having difficulty with payouts from www.bottlecapspool.com?
I should have had 5 payouts from the site, but only 2 are actually showing up on the blockchain:

1089864   2013-07-26 09:44:34   Don_Fee          -0.10000000
1089864   2013-07-26 09:44:34   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.12082583

1079121   2013-07-26 06:59:27   Don_Fee          -0.10000000
1079121   2013-07-26 06:59:27   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.07787684

1067868   2013-07-26 04:26:41   Don_Fee          -0.10000000
1067868   2013-07-26 04:26:41   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.03213076

1054597   2013-07-25 17:42:28   Don_Fee          -0.10000000
1054597   2013-07-25 17:42:28   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.92989879

1043043   2013-07-25 10:08:30   Don_Fee          -0.10000000
1043043   2013-07-25 10:08:30   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.9567508

http://bot.webboise.com:2760/address/F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5

It appears that the bottom two went through without any issues, but the top three are MIA.

I didn't have any issues with payouts from that pool, but stopped mining there yesterday. My results there were horrendous. I started tracking the results per hour and was getting about 68% of the coins I should have been receiving according to their stats.

I just tried to login to the pool now to double check my transaction history, but the site seems down. I've had no problem with any transactions going through from any point to point anywhere on the network, and confirmations are really fast. Everything has been flawless for me concerning transactions.

[BitJohn]

Is anyone else having difficulty with payouts from www.bottlecapspool.com?
I should have had 5 payouts from the site, but only 2 are actually showing up on the blockchain:

1089864   2013-07-26 09:44:34   Don_Fee          -0.10000000
1089864   2013-07-26 09:44:34   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.12082583

1079121   2013-07-26 06:59:27   Don_Fee          -0.10000000
1079121   2013-07-26 06:59:27   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.07787684

1067868   2013-07-26 04:26:41   Don_Fee          -0.10000000
1067868   2013-07-26 04:26:41   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.03213076

1054597   2013-07-25 17:42:28   Don_Fee          -0.10000000
1054597   2013-07-25 17:42:28   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.92989879

1043043   2013-07-25 10:08:30   Don_Fee          -0.10000000
1043043   2013-07-25 10:08:30   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.9567508

http://bot.webboise.com:2760/address/F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5

It appears that the bottom two went through without any issues, but the top three are MIA.

I didn't have any issues with payouts from that pool, but stopped mining there yesterday. My results there were horrendous. I started tracking the results per hour and was getting about 68% of the coins I should have been receiving according to their stats.

I just tried to login to the pool now to double check my transaction history, but the site seems down. I've had no problem with any transactions going through from any point to point anywhere on the network, and confirmations are really fast. Everything has been flawless for me concerning transactions.

BigVern's Wallet for bottlecaps pool got corrupted should be fixed now. The weird blip was due to 90% of the hashrate popping off at one time. Lets spread the wealth to some of the other pools as well. Silverwolf, Eurdook, Multipool all run some great stuff try em out.

[eBit]

Looking into issues now. Will update when i have all the info. Chain is back on track form what i can see

That does not sound good. Rather than making some fancy client skins, I would rather see the devs focus on client security and network monitoring tools first.

[digitalindustry]

I understand and am empathetic to the general direction in which you speak John ,.

I apologize for bringing up nibble I don't see nibble and Cap currency as competitors I guess , so in that sense I didn't see it as a problem , I have a stake in both and want to see both succeed.

To answer all your questions I would say , as a management direction I think it's better to be now focused , and build on that step by step , if we can't get the basics right , right now there is no point at looking far into the future .

So I'm saying in a growth phase I'd look after stakeholders number one , with low to zero fees solid simplicity , etc, then on top of this , we can all find solutions , this whole community .

Without a community though , there is no need for solutions.

I think my transaction went though , I'm wondering if verns wallet gotta  blkindex.dat error like mine ?

I'm still on board with cap currency , and want to support .

[digitalindustry]

Looking into issues now. Will update when i have all the info. Chain is back on track form what i can see

That does not sound good. Rather than making some fancy client skins, I would rather see the devs focus on client security and network monitoring tools first.

^^^^

That John .

[Damnsammit]

Yeah I can't get the new client to work.

No more mining for me!  Just wasted 24 hours.

[John Eden]

Looking into issues now. Will update when i have all the info. Chain is back on track form what i can see

That does not sound good. Rather than making some fancy client skins, I would rather see the devs focus on client security and network monitoring tools first.

I understand your concern 100%. In fact for the skinnable wallet we are looking to hire outside. Network functionality and security are our #1 goal and I have been working on nothing else until any issues are resolved.

We can assure you chain is back on track and moving ahead smoothly. If you are having Issues syncing your client Re downloading the blockchain should resolve the issue.

This does not appear to be an attack of any sort but may have been caused or exaggerated by 90% of the network hashrate disappearing when verns pool went down. We had a slight dip in coin generation due to this today but all is well and back on track.

It will require a little more investigation as I was not available during the actual event. We are looking into the cause and will get to the bottom of it and hopefully prevent any issues from here on out. The next update is still on track for a release date of 7/30/2013

For now it is recommended that users spread out their hashrate. If the  pool you are mining on is controlling a substantial amount of the network consider one of the many other great pools. This can only lead to a more efficient network and hopefully avoid any issues like this in the future.

[captainfuture]

whats the diff right now?

[erundook]

was there a fork? seems like my pool was on a wrong chain until now. re-downloading the blockchain now...

[mullick]

was there a fork? seems like my pool was on a wrong chain until now. re-downloading the blockchain now...

It appears so. We are still investigating in light of new information

[Isotactic]

Is anyone else having difficulty with payouts from www.bottlecapspool.com?
I should have had 5 payouts from the site, but only 2 are actually showing up on the blockchain:

1089864   2013-07-26 09:44:34   Don_Fee          -0.10000000
1089864   2013-07-26 09:44:34   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.12082583

1079121   2013-07-26 06:59:27   Don_Fee          -0.10000000
1079121   2013-07-26 06:59:27   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.07787684

1067868   2013-07-26 04:26:41   Don_Fee          -0.10000000
1067868   2013-07-26 04:26:41   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.03213076

1054597   2013-07-25 17:42:28   Don_Fee          -0.10000000
1054597   2013-07-25 17:42:28   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.92989879

1043043   2013-07-25 10:08:30   Don_Fee          -0.10000000
1043043   2013-07-25 10:08:30   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.9567508

http://bot.webboise.com:2760/address/F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5

It appears that the bottom two went through without any issues, but the top three are MIA.

I didn't have any issues with payouts from that pool, but stopped mining there yesterday. My results there were horrendous. I started tracking the results per hour and was getting about 68% of the coins I should have been receiving according to their stats.

I just tried to login to the pool now to double check my transaction history, but the site seems down. I've had no problem with any transactions going through from any point to point anywhere on the network, and confirmations are really fast. Everything has been flawless for me concerning transactions.

BigVern's Wallet for bottlecaps pool got corrupted should be fixed now. The weird blip was due to 90% of the hashrate popping off at one time. Lets spread the wealth to some of the other pools as well. Silverwolf, Eurdook, Multipool all run some great stuff try em out.

Still have not gotten paid... Kind of a bummer, something like that really turns you off of what looked to be a decent coin.

[eBit]

Looking into issues now. Will update when i have all the info. Chain is back on track form what i can see

That does not sound good. Rather than making some fancy client skins, I would rather see the devs focus on client security and network monitoring tools first.

I understand your concern 100%. In fact for the skinnable wallet we are looking to hire outside. Network functionality and security are our #1 goal and I have been working on nothing else until any issues are resolved.

We can assure you chain is back on track and moving ahead smoothly. If you are having Issues syncing your client Re downloading the blockchain should resolve the issue.

This does not appear to be an attack of any sort but may have been caused or exaggerated by 90% of the network hashrate disappearing when verns pool went down. We had a slight dip in coin generation due to this today but all is well and back on track.

It will require a little more investigation as I was not available during the actual event. We are looking into the cause and will get to the bottom of it and hopefully prevent any issues from here on out. The next update is still on track for a release date of 7/30/2013

For now it is recommended that users spread out their hashrate. If the  pool you are mining on is controlling a substantial amount of the network consider one of the many other great pools. This can only lead to a more efficient network and hopefully avoid any issues like this in the future.

I was mining at a different pool at the time.  After having some issues with Vern's & Silverwolf on this coin, I wasn't expecting anything much, but I thought I'd give http://cap.epools.org a try. Wow! What a difference. I was actually getting the correct amount of coin and slightly more. I was truly impressed with this pool. It just worked right.

After you mentioned an issue here, I checked the pool right before going to sleep and everything seemed to be working well, blocks were confirming so I wasn't concerned. The difficulty started going down so I figured miners were jumping to another coin and the number of coins I was mining was going up. When I woke up, I checked the pool stats and half my mining balance was gone.  I definitely thought I got scammed by the pool. When I investigated further I realized that a fork did occur and that there were a whole chain of now invalid blocks.

It looks like the fork occurred between blocks 47,738 and 47,743. The pool synched back up with a longer chain between blocks 48,217 and 47,985. That's about 479 blocks on the invalid chain (value about $225 in coins). If we were the shorter chain, shouldn't we have synched back up automatically after a few blocks at most?  I checked the Silverwolf pool, and that pool remained on the currently correct chain at the time of the fork.

I tried re-downloading the block chain a couple times. It struggled. Only three piers. It finally downloaded and all my wallet coins are there and confirmed. We need the checkpoint w/client update soon!

The other strange thing I noticed was that because the chain was taking hours to download, I sent a test transaction before I had the entire chain had downloaded. What happened surprised me. Not only did this transaction go through, but it received multiple confirmations.  How is this even possible if my client didn't even download the block in which the transaction occurred?  Is this something unique to Proof of Stake? I thought the client could only display a confirmed transaction after it downloaded the block that contained that transaction.

Please update once you have more info. about the fork.  I've posted what I know. Thanks.

[eBit]

Is anyone else having difficulty with payouts from www.bottlecapspool.com?
I should have had 5 payouts from the site, but only 2 are actually showing up on the blockchain:

1089864   2013-07-26 09:44:34   Don_Fee          -0.10000000
1089864   2013-07-26 09:44:34   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.12082583

1079121   2013-07-26 06:59:27   Don_Fee          -0.10000000
1079121   2013-07-26 06:59:27   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.07787684

1067868   2013-07-26 04:26:41   Don_Fee          -0.10000000
1067868   2013-07-26 04:26:41   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -15.03213076

1054597   2013-07-25 17:42:28   Don_Fee          -0.10000000
1054597   2013-07-25 17:42:28   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.92989879

1043043   2013-07-25 10:08:30   Don_Fee          -0.10000000
1043043   2013-07-25 10:08:30   Debit_ATP   F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5      -14.9567508

http://bot.webboise.com:2760/address/F4iiBtyq3bNpWoojxDYPnMdL9TUMLMHiV5

It appears that the bottom two went through without any issues, but the top three are MIA.

I didn't have any issues with payouts from that pool, but stopped mining there yesterday. My results there were horrendous. I started tracking the results per hour and was getting about 68% of the coins I should have been receiving according to their stats.

I just tried to login to the pool now to double check my transaction history, but the site seems down. I've had no problem with any transactions going through from any point to point anywhere on the network, and confirmations are really fast. Everything has been flawless for me concerning transactions.

BigVern's Wallet for bottlecaps pool got corrupted should be fixed now. The weird blip was due to 90% of the hashrate popping off at one time. Lets spread the wealth to some of the other pools as well. Silverwolf, Eurdook, Multipool all run some great stuff try em out.

Still have not gotten paid... Kind of a bummer, something like that really turns you off of what looked to be a decent coin.

I think you need to reinitiate the transfers.

BigVern's tweets:

 BigVern @LiteBonk
I will be removing withdrawal and payment transactions that occurred on the bottlecaps pool during the fork.

 BigVern @LiteBonk
After removing the transactions, you will be able to reinitiate any withdrawals