check out here to get a working copy of the blockchain just a few days back
http://wiki.hobonickels.info/index.php?title=Replace_Blockchain
Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 229. (Read 478852 times)
April 12, 2014, 08:22:21 AM
April 12, 2014, 08:17:35 AM
Hi
https://github.com/Tranz5/HoboNickels/releases/tag/1.4.0.0
I just downloaded this to update and now it is taking a real long time to sync ( like 24 + hours ) it just does not seem to make a connection for very long,,,, in fact looking at it now the "blocks remaining" is going up and not down
any reason for this ??
oh i need to add that i am trying to sync by loading my old roaming folder is this correct ??
cheers
https://github.com/Tranz5/HoboNickels/releases/tag/1.4.0.0
I just downloaded this to update and now it is taking a real long time to sync ( like 24 + hours ) it just does not seem to make a connection for very long,,,, in fact looking at it now the "blocks remaining" is going up and not down
any reason for this ??
oh i need to add that i am trying to sync by loading my old roaming folder is this correct ??
cheers
I had the same problem. I just deleted everything except for my wallets. downloading the blockchain again, its going to take a while. If you can get it to sync without deleting anything, that's even better.
April 12, 2014, 08:16:58 AM
Hi
https://github.com/Tranz5/HoboNickels/releases/tag/1.4.0.0
I just downloaded this to update and now it is taking a real long time to sync ( like 24 + hours ) it just does not seem to make a connection for very long,,,, in fact looking at it now the "blocks remaining" is going up and not down
any reason for this ??
oh i need to add that i am trying to sync by loading my old roaming folder is this correct ??
cheers
https://github.com/Tranz5/HoboNickels/releases/tag/1.4.0.0
I just downloaded this to update and now it is taking a real long time to sync ( like 24 + hours ) it just does not seem to make a connection for very long,,,, in fact looking at it now the "blocks remaining" is going up and not down
any reason for this ??
oh i need to add that i am trying to sync by loading my old roaming folder is this correct ??
cheers
See if this page helps. You may just need to add a few nodes manually.
https://cryptocointalk.com/topic/9592-hbn-trouble-shooting-guide-syncing-and-checkpoints/
April 12, 2014, 08:16:07 AM
Good news and bad news.
Good news. After fixing a small issue with the Pi, it staked quite easily within 10 minuets of 1500 coins at 20 days weight, after getting up to current.
https://cryptocointalk.com/topic/8233-pihobonickels/
I am considering loading up a few of these bad boys with version 1.4.0.1 and some coins, and selling them. Fast load time, easy staking, should be perfect for the pi. If you are interested in buying or helping, let me know.
Bad News.
I am going to release 1.4.0.1 as a pre-release only. I have a been able to create a stable index by shutting down the client every 200k blocks, during initial download. If I let it go from start to finish i get an assert failure on the next shut down, and restart. But all seems fine, if I give it a break. Not sure what is going on, but I wouldn't mind a bit of feed back from the community.
I'll put this up tomorrow, so we can get a few tests and feedback in.
Thanks!
Good news. After fixing a small issue with the Pi, it staked quite easily within 10 minuets of 1500 coins at 20 days weight, after getting up to current.
https://cryptocointalk.com/topic/8233-pihobonickels/
I am considering loading up a few of these bad boys with version 1.4.0.1 and some coins, and selling them. Fast load time, easy staking, should be perfect for the pi. If you are interested in buying or helping, let me know.
Bad News.
I am going to release 1.4.0.1 as a pre-release only. I have a been able to create a stable index by shutting down the client every 200k blocks, during initial download. If I let it go from start to finish i get an assert failure on the next shut down, and restart. But all seems fine, if I give it a break. Not sure what is going on, but I wouldn't mind a bit of feed back from the community.
I'll put this up tomorrow, so we can get a few tests and feedback in.
Thanks!
The Pi sounds awesome! I just wish they had expandable RAM! Still considering it though. So small.
Version 1.4.01 should not be a problem if you already have the chain downloaded then right?
yes.
April 12, 2014, 07:37:34 AM
Hi
https://github.com/Tranz5/HoboNickels/releases/tag/1.4.0.0
I just downloaded this to update and now it is taking a real long time to sync ( like 24 + hours ) it just does not seem to make a connection for very long,,,, in fact looking at it now the "blocks remaining" is going up and not down
any reason for this ??
oh i need to add that i am trying to sync by loading my old roaming folder is this correct ??
cheers
https://github.com/Tranz5/HoboNickels/releases/tag/1.4.0.0
I just downloaded this to update and now it is taking a real long time to sync ( like 24 + hours ) it just does not seem to make a connection for very long,,,, in fact looking at it now the "blocks remaining" is going up and not down
any reason for this ??
oh i need to add that i am trying to sync by loading my old roaming folder is this correct ??
cheers
April 12, 2014, 01:21:32 AM
The Pi is so cool 
I just added a bunch of stats to the rich list, check it out (click on the blue button for more)
http://hbn.blockx.info/richlist/
I just added a bunch of stats to the rich list, check it out (click on the blue button for more)
http://hbn.blockx.info/richlist/
April 12, 2014, 01:14:09 AM
Good news and bad news.
Good news. After fixing a small issue with the Pi, it staked quite easily within 10 minuets of 1500 coins at 20 days weight, after getting up to current.
https://cryptocointalk.com/topic/8233-pihobonickels/
I am considering loading up a few of these bad boys with version 1.4.0.1 and some coins, and selling them. Fast load time, easy staking, should be perfect for the pi. If you are interested in buying or helping, let me know.
Bad News.
I am going to release 1.4.0.1 as a pre-release only. I have a been able to create a stable index by shutting down the client every 200k blocks, during initial download. If I let it go from start to finish i get an assert failure on the next shut down, and restart. But all seems fine, if I give it a break. Not sure what is going on, but I wouldn't mind a bit of feed back from the community.
I'll put this up tomorrow, so we can get a few tests and feedback in.
Thanks!
Good news. After fixing a small issue with the Pi, it staked quite easily within 10 minuets of 1500 coins at 20 days weight, after getting up to current.
https://cryptocointalk.com/topic/8233-pihobonickels/
I am considering loading up a few of these bad boys with version 1.4.0.1 and some coins, and selling them. Fast load time, easy staking, should be perfect for the pi. If you are interested in buying or helping, let me know.
Bad News.
I am going to release 1.4.0.1 as a pre-release only. I have a been able to create a stable index by shutting down the client every 200k blocks, during initial download. If I let it go from start to finish i get an assert failure on the next shut down, and restart. But all seems fine, if I give it a break. Not sure what is going on, but I wouldn't mind a bit of feed back from the community.
I'll put this up tomorrow, so we can get a few tests and feedback in.
Thanks!
The Pi sounds awesome! I just wish they had expandable RAM! Still considering it though. So small.
Version 1.4.01 should not be a problem if you already have the chain downloaded then right?
April 11, 2014, 11:59:53 PM
Good news and bad news.
Good news. After fixing a small issue with the Pi, it staked quite easily within 10 minuets of 1500 coins at 20 days weight, after getting up to current.
https://cryptocointalk.com/topic/8233-pihobonickels/
I am considering loading up a few of these bad boys with version 1.4.0.1 and some coins, and selling them. Fast load time, easy staking, should be perfect for the pi. If you are interested in buying or helping, let me know.
Bad News.
I am going to release 1.4.0.1 as a pre-release only. I have a been able to create a stable index by shutting down the client every 200k blocks, during initial download. If I let it go from start to finish i get an assert failure on the next shut down, and restart. But all seems fine, if I give it a break. Not sure what is going on, but I wouldn't mind a bit of feed back from the community.
I'll put this up tomorrow, so we can get a few tests and feedback in.
Thanks!
Good news. After fixing a small issue with the Pi, it staked quite easily within 10 minuets of 1500 coins at 20 days weight, after getting up to current.
https://cryptocointalk.com/topic/8233-pihobonickels/
I am considering loading up a few of these bad boys with version 1.4.0.1 and some coins, and selling them. Fast load time, easy staking, should be perfect for the pi. If you are interested in buying or helping, let me know.
Bad News.
I am going to release 1.4.0.1 as a pre-release only. I have a been able to create a stable index by shutting down the client every 200k blocks, during initial download. If I let it go from start to finish i get an assert failure on the next shut down, and restart. But all seems fine, if I give it a break. Not sure what is going on, but I wouldn't mind a bit of feed back from the community.
I'll put this up tomorrow, so we can get a few tests and feedback in.
Thanks!
April 11, 2014, 05:22:07 PM
New wallet is working really well for me... now if only the price of HBN would take a dip so that I can load up!
Yes mine has also been very nice. Been testing the new start up, so far it is working. Load time on full block chain with empty wallet was less then 10 seconds. Old version was about almost 5 minutes.
Still had a few issue with Asserts, so changed the coding a bit and getting good success. Doing 1 more full network sync test from scratch. If that goes well I will look to move this into production.
April 11, 2014, 12:14:27 PM
New wallet is working really well for me... now if only the price of HBN would take a dip so that I can load up!
April 10, 2014, 02:37:58 AM
http://hobonickels.chickenstrips.net could use some hash, currently at 5.5mh/s
April 09, 2014, 11:48:34 PM
HBN Lesson for the day #1
Why orphans happen?
Here is one example as to why you might get an orphan block with PoS.
All within 6 seconds, for world wide network, with 30 second block time. Not bad really!
Why orphans happen?
Here is one example as to why you might get an orphan block with PoS.
Code:
04/10/14 03:25:33 SetBestChain: new best=0000000005cadad37032 height=746269 trust=1931039688483 date=04/10/14 03:24:40 (peer sent block)
04/10/14 03:25:33 ProcessBlock: ACCEPTED (Block is good)
04/10/14 03:25:33 ProcessSyncCheckpoint: sync-checkpoint at 0000000005cadad37032e692be2124d6d876c423888e9fd8a5e5e7cc09eec4bd (checkpoint agrees)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:35 CheckStake() : new proof-of-stake block found ( I find PoS!)
hash: b6dfb34b7df788a
.....
04/10/14 03:25:36 SetBestChain: new best=b6dfb34b7df788a9f841 height=746270 trust=1931056500073 date=04/10/14 03:25:30 (I accept my own block as valid)
04/10/14 03:25:36 ProcessBlock: ACCEPTED (looks good by me, from me!)
04/10/14 03:25:36 getblocks 746270 to 00000000000000000000 limit 500 (network wants the block)
....
04/10/14 03:25:38 REORGANIZE (uh oh)
04/10/14 03:25:38 REORGANIZE: Disconnect 1 blocks; 0000000005cadad37032..b6dfb34b7df788a9f841 ( my block is no good)
04/10/14 03:25:38 REORGANIZE: Connect 1 blocks; 0000000005cadad37032..f6593834a47b8f920358 ( connect new block)
04/10/14 03:25:38 REORGANIZE: done
...
04/10/14 03:25:38 ProcessSyncCheckpoint: sync-checkpoint at f6593834a47b8f920358a809d106d35bdfda5c1f08feaebf462f7764ef38de0d (CP agrees his was first)
04/10/14 03:25:39 getblocks 746270 to f6593834a47b8f920358 limit 500 (network wants this block instead)
All within 6 seconds, for world wide network, with 30 second block time. Not bad really!
That is incredibly fast for the daemon to realize that the block wasn't accepted by the other nodes. Very interesing.
April 09, 2014, 10:48:19 PM
HBN Lesson for the day #1
Why orphans happen?
Here is one example as to why you might get an orphan block with PoS.
All within 6 seconds, for world wide network, with 30 second block time. Not bad really!
Why orphans happen?
Here is one example as to why you might get an orphan block with PoS.
Code:
04/10/14 03:25:33 SetBestChain: new best=0000000005cadad37032 height=746269 trust=1931039688483 date=04/10/14 03:24:40 (peer sent block)
04/10/14 03:25:33 ProcessBlock: ACCEPTED (Block is good)
04/10/14 03:25:33 ProcessSyncCheckpoint: sync-checkpoint at 0000000005cadad37032e692be2124d6d876c423888e9fd8a5e5e7cc09eec4bd (checkpoint agrees)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:34 getblocks -1 to 00000000000000000000 limit 500 (network asks for current block)
04/10/14 03:25:35 CheckStake() : new proof-of-stake block found ( I find PoS!)
hash: b6dfb34b7df788a
.....
04/10/14 03:25:36 SetBestChain: new best=b6dfb34b7df788a9f841 height=746270 trust=1931056500073 date=04/10/14 03:25:30 (I accept my own block as valid)
04/10/14 03:25:36 ProcessBlock: ACCEPTED (looks good by me, from me!)
04/10/14 03:25:36 getblocks 746270 to 00000000000000000000 limit 500 (network wants the block)
....
04/10/14 03:25:38 REORGANIZE (uh oh)
04/10/14 03:25:38 REORGANIZE: Disconnect 1 blocks; 0000000005cadad37032..b6dfb34b7df788a9f841 ( my block is no good)
04/10/14 03:25:38 REORGANIZE: Connect 1 blocks; 0000000005cadad37032..f6593834a47b8f920358 ( connect new block)
04/10/14 03:25:38 REORGANIZE: done
...
04/10/14 03:25:38 ProcessSyncCheckpoint: sync-checkpoint at f6593834a47b8f920358a809d106d35bdfda5c1f08feaebf462f7764ef38de0d (CP agrees his was first)
04/10/14 03:25:39 getblocks 746270 to f6593834a47b8f920358 limit 500 (network wants this block instead)
All within 6 seconds, for world wide network, with 30 second block time. Not bad really!
April 09, 2014, 08:44:06 PM
Acutally I just found the issue.
1 line.
READWRITE(blockHash);
I will be testing this over the next few days and then re-releasing 1.4.0.1. I think it might be it!
1 line.
READWRITE(blockHash);
I will be testing this over the next few days and then re-releasing 1.4.0.1. I think it might be it!
Yes!!
April 09, 2014, 07:52:04 PM
Acutally I just found the issue.
1 line.
READWRITE(blockHash);
I will be testing this over the next few days and then re-releasing 1.4.0.1. I think it might be it!
1 line.
READWRITE(blockHash);
I will be testing this over the next few days and then re-releasing 1.4.0.1. I think it might be it!
April 09, 2014, 07:39:31 PM
Thanks for the update Tranz, good stuff man. 
April 09, 2014, 06:46:29 PM
1.4 running fine. I just wish the startup time was faster. Loading block index takes forever.
Yes I have been thinking of more ways to speed it up. Such as compiling with 64 bit(may help) and/or threading the init load. Difficulties arrise on both.
Perhaps take a look at what PHS is doing? One of the more recent updates to the PHS client lowered loading time significantly.
For comparison
PHS load time: 14s
HBN load time: 281s
The code is very close, and comes from NVC's fast start. PHS is at block ~200,000, HBN is approaching 750,000. So PHS will also slow as time goes.
However I will take another look at sometime and see if I missed something.
Didn't think of the vast difference in block count.
Appreciate all the work you put into this coin.
April 09, 2014, 06:34:23 PM
1.4 running fine. I just wish the startup time was faster. Loading block index takes forever.
Yes I have been thinking of more ways to speed it up. Such as compiling with 64 bit(may help) and/or threading the init load. Difficulties arrise on both.
Perhaps take a look at what PHS is doing? One of the more recent updates to the PHS client lowered loading time significantly.
For comparison
PHS load time: 14s
HBN load time: 281s
The code is very close, and comes from NVC's fast start. PHS is at block ~200,000, HBN is approaching 750,000. So PHS will also slow as time goes.
However I will take another look at sometime and see if I missed something.
April 09, 2014, 06:12:38 PM
1.4 running fine. I just wish the startup time was faster. Loading block index takes forever.
Yes I have been thinking of more ways to speed it up. Such as compiling with 64 bit(may help) and/or threading the init load. Difficulties arrise on both.
Perhaps take a look at what PHS is doing? One of the more recent updates to the PHS client lowered loading time significantly.
For comparison
PHS load time: 14s
HBN load time: 281s
April 09, 2014, 04:41:10 PM
1.4 running fine. I just wish the startup time was faster. Loading block index takes forever.
Yes I have been thinking of more ways to speed it up. Such as compiling with 64 bit(may help) and/or threading the init load. Difficulties arrise on both.
Maybe consider adding progress bar. Users are more willing to wait if they know how long they have to wait.
Jump to: