Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 54. (Read 478852 times)

HoboNickels Version 2.0 is now live.  https://github.com/Tranz5/HoboNickels/releases/latest

Everyone must upgrade by block 5667000 or by Fri, 15 Sep 2017 21:00:00 which every comes sooner.

Changes in this version to create a more stable block chain with less resource usage include:

• Fixed issued where clients were creating own chain
• Block time changed to 2 mins.
• Min stake Age changed to 1 day
• Min stake reward set at 20% Yearly
• Stake will degrade over difficulty slower
• Old clients will be disconnected on Friday Sept 15

Upgrade can be very simple or slightly complicated depending on if you are on the correct chain.

To ensure you are on the correct chain, type the following commands in your debug console:


If these match or a very close you should be good to go. You can also check against what I post here using   If the hash value matches then you are golden. You will only have  close the client, replace the executable and start it back up.  Just check back here to ensure after the fork all is well.


If you are one of the unlucky souls that do not match the best chain. Here is what you should do.

1) close the current client.
2) download the block chain from HoboNickels.info http://hobonickels.info/HBNBlockChain.zip. Or resync the blockchain from scratch using version 2.0.
3) replace the contents of the .zip file, over your blk0001.dat blk0002.dat and remove/replace your txleveldb folder from %appdata%/HoboNickels directory. (This can be different on linux/mac systems)
4) remove the peer.dat from your  %appdata%/HoboNickels directory. (This can be different on linux/mac systems)
5) start the new 2.0 client up.
6) goto the debug window/console and type addnode IP add.

Depending on how long you were on the wrong chain, you may have to re scan your wallet to get the correct coins in place.  If this is necessary, start the client with -rescan option. This can take 6-24 hours depending on computer resources.

The current good IPs are: ( this list will be updated as I know them)
5.103.138.97
146.71.78.97
158.69.48.52
80.56.92.208
85.4.82.82


Current Best Chain: SetBestChain: new best=191c1bb7bfede5f89e64 height=5653023 trust=87703134339018 blocktrust=22162211 date=09/10/17 15:42:09

If you are in the midst of re-syncing the block chain, you should be fine to just replace the executable.

Question or Issue, let me know.

Thanks and happy staking!

Still working on completing the code and testing.

Current best block

SetBestChain: new best=86a96fd33a92abf5db96 height=5649275 trust=87640762736331 blocktrust=21518967 date=09/09/17 17:57:04

1.5.5.5 since two days, 1.5.5.3 before. Both have been working well. I'm compiling myself on ubuntu linux, version 14.04.5 LTO.

Can you tell me the wallet version you are using?
Im fine with the 1.5.5.5 wallet since more than 24hrs

Feeling a bit better tonight. I have a plan put together that should help out.

I am going to finalize the changes tonight and put out the executable, the fork will take effect very quickly, 24 hours or less.  I also believe I have a reason for the forking and a potential fix. I am hopeful this will help. I will also put out detailed instructions for those that need it.  If all goes well and everyone can get on this chain and stay on it. Then we should be good go and I will contact Cryptopia and get their feedback.

Please stay tuned!

Here is the best chain I know of right now.

SetBestChain: new best=eaff371bf47b0db67406 height=5646256 trust=87572632652924 blocktrust=20663627 date=09/08/17 23:19:30

So shapping up to be a bad day. No end in site for real work. And yes it looks like wallets are creating their own chains.


I am going to turn back on the checkpoint server as that seemed to help keep most wallets together.

7-09-08 03:17:34 SetBestChain: new best=8c0ca8d785485e6d50ae height=5642854 trust=87513099890830 blocktrust=18179455 date=09/08/17 03:17:12

I will try to push out the changes and a updated checkpoint as soon as possible..

I gotta get off for now. 15 hrs in front of computer.

Tranz, can you supply a block height and txid on the right chain again, just so we know we're following the correct fork while we wait on the market?

So we have been on the wrong chain for around 12 hours. But what made it fork?

I follow this thread thoroughly and test every hint on a correct chain.

My :

2017-09-07 18:13:47 SetBestChain: new best=140c9288ecc057cf6a3a height=5641411 trust=87487983537864 blocktrust=16865485 date=09/07/17 18:11:37
2017-09-07 18:13:47 ProcessBlock: ACCEPTED


Same chain 

Yesterday i downloading from hobonickels.info and delete peers.dat

Me 2


I have only 4 connections :

Minting is becoming better. Can anybody commit about the right block chain high?

On the new fork (nearly?) all my new minted blocks become orphaned.

I'm downloading the blockchain from hobonickels.info now, and try again.

My debug.log about this:

Something strange is going on at this time. My wallet was staking until block 5641297. Now somebody overtook with a new fork going to block 5641537, letting a lot of orphanes in my wallets. All my minted coins become orphaned starting from 12 hours before. My block high is on 5641537 now.

And another phenomenon: Before the "current PoS netweight" was around 200000, now it is around 400000. So we have two coexisting competing chains? (I remind some days before we had a "current PoS netweight" of around 800000 and more, so one chain in consent?)

Nice i have @5634940 "hash" : "e841471edd89b909856300729b328330dc6967acf6e6b828be07494ef3376e17"

Now i have nodes :
92.30.44.22:7372
[2001:0:9d38:6abd:38fe:22cc:e02c:118]:7372
98.213.69.205:7372

you got no choice really, cryptopia wont allow withdrawls on wallets under investigation.

however, as a general rule of thumb, you dont want to keep (larger amounts of) staking type currencies on exchanges since they dont pay you any of the stake they may earn.

HBN / BTC market is paused Investigating network fork, markets are paused pending outcome of investigation.
is it okay to hold my HBN on cryptopia and wait until the market active again?

My current block is 5641035 (and I'm luckily got the hash above with command "getblockbynumber")

Yep, the cryptoID BE is on the wrong chain.

Compair the blocks from your wallet with this:

Right chain:
Block: 5634940
Block Hash: e841471edd89b909856300729b328330dc6967acf6e6b828be07494ef3376e17
Block Timestamp: 2017-09-06 00:26:17 UTC

Wrong chain (cryptoid)
Block: 5634940
Block Hash: 40ae60351b69a7ebd87d5a50898d5a818f58cc66dc5ca292c258e2bf317326c8
Block Timestamp: 2017-09-07 11:32:37

At the time writting, we are at block 5640899
As you can see the cryptoid BE is about 5959 Blocks behind the valid chain.