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

[cryptmebro]

Hi Guys,

Here are the latest bootstraps for HBN & CAP

http://www.mediafire.com/download/yfnp7ubv35h869z/HoboNickels1510_20160322.rar
http://www.mediafire.com/download/6os6mv5f36fxubh/BottleCaps2220_20160322.rar


Don't forget to make a backup of your wallet, Cheers!

Has someone tested/tried these files already? Will it be useful for RPi-2/3?

Thanks in advance.

I used the cap one, its fine.

[GoldTiger69]

Thanks for all the info guys, I'm gonna use it then

[catotune]

Hi Bottlecaps fans! I have been experiencing an issue with coin control lately: when I use coin control to consolidate my coins to one address, I am seeing the operation succeed in the coin control window, but these newly created blocks of coins never receive any confirmations.

This has only been happening lately; I've been able to use coin control normally for months. My wallet seems to be up to date with the blockchain, and sending coins via Auto Savings is working fine. Has anyone else experienced this, or knows how to fix it? Thanks.

[mybitcoin101]

Where is bottlecaps traded?

[GoldTiger69]

Where is bottlecaps traded?

AFAIK in Cryptopia: https://www.cryptopia.co.nz/Exchange/?market=CAP_BTC

[Lutomysl]

Hi Bottlecaps fans! I have been experiencing an issue with coin control lately: when I use coin control to consolidate my coins to one address, I am seeing the operation succeed in the coin control window, but these newly created blocks of coins never receive any confirmations.

This has only been happening lately; I've been able to use coin control normally for months. My wallet seems to be up to date with the blockchain, and sending coins via Auto Savings is working fine. Has anyone else experienced this, or knows how to fix it? Thanks.

i'm sorry to hear you are having problems with your walllet... are you sure you are not on a fork? beside this, i dont know what the problem might be.

[ReydeApio]

Hi Bottlecaps fans! I have been experiencing an issue with coin control lately: when I use coin control to consolidate my coins to one address, I am seeing the operation succeed in the coin control window, but these newly created blocks of coins never receive any confirmations.

This has only been happening lately; I've been able to use coin control normally for months. My wallet seems to be up to date with the blockchain, and sending coins via Auto Savings is working fine. Has anyone else experienced this, or knows how to fix it? Thanks.

I was having some wallet issues I

• Backed up my wallet; navigate: File > Backup Wallet > Save (to Vault)
• Checked my wallet; navigate: File >  Wallet > Check Wallet. (if no errors then skip next step.)
• Repaired my wallet; navigate: File >  Wallet > Repair Wallet. (if resolved then stop here.)
• Deleted all files except wallet.dat (repaired) from my bottlecaps appdata roaming folder then re-launched the QT client and re-synced the BlockChain.

A full resync fixed my issues (48 hours later) but you'll likely be able to stop at the third step.

Should you have read some earlier threads and come to the 'pywallet' mentions hesitate to download the current one. I recall coming across some recent negative feedback surrounding it stealing keys.

If you have issues dont hesitate to ask.  

[ReydeApio]

Evening all,

Fuzzbawls shared RPi binaries for BottleCaps-qt AND the bottlecapsd.  

If you appreciate it here is his BottleCaps address = Et4a2FrRzRxC4RAh88haNag3UaFFubyaPo

Thanks Fuzzbawls!

Got a successful stake on the RPi2

Here is the link to the binaries:
https://drive.google.com/open?id=0B-oIh2h7uqLSakE4c0llTmhCYlU

Included in the file is the BottleCaps-qt AND the bottlecapsd binaries, statically compiled for use on Raspbian Wheezy or Raspbian Jessie (RPi2 intended target). They MAY work on a RPi1 or RPi3, but as I don't have such hardware myself, I cannot verify.

As noted previously, the rather large size of the CAP blockchain may result in inherent instability of the program when running on any SBC platform. Users should monitor and make frequent backups of their wallet.dat files (which is general good practice for any coin wallet on any platform).

RPi2 Binaries were compiled using OpenSSL 1.0.2d, BerkeleyDB 4.8.30, and Qt 5.4.2. UPNP disabled

Raspbian Jessie has seen some updates that aren't included in the default image that seem to have fixed the instability issues I was previously having. These aren't "extra" packages, but newer/fixed versions of the packages that are installed by default on a base system.

Users of Raspbian Jessie should ensure that their packages/system are updated if they are experiencing any stability problems with the wallet.

The same may hold true for Raspbian Wheezy, but I have yet to do extensive testing on that platform (especially since Wheezy is becoming older)

https://twitter.com/bottlecapsio/status/726529083018870784

[Fuzzbawls]

Just wanted to chime in myself and state that the files produced from my RPi2 binaries are completely portable with other binary distributions of the BottleCaps wallet. Though if you have followed previously mentioned steps to self-compile, you are probably running with bdb5.x (in which case your blockchain and wallet files are NOT compatible)

[TentacleMan]

Just wanted to chime in myself and state that the files produced from my RPi2 binaries are completely portable with other binary distributions of the BottleCaps wallet. Though if you have followed previously mentioned steps to self-compile, you are probably running with bdb5.x (in which case your blockchain and wallet files are NOT compatible)

Wallet is upgradeable with the db_upgrade wallet.dat command though. db_upgrade came bundled with the Berkeley DB I use on my Linux system (Arch based).

[Fuzzbawls]

Just wanted to chime in myself and state that the files produced from my RPi2 binaries are completely portable with other binary distributions of the BottleCaps wallet. Though if you have followed previously mentioned steps to self-compile, you are probably running with bdb5.x (in which case your blockchain and wallet files are NOT compatible)

Wallet is upgradeable with the db_upgrade wallet.dat command though. db_upgrade came bundled with the Berkeley DB I use on my Linux system (Arch based).

Forward compatibility isn't the issue. The standard bdb version used is 4.8.30, which cannot open or otherwise use files that have been touched by bdb 5+.

[catotune]

Hi Bottlecaps fans! I have been experiencing an issue with coin control lately: when I use coin control to consolidate my coins to one address, I am seeing the operation succeed in the coin control window, but these newly created blocks of coins never receive any confirmations.

This has only been happening lately; I've been able to use coin control normally for months. My wallet seems to be up to date with the blockchain, and sending coins via Auto Savings is working fine. Has anyone else experienced this, or knows how to fix it? Thanks.

I was having some wallet issues I

• Backed up my wallet; navigate: File > Backup Wallet > Save (to Vault)
• Checked my wallet; navigate: File >  Wallet > Check Wallet. (if no errors then skip next step.)
• Repaired my wallet; navigate: File >  Wallet > Repair Wallet. (if resolved then stop here.)
• Deleted all files except wallet.dat (repaired) from my bottlecaps appdata roaming folder then re-launched the QT client and re-synced the BlockChain.

A full resync fixed my issues (48 hours later) but you'll likely be able to stop at the third step.

Should you have read some earlier threads and come to the 'pywallet' mentions hesitate to download the current one. I recall coming across some recent negative feedback surrounding it stealing keys.

If you have issues dont hesitate to ask.  

Thanks for your suggestions! Checking and repairing the wallet didn't do the trick, but everything is fine now that I:

1. Dumped all my private keys, recording them in a text file
2. Stopped my BottleCaps wallet
3. Removed everything from my AppData\Roaming\BottleCaps folder, except for BottleCaps.conf
4. Restarted my BottleCaps wallet
5. Imported all my private keys into the new, empty wallet that gets generated

Somehow my wallet.dat needed to be replaced by a fresh one.

[Woody20285]

Hi Bottlecaps fans! I have been experiencing an issue with coin control lately: when I use coin control to consolidate my coins to one address, I am seeing the operation succeed in the coin control window, but these newly created blocks of coins never receive any confirmations.

This has only been happening lately; I've been able to use coin control normally for months. My wallet seems to be up to date with the blockchain, and sending coins via Auto Savings is working fine. Has anyone else experienced this, or knows how to fix it? Thanks.

I was having some wallet issues I

• Backed up my wallet; navigate: File > Backup Wallet > Save (to Vault)
• Checked my wallet; navigate: File >  Wallet > Check Wallet. (if no errors then skip next step.)
• Repaired my wallet; navigate: File >  Wallet > Repair Wallet. (if resolved then stop here.)
• Deleted all files except wallet.dat (repaired) from my bottlecaps appdata roaming folder then re-launched the QT client and re-synced the BlockChain.

A full resync fixed my issues (48 hours later) but you'll likely be able to stop at the third step.

Should you have read some earlier threads and come to the 'pywallet' mentions hesitate to download the current one. I recall coming across some recent negative feedback surrounding it stealing keys.

If you have issues dont hesitate to ask.  

Thanks for your suggestions! Checking and repairing the wallet didn't do the trick, but everything is fine now that I:

1. Dumped all my private keys, recording them in a text file
2. Stopped my BottleCaps wallet
3. Removed everything from my AppData\Roaming\BottleCaps folder, except for BottleCaps.conf
4. Restarted my BottleCaps wallet
5. Imported all my private keys into the new, empty wallet that gets generated

Somehow my wallet.dat needed to be replaced by a fresh one.

Had the same problem - Nothing worked so I will try the dumpprivkey

[mmfiore]

whats up with the network difficulty for proof of work? I go to presstabs dashboard and it says no one is hashing but the difficulty is way high like in the 30 to 40 range. I am wondering how this could be?

[presstab]

whats up with the network difficulty for proof of work? I go to presstabs dashboard and it says no one is hashing but the difficulty is way high like in the 30 to 40 range. I am wondering how this could be?

no problem with network, smth wrong with presstab's explorer, it shows no pow data at all, and:

getdifficulty
{
"proof-of-work" : 9.74358349,
"proof-of-stake" : 0.01850548,
"search-interval" : 0
}

I don't see any proof of work blocks being published to the chain do you? Please advise.

[presstab]

whats up with the network difficulty for proof of work? I go to presstabs dashboard and it says no one is hashing but the difficulty is way high like in the 30 to 40 range. I am wondering how this could be?

no problem with network, smth wrong with presstab's explorer, it shows no pow data at all, and:

getdifficulty
{
"proof-of-work" : 9.74358349,
"proof-of-stake" : 0.01850548,
"search-interval" : 0
}

I don't see any proof of work blocks being published to the chain do you? Please advise.

that means no hashes, but why no pow diff on the graph ? it's simply constant now

The graph extracts information from the last 500 blocks. If there are not any PoW blocks then there is not any information added to the graph. Once another PoW block is added to the chain it will show up on the graph if it is within the last 500 blocks.

[mmfiore]

Thanks for the info but I noticed that when I try to mine bottlecaps it still seems much more difficult to find blocks. I have tried several times even throwing over 1 ghz at the pool and still not able to find a block and I notice that pool reporting large sudden shifts in difficulty. I did notice that that presstab explorer not showing found blocks. I watch my miners in putty using screen -r. and notice they are not finding blocks as if the difficulty was real high. Usually I can find several blocks every minute when difficulty is low. I will keep trying and see what happens.

[mmfiore]

Yeah its definitely the pool. I wrote the admin for the pool. Hopefully they will fix the problem.

[presstab]

Looks like PoW blocks are coming in again. Probably just some problems with the pools, or too high of difficulty or something. Glad to see everything working again.

[mmfiore]

the problem has been fixed. The pool had a glitch and switch my workers and pointed them to another coin. Bottlecaps network is golden