Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 201. (Read 388610 times)
July 27, 2013, 05:42:10 AM
was there a fork? seems like my pool was on a wrong chain until now. re-downloading the blockchain now...
July 27, 2013, 05:18:00 AM
whats the diff right now?
July 27, 2013, 02:16:25 AM
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.
July 26, 2013, 11:22:34 PM
Yeah I can't get the new client to work.
No more mining for me! Just wasted 24 hours.
No more mining for me! Just wasted 24 hours.
July 26, 2013, 07:36:29 PM
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 .
July 26, 2013, 07:34:36 PM
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 .
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 .
July 26, 2013, 07:23:57 PM
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.
July 26, 2013, 07:07:43 PM
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 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.
July 26, 2013, 07:04:35 PM
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 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.
July 26, 2013, 06:20:28 PM
Looking into issues now. Will update when i have all the info. Chain is back on track form what i can see
July 26, 2013, 05:01:10 PM
July 26, 2013, 04:21:16 PM
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://bitcointalksearch.org/topic/ann-nybble-0652-nybble-new-wallet-win-mac-and-source-new-pools-216637
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 " .
I'm blowing my own whistle here guys but Nibble is about the release one of the most stable clients currently out there
https://bitcointalksearch.org/topic/ann-nybble-0652-nybble-new-wallet-win-mac-and-source-new-pools-216637
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?
July 26, 2013, 02:45:27 PM
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.
July 26, 2013, 01:35:40 PM
Been mining other stuff lately...
What's the deal with the client? I haven't updated yet. Should I?
What's the deal with the client? I haven't updated yet. Should I?
July 26, 2013, 01:32:28 PM
...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.
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.
July 26, 2013, 01:27:34 PM
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.
July 26, 2013, 11:49:18 AM
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://bitcointalksearch.org/topic/ann-nybble-0652-nybble-new-wallet-win-mac-and-source-new-pools-216637
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 " .
I'm blowing my own whistle here guys but Nibble is about the release one of the most stable clients currently out there
https://bitcointalksearch.org/topic/ann-nybble-0652-nybble-new-wallet-win-mac-and-source-new-pools-216637
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 " .
July 26, 2013, 11:24:19 AM
Gotta love the Fallout game reference 
July 26, 2013, 11:18:23 AM
Does anyone want me to start a pool I can do p2pool or stratum
Yes. If you can get p2pool working for botttlecaps I would immediately point hashpower your way
Edit:
ATTENTION
Vern's pool is in the wrong chain?
Vern's pool is in the wrong chain?
Yeah, it appears that got off about 12 hours ago. Real excited about wasting all that hash power
How is that even possible ? Glad I wasn't mining , going to pause on bottlecaps , too many issues .
July 26, 2013, 11:16:04 AM
Hi I'm a little concerned about the Caps client -
Perhaps some advice / help ?
- The Checkpoint warning persists
- I sent 1101.531397 to an address the receiver has tried every way possible get the client to stop the warning but can not - regardless the destination client is in sync .
- But my transaction is sent out , (see below for Tran history) but under "transactions" has 0 of 6 confirmations and it has not arrived at the destination?
- the 1101 Caps have left this wallet but have 0 confirmations and not arrived at the other wallet
- both wallets show the same block downloaded block count
Transaction details :
Status: 0/unconfirmed
Date: 7/26/2013 12:43
To: digitalindustry-wallet F21vYmnvWRhmPSJ57s9J81TVgHi3etZQgM
Debit: -1101.531397 CAP
Transaction fee: -0.001 CAP
Net amount: -1101.532397 CAP
Transaction ID: af9cb93009791f900903d14cf3f338d7f34080cb38d60a7ddf46e01e1c84cd1a
Is this sort of behavior typical of a 51% type attack? - or could my wallet be having some sort of malfunction .
any help would be appreciated - i'd like not to lose the 1101 Caps as im saving for a new car energy cell.
That behavior is typical of a wallet not in sync. So if your wallet is in sync it leads me to believe your Tx is omitted from new blocks, and thus isn't being confirmed via PoW. I would suggest to make sure your wallet is definitely in sync. Next, perhaps a delete of blkindex.dat and peers.dat to force the Tx to be submitted into the CAP network. If you have any CAP in that wallet, send 1 CAP to anyone. Sometimes receiving/sending a PoS coin will trigger a quick scan of all past Tx with network and will force a re-submit of your Tx above.
-Merc
Ok I will try this , yes the original wallet had a blkindex.dat error and would not open , so I moved the wallet.dat to a new client , then made the transaction . It left my wallet but never arrived ?
This client seems to have a lot of issues , if I lose these caps , that's it for me . Have fun with bottlecaps.
Jump to: