Pages:
Author

Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 55. (Read 388610 times)

hero member
Activity: 808
Merit: 502
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?
legendary
Activity: 1218
Merit: 1002
Supporting DMD, ERC & PIO
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
sr. member
Activity: 422
Merit: 250
Meow
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.
hero member
Activity: 750
Merit: 500
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+.
full member
Activity: 128
Merit: 100
INSERT COIN
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).
hero member
Activity: 750
Merit: 500
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)
full member
Activity: 152
Merit: 100
Evening all,

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

If you appreciate it here is his BottleCaps address = Et4a2FrRzRxC4RAh88haNag3UaFFubyaPo

Thanks Fuzzbawls!

Quote from: 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
full member
Activity: 152
Merit: 100
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.  

newbie
Activity: 17
Merit: 0
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.
sr. member
Activity: 378
Merit: 251
Where is bottlecaps traded?
sr. member
Activity: 422
Merit: 250
Meow
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.
hero member
Activity: 583
Merit: 502
Thanks for all the info guys, I'm gonna use it then Smiley
hero member
Activity: 786
Merit: 1000
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.
newbie
Activity: 17
Merit: 0
no, but files from PressF1 are reliable so try with confidence.
hero member
Activity: 583
Merit: 502
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.
hero member
Activity: 583
Merit: 502
current peers

98.115.147.74
193.227.134.111
62.210.122.161
178.33.64.234

Thanks a lot man, I really appreciate them.
legendary
Activity: 912
Merit: 1000
current peers

98.115.147.74
193.227.134.111
62.210.122.161
178.33.64.234
legendary
Activity: 912
Merit: 1000

Btw, do you have some nodes that I can get a hold of for my .conf file? the daemon is running but it can't sync :/

Later tonight when I am home from work I will post the peers I am connected to. 
hero member
Activity: 583
Merit: 502
Finally I could fix the error from: "error: makefile.unix:160: *** missing separator. Stop."

Amazingly, it was caused for the lack of a 'tab' instead of 'spaces' in the line:  "$(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<" (the one after "obj/scrypt-arm.o: scrypt-arm.S"). The line should be: "$(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<".

Btw, I also changed:
Code:
obj/scrypt-x86.o \
obj/scrypt-x86_64.o \
obj/srcypt-arm.S

For:
Code:
obj/scrypt-x86.o \
obj/scrypt-x86_64.o \
obj/srcypt-arm.o

I'll let you know how that worked out when it finish compiling.

Edit: Success! Finally I could compile the bottlecapsd and it's running right now. The only problem that I haven't solve yet is the synchronization. Looks like it can't find peers. Does anyone would care to share some working peers, please?

Thanks in advance.
Again sorry for typos...any of the actual code pieces like that above I was looking at my Pi screen for the code and typing on my Windows desktop....and it was late at night...and i had wine....and...  Grin

BTW...hope you changed it to obj/scrypt-arm.o....i notice my typo has the c and r backwards as well... 

Original Post updated with typo fixes

No need to sorry, on the contrary! thanks again for such a detailed guide! It is just great! (the typos are very understandable in such a long guide)

And yes, I did changed the .S for the .o, thanks Smiley

Btw, do you have some nodes that I can get a hold of for my .conf file? the daemon is running but it can't sync :/
Pages:
Jump to: