HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive

[versprichnix]

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

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

[1713484921]

1713484921

[1713484921]

1713484921

[1713484921]

1713484921

[1713484921]

1713484921

[1713484921]

1713484921

[1713484921]

1713484921

[versprichnix]

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

[Turrican]

Me 2

Code:

2017-09-07 20:23:42 SetBestChain: new best=b9d50cdbe6e6cebcc199 height=5641665 trust=87492255176444 blocktrust=16801828 date=09/07/17 20:22:36
2017-09-07 20:23:42 ProcessBlock: ACCEPTED
2017-09-07 20:23:47 SetBestChain: new best=2d82d2926bc9d6468a8d height=5641666 trust=87492271997807 blocktrust=16821363 date=09/07/17 20:23:37
2017-09-07 20:23:47 ProcessBlock: ACCEPTED
2017-09-07 20:24:14 ProcessBlock: ORPHAN BLOCK, prev=000ca911f875f19d2fec
2017-09-07 20:24:15 REORGANIZE
2017-09-07 20:24:15 REORGANIZE: Disconnect 1 blocks; b9d50cdbe6e6cebcc199..2d82d2926bc9d6468a8d
2017-09-07 20:24:15 REORGANIZE: Connect 2 blocks; b9d50cdbe6e6cebcc199..d26884a6649b630d32b1
2017-09-07 20:24:15 REORGANIZE: done
2017-09-07 20:24:16 SetBestChain: new best=d26884a6649b630d32b1 height=5641667 trust=87492288858379 blocktrust=16860572 date=09/07/17 20:23:13
2017-09-07 20:24:16 ProcessBlock: ACCEPTED
2017-09-07 20:24:38 SetBestChain: new best=73b5f29073d0cb7e6903 height=5641668 trust=87492305736291 blocktrust=16877912 date=09/07/17 20:24:20
2017-09-07 20:24:38 ProcessBlock: ACCEPTED
2017-09-07 20:25:11 SetBestChain: new best=1d95ce0830dc660f13a3 height=5641669 trust=87492322524522 blocktrust=16788231 date=09/07/17 20:24:25
2017-09-07 20:25:11 ProcessBlock: ACCEPTED
2017-09-07 20:25:17 ProcessBlock: ORPHAN BLOCK, prev=d7c711c807648edfc424
2017-09-07 20:25:18 REORGANIZE
2017-09-07 20:25:18 REORGANIZE: Disconnect 2 blocks; d26884a6649b630d32b1..1d95ce0830dc660f13a3
2017-09-07 20:25:18 REORGANIZE: Connect 2 blocks; d26884a6649b630d32b1..5b98d92cfb9643ce1c03
2017-09-07 20:25:18 REORGANIZE: done
2017-09-07 20:25:19 SetBestChain: new best=5b98d92cfb9643ce1c03 height=5641669 trust=87492322643790 blocktrust=16907499 date=09/07/17 20:24:50
2017-09-07 20:25:19 ProcessBlock: ACCEPTED

I have only 4 connections :

Code:

{
"addr" : "92.30.44.22:7372",
"services" : "00000001",
"lastsend" : 1504816066,
"lastrecv" : 1504816067,
"conntime" : 1504805820,
"pingtime" : 0.10938100,
"bytessent" : 128484,
"bytesrecv" : 230029,
"blocksrequested" : 3,
"version" : 70008,
"subver" : "/HoboNickels:1.5.3/",
"inbound" : false,
"startingheight" : 5641353,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "98.213.69.205:7372",
"services" : "00000001",
"lastsend" : 1504816068,
"lastrecv" : 1504815824,
"conntime" : 1504805866,
"pingtime" : 747.32437500,
"pingwait" : 254.74630200,
"bytessent" : 510493,
"bytesrecv" : 38644,
"blocksrequested" : 120,
"version" : 70009,
"subver" : "/HoboNickels:1.5.5.5/",
"inbound" : false,
"startingheight" : 376172,
"banscore" : 0
},
{
"addr" : "178.248.4.130:7372",
"services" : "00000001",
"lastsend" : 1504816068,
"lastrecv" : 1504816049,
"conntime" : 1504810542,
"pingtime" : 213.99438800,
"pingwait" : 29.26699700,
"bytessent" : 2202050,
"bytesrecv" : 162905,
"blocksrequested" : 3346,
"version" : 70009,
"subver" : "/HoboNickels:1.5.5.5/",
"inbound" : false,
"startingheight" : 2240149,
"banscore" : 0
},
{
"addr" : "85.201.244.230:7372",
"services" : "00000001",
"lastsend" : 1504816068,
"lastrecv" : 1504816068,
"conntime" : 1504815438,
"pingtime" : 0.14062400,
"bytessent" : 7979,
"bytesrecv" : 14568,
"blocksrequested" : 9,
"version" : 70008,
"subver" : "/HoboNickels:1.5.3/",
"inbound" : false,
"startingheight" : 5641649,
"banscore" : 0
},
{
"addr" : "24.4.200.90:7372",
"services" : "00000000",
"lastsend" : 1504816054,
"lastrecv" : 0,
"conntime" : 1504816054,
"pingtime" : 0.00000000,
"bytessent" : 130,
"bytesrecv" : 0,
"blocksrequested" : 0,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0
}

[Turrican]

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

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

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

[Turrican]

My debug.log about this:

...
2017-09-07 19:33:28 SetBestChain: new best=1216ddded51dd9523c0e height=5641410 trust=87487966672379 blocktrust=16865485 date=07.09.2017 18:10:15
2017-09-07 19:33:30 SetBestChain: new best=140c9288ecc057cf6a3a height=5641411 trust=87487983537864 blocktrust=16865485 date=07.09.2017 18:11:37[/tt]

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 

[versprichnix]

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.

[vancefox]

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?

[Tranz]

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]

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.

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

[lightspeedy]

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?)

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

[versprichnix]

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?)

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

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.

[Tranz]

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

[Tranz]

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:

Code:

getcheckpoint

"height" : 5651019,

Code:

getblockcount

5651019

If these match or a very close you should be good to go. You can also check against what I post here using  

Code:

getblockbynumber 5651019

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!

[2xjO9M3P]

Code:

master@miranda:~$ hobonickelsd getinfo
{
    "version" : "v2.0.0.0-g-V2.0",
    "protocolversion" : 70010,
    "blocks" : 5651145,

So far so good.

[Zels]

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

[Tranz]

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

No all coins, but doesn't effect until after the block 5667000 .

Best hash right now:
SetBestChain: new best=ef68f741ec495654d34e height=5652466 trust=87692314699589 blocktrust=19509069 date=09/10/17 12:34:29

[lightspeedy]

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

No all coins, but doesn't effect until after the block 5667000 .

Best hash right now:
SetBestChain: new best=ef68f741ec495654d34e height=5652466 trust=87692314699589 blocktrust=19509069 date=09/10/17 12:34:29

Thanks for all your hard work, Tranz! 

Updated the Client from v1.5.5.5 > v2.0.0 an everything went smooth.
At the time writing my client is connected to 5 v2.0.0 clients already. Total connected peers are 23 with < v2.00

Current PoS Difficulty: 0.00468566
Current PoS Netweight: 936376

I had recently lot of orphans, but i guess this had to do with the chain issues.

[Tranz]

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

No all coins, but doesn't effect until after the block 5667000 .

Best hash right now:
SetBestChain: new best=ef68f741ec495654d34e height=5652466 trust=87692314699589 blocktrust=19509069 date=09/10/17 12:34:29

Thanks for all your hard work, Tranz! 

Updated the Client from v1.5.5.5 > v2.0.0 an everything went smooth.
At the time writing my client is connected to 5 v2.0.0 clients already. Total connected peers are 23 with < v2.00

Current PoS Difficulty: 0.00468566
Current PoS Netweight: 936376

I had recently lot of orphans, but i guess this had to do with the chain issues.

I am sending out alerts this morning, so that should get more people on the right version.

Orphans should be much lower after the changes take effect.

In the mean time you can try to stop client, remove or rename peers.dat and add 1 or 2 peers you know are good..  Don't have to do it, but it may help. 

[HCLivess]

Yes, yes, YES, you're a hero!
Can I send you some Bismuth? PM me your adress, we now even have a web wallet https://biswallet.acc-pool.pw/index.php

[johnnarmst]

Perfect site for trading online for both newbies and well experienced traders.