Yes if you are on the correct block, currently 505952+ you are good to go. Unick has said that is not fully functional yet. Hello! my wallet still say's "warning:INvalid Checkpoint found displayed trasaction may not be correct you may need to upgrade or or notify 8 active connection Lat receive block 1 minute ago 500875 block in the top out of sync I tried to dowload again the blockchain I delete the the 2 file in bottlecap folder, i did 3 times already That chain you are on is over 7,000 short of the real on. Not sure why you are having this trouble? You are using 2.1 yes? https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.1.zipIt is possible you are only connecting to bad peers, but that seems odd. Make sure you are one 2.1 then try to remove blkindex.dat, blk0001.dat and peers.dat . Then start up 2.1. If this still doesn't work for you, please PM me, I will help you get sorted out. Just checking on how it is going. Did this help? hello! I still have this message "warning:INvalid Checkpoint found displayed trasaction may not be correct you may need to upgrade or or notify" but the out of SYNC is gone it says updated dowloaded 501003 block last receive 7 minutes Hmm Something is clearly not correct. I am going to send you a PM. |
|
|
|
I have added an additional 1000 coins to each of the wallets I use for stake for charity listed on the charity page on hobonickels.info http://hobonickels.info/donate.phpThere are now 2,000 each in those wallets and 50% of all stakes are going to those addresses. I will be adding more in the future as well. Want to be part? Let us know! We are looking for "real" charities, or someone who will run service for HBN. Some restrictions do apply. Please feel free to write here or PM me. Thanks! |
|
|
|
Yes if you are on the correct block, currently 505952+ you are good to go. Unick has said that is not fully functional yet. Hello! my wallet still say's "warning:INvalid Checkpoint found displayed trasaction may not be correct you may need to upgrade or or notify 8 active connection Lat receive block 1 minute ago 500875 block in the top out of sync I tried to dowload again the blockchain I delete the the 2 file in bottlecap folder, i did 3 times already That chain you are on is over 7,000 short of the real on. Not sure why you are having this trouble? You are using 2.1 yes? https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.1.zipIt is possible you are only connecting to bad peers, but that seems odd. Make sure you are one 2.1 then try to remove blkindex.dat, blk0001.dat and peers.dat . Then start up 2.1. If this still doesn't work for you, please PM me, I will help you get sorted out. Just checking on how it is going. Did this help? |
|
|
|
Can maybe someone change the header of this discussion? It says 2.0 update in stead of 2.1.
Also the link to the wallet on page 1 is to the 2.0 version instead of 2.1.
It may solve some potential trouble someone new to CAPS could encounter
The link in the oOP says 2.0, but the zip actually contains 2.1. If Flounder wants to update it, the best link to put is not the zip but my release page. https://github.com/Tranz5/bottlecaps/releasesThis goes for anyone linking the wallets. This will always have the most updated wallets. |
|
|
|
Yes if you are on the correct block, currently 505952+ you are good to go. Unick has said that is not fully functional yet. Hello! my wallet still say's "warning:INvalid Checkpoint found displayed trasaction may not be correct you may need to upgrade or or notify 8 active connection Lat receive block 1 minute ago 500875 block in the top out of sync I tried to dowload again the blockchain I delete the the 2 file in bottlecap folder, i did 3 times already That chain you are on is over 7,000 short of the real on. Not sure why you are having this trouble? You are using 2.1 yes? https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.1.zipIt is possible you are only connecting to bad peers, but that seems odd. Make sure you are one 2.1 then try to remove blkindex.dat, blk0001.dat and peers.dat . Then start up 2.1. If this still doesn't work for you, please PM me, I will help you get sorted out. |
|
|
|
So I was able to fix the wallet from ESM and I took the opportunity to full sync test. I was able to do it starting fresh in 8 hours. No restarts just started it up and let it go! Also I got a message for a new site. Please vote if you think we should have HBN there. I haven't done any due diligence, just passing along information. So use it as such. Thanks. We have added HoboNickels into our voting list for a few days. I want you to know HBN will catch more chinese players' eyes to know and participate when it lives on our exchange.If you'r not sure the vote of HBN can reach 1000,we will cancel it.So pls reply me,thanks.
the voting rule as follow:
An effective vote will cost 10 ECFC(EcoinfundCoin), repeating vote are allowed, each coin will be listed on our exchange the next day as soon as the vote reach 1000.
EcoinFund
Website:ecoinfund.com They don't even have the correct website for HBN listed http://ecoinfund.com/voteEwww, ya that was from the original ANN thread about 256 days ago.. |
|
|
|
Yes if you are on the correct block, currently 505952+ you are good to go. Unick has said that is not fully functional yet. |
|
|
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar? tnx 607 to go, or at block 607, either way no reason for that. The connection icon is to the right of the staking arrow. I have 19 connections 3 are bad, 2 are in the process of syncing. So it looks like things are getting normal. hello! I close and open the wallet again now it says out of sync but it says 8 active connection when i put my cursor to the word out of sync its says "the displaed information maybe out of date your wallet automatically synchronizes with the bottlecap network after a connection is establish but this process has not completed yet" Sounds like you got stuck on the wrong chain. Please shutdown client and remove blk0001.dat and blkindex.dat and restart. Please be sure to use 2.1. Alternatively you can also try to create a DB_CONFIG file as suggested by ghostlander here: https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114 |
|
|
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. Banning bad peers via firewall worked, thanks. Are there plans to add some kind of peer blacklist to the wallet? Something like bannode=1.2.3.4. The Extended Peer Information window has the advantage over getpeerinfo that it shows converted date/time but it has fixed size and the text box is very small. I had to copy&paste to notepad for comfortable reading, so a variable size window would be cool. You can hit control c on the window and paste the entire Detailed View into notepad. The popup window that I used built into QT doesn't allow size update. But one of these days when I have time I will see about popping up a more custom window, similar to the about window. It's just a lot more work. I've thought about bannode before. I may do it. I'd would hate for everyone to ban these IPs and they are not able to get connection to network, once they get themselves fixed up. |
|
|
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar? tnx 607 to go, or at block 607, either way no reason for that. The connection icon is to the right of the staking arrow. I have 19 connections 3 are bad, 2 are in the process of syncing. So it looks like things are getting normal. |
|
|
|
|
Regarding Cryptsy and other exchanges.
I do not take part in pushing any coin anywhere. I may vote for free here and there if I have a few minutes. But if it requires sending BTC to get a coin listed, it might as well just be a bribe in my opinion. I do not take part in that. If an exchange wants to list it. Here it is.
My job here is to get the wallet working, the network secure and the community excited about a coin. The rest is up to you guys.
I may work towards getting certain people or aspects on board. Such as I will soon be working on getting some high profile charities involved with HoboNickels. But that is about my fullest extent towards pushing a coin on anyone.
Let's work together to achieve the ends we all desire. Divide and concur and casting blame, isn't likely to have the desired results.
Thanks!
|
|
|
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. |
|
|
|
So I was able to fix the wallet from ESM and I took the opportunity to full sync test. I was able to do it starting fresh in 8 hours. No restarts just started it up and let it go! Also I got a message for a new site. Please vote if you think we should have HBN there. I haven't done any due diligence, just passing along information. So use it as such. Thanks. We have added HoboNickels into our voting list for a few days. I want you to know HBN will catch more chinese players' eyes to know and participate when it lives on our exchange.If you'r not sure the vote of HBN can reach 1000,we will cancel it.So pls reply me,thanks.
the voting rule as follow:
An effective vote will cost 10 ECFC(EcoinfundCoin), repeating vote are allowed, each coin will be listed on our exchange the next day as soon as the vote reach 1000.
EcoinFund
Website:ecoinfund.com |
|
|
|
Version 2.1 is ready.
Generated 1% PoS block today. thanks! Cryptsy is still screwy. Of the two deposits I've made (6/12 and 6/18), only the 6/18 one showed up. This coin really needs another Exchange as it now lives/dies/values solely by Cryptsy's wallet maintenance schedule. hello! how many total coin has bottle cap will have? In-deterministic. There is no hard cap. The target is 47MM, but with the change to 200% PoS, this target will likely be breached in 3-4 years. But the rate of inflation should begin slowing as we approach it. |
|
|
|
Hi,
I have this version v1.4.0.1, but they are two days that the wallet is not synchronized. What should I do?
thanks
Hi a bit more information could help. Did the wallet seem to get stuck on a block? Sometimes a quick shutdown restart of the client can help. Do you have a strong connection to the network? 8+ If not you can try to addnodes using rpc while the client is running. See here http://wiki.hobonickels.info/index.php?title=Node and here http://hbn.blockx.info/connected-nodesYou can also try to use our blkchain download, which will get you much for farther along. http://wiki.hobonickels.info/index.php?title=Replace_BlockchainSlower machines can take 12-24+ hours. But shouldn't be much more then that. I did a recent download on my brothers older machine a few weeks ago it took about 7 hrs. |
|
|
|
hello! I want to make sure what im gonna do is right I will back up my wallet save the wallet.dat somewhere and install the new updated wallet and replace the new wallet.dat file in the new wallet ? thanks again No sir. Just grab this version and overwrite the executable you used to use. Then remove blk0001.dat and blkindex.dat. Don't remove anything else. Then just start up version 2.1, and resync. After you are done, click the thumbs up and verify you match http://cap.cryptocoinexplorer.com/ regarding height. If so you are good to go! |
|
|
|
Yep. Confirming v2.1 works for me. Thanks for all your work on this Tranz. I see a lot of improvements since v1.52.
The only issue I'd like to report is a highlighted message at the top of the Overview page stating that "Info: Minting suspended due to locked wallet" when in fact the wallet is unlocked and staking.
Thanks I actually meant to remove that, as we now have the staking icon. |
|
|
|
Hi guys. I added a small update to github tonight. There was an issue with staking and it wasn't working on 2.0 I have corrected this error: https://github.com/Tranz5/bottlecaps/commit/9409ca831c63763b34cd46b6736a3c2aa636beadFor you self compilers that want to stake, use this release. I will be officially releasing this, plus more sync issues fixes here tonight or tomorrow. Thanks for all your patients on this, hard forks can be a bit frustrating sometimes. But this time next month I think the network will be very secure and staking away! I'm on v2.0.0.1 and I'm able to generate POS blocks. Does that make sense? It depended on the size of the block. But Please try 2.1 (releasing here shortly) and let me know if it works for you. i am pretty sure it should work for all. |
|
|
|
|
Show Posts
