Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
April 10, 2014, 03:48:19 AM |
|
HBN Lesson for the day #1 Why orphans happen? Here is one example as to why you might get an orphan block with PoS. 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!
|
|
|
|
|
|
|
|
|
"If you don't want people to know you're a scumbag then don't be a scumbag." -- margaritahuyan
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
April 10, 2014, 04:48:34 AM |
|
HBN Lesson for the day #1 Why orphans happen? Here is one example as to why you might get an orphan block with PoS. 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.
|
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
April 11, 2014, 05: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!
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
April 11, 2014, 10: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.
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
April 12, 2014, 04:59:53 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!
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
April 12, 2014, 06: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! 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?
|
|
|
|
|
semajjames
|
|
April 12, 2014, 12:37:34 PM |
|
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
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
April 12, 2014, 01:16:07 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! 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.
|
|
|
|
|
tokyoghetto
Legendary
Offline
Activity: 1232
Merit: 1000
|
|
April 12, 2014, 01:17:35 PM |
|
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 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.
|
|
|
|
|
semajjames
|
|
April 12, 2014, 01:54:12 PM |
|
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 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. If I start from fresh and just keep Wallet.dat file will i loose stake data ??
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
April 12, 2014, 03:20:02 PM |
|
Nope staking info is stored publically on the block chain not on a users machine.
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
April 12, 2014, 03:28:07 PM Last edit: April 13, 2014, 04:22:49 AM by Tranz |
|
Moving to version 1.4 should not require a re-index. Unless you were on a very old version before.
Was it trying to sync with the whole block chain? Or are we only talking about a few blocks to get to current?
Version 1.4.0.1 will require full re-sync.
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
April 12, 2014, 03:41:02 PM |
|
Using this is ok. Best to create your own index, but this is safe enough. However you shouldn't replace your database directory, this is used for the wallet.dat. Just need the blk0001.dat and the leveldb directory. Those 2 are for the block chain. wallet.dat and database directory work for the wallet.dat
|
|
|
|
dogechode
|
|
April 12, 2014, 05:08:28 PM |
|
hobonickels appears to have accomplished what 99% of the other altcoins have not been able to: slow and steady price gains that don't seem to be in any danger of crashing back down. Kudos to Tranz! I think the fact that he hasn't been pushing the coin on every exchange under the sun, or doing any of the other stupid tryhard marketing efforts that most coins do nowadays, is a pretty clear indicator that those are not what makes a coin grow.
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
April 12, 2014, 06:39:06 PM |
|
hobonickels appears to have accomplished what 99% of the other altcoins have not been able to: slow and steady price gains that don't seem to be in any danger of crashing back down. Kudos to Tranz! I think the fact that he hasn't been pushing the coin on every exchange under the sun, or doing any of the other stupid tryhard marketing efforts that most coins do nowadays, is a pretty clear indicator that those are not what makes a coin grow.
I think Tranz has taken the "if you build it they will come" approach, meaning that Tranz has done the building and lets other participants come add to the coin in other ways. Without a variety of people helping with the coin and a community, then a coin is nothing in my opinion. HBN has seen a lot of support from all types of people and that is what makes it strong.
|
|
|
|
unick
|
|
April 12, 2014, 07:05:55 PM |
|
Using this is ok. Best to create your own index, but this is safe enough. However you shouldn't replace your database directory, this is used for the wallet.dat. Just need the blk0001.dat and the leveldb directory. Those 2 are for the block chain. wallet.dat and database directory work for the wallet.dat I just learned something new about the file structure... thanks
|
|
|
|
|