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

[dnp]

I will need another 1 to 3 days to finish the code and run it on testnet.  Then I plan to have only about 7 to 10 days lead time before the fork will take place. So it will be quick! Hopefully the pain will only last for a short time.

Stay tuned!

do you need any other testnet nodes? either passive or with light solo mining?
perhaps some initial less-light solo mining to get some coins for staking
i could put one on up my 24/7 linux server
i could also put one on my evenings windoze machine and randomly send coins between the too as well.

i could run older versions for compatibility/conflict testing or your most recent development, whatever helps most.

[1714143161]

1714143161

[1714143161]

1714143161

[1714143161]

1714143161

[Tranz]

I am on the wrong fork 5633965 - running all day, every day and not rolling back. I am one of the port-forwarded nodes many people have in their config

Thank you. Did you start on the right chain? Or maybe just started on the wrong chain and didn't realize it? Are you good now?

[HCLivess]

I am on the wrong fork 5633965 - running all day, every day and not rolling back. I am one of the port-forwarded nodes many people have in their config

Thank you. Did you start on the right chain? Or maybe just started on the wrong chain and didn't realize it? Are you good now?

I replaced the chain with the one you provided right after the upgrade to the latest version
I have now replaced the peers with those someone suggested above

I'm not sure, I think I'm still forked. I thought it would reorganize. I will redownload your chain.


{
"version" : "v1.5.5.5-g87b0f55-V1.5",
"protocolversion" : 70009,
"blocks" : 5634186,
"timeoffset" : -2,
"moneysupply" : 58889629.65486800,
"connections" : 12,
"walletversion" : 60002,
"balance" : 0.00000000,
"unspendable" : 0.00000000,
"wallets" : 2,
"tolbal-all-wallets" : 606719.46075500,
"proxy" : "",
"ip" : "94.113.207.67",
"difficulty" : 0.15742026,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"errors" : ""
}



{
"synccheckpoint" : "436d8a36d77242488b7b75a9687917f3cf29fe59025a72022d89f0ba8933d44e",
"height" : 5632990,
"timestamp" : "2017-09-05 14:30:00 UTC",
"policy" : "strict"
}

[Digi7ech]

Just check mine. So if the height & blocks from getinfo and getcheckpoint are not the same, then we're on the wrong chain?

I'm going to shut mine down just in case. Looks like I went onto bad fork.

version" : "v1.5.5.4-g87b0f55-V1.5",
"protocolversion" : 70009,
"blocks" : 5637984,
"timeoffset" : -56,
"moneysupply" : 59058072.47927100,
"connections" : 42,

///////////////

synccheckpoint" : "baadf099eeb5430eb92600ca4426fbb6b1e12ea49c44316eb1d41e3416f86fc2",
"height" : 5634827,
"timestamp" : "2017-09-05 23:53:08 UTC",
"data" : {
"parsed" : {
"version" : 1,
"hash" : "baadf099eeb5430eb92600ca4426fbb6b1e12ea49c44316eb1d41e3416f86fc2"
},
"raw" : {
"data" : "01000000c26ff816341ed4b16e31449ca42ee1b1b6fb2644ca0026b90e43b5ee99f0adba",
"signature" : "304402205e4b0b13ab14903b5076f44e0e70a76d97ab36867335313b6b2389d8695295fd02207ef 46f989cfb7285eae7638f53843f7dd675d5d740775509862db8ca76eb5010"
}
},
"policy" : "strict"

[PeterTheGrape]

Can you share for others how you quickly jumped to the right chain?

of course not, i love em suffer for their sins.
...

aaargh, pirate bastards

[Zels]

cryptopia message:

Code:

HBN / BTC market is paused

Investigating network fork, markets are paused pending outcome of investigation.


{
"version" : "v1.5.3.0-gf46fa0c-V1.5",
"protocolversion" : 70008,
"blocks" : 5638119,
"timeoffset" : 0,
"moneysupply" : 59061796.09772400,
"connections" : 29,
"wallets" : 1,
"walletversion" : 60001,
"proxy" : "",
"ip" : "xxxxx",
"difficulty" : 0.53295220,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"errors" : ""
}

I'm on the right one ?

[HCLivess]

I started with Tranz's chain and hopefully synced to the right fork

18:16:49

{
"version" : "v1.5.5.5-g87b0f55-V1.5",
"protocolversion" : 70009,
"blocks" : 5638153,
"timeoffset" : -31,
"moneysupply" : 59062333.61715300,
"connections" : 52,
"walletversion" : 60002,
"balance" : 0.00000000,
"unspendable" : 0.00000000,
"wallets" : 2,
"proxy" : "",
"ip" : "94.113.207.67",
"difficulty" : 0.54625701,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"errors" : ""
}


18:16:59

getcheckpoint


18:16:59

{
"synccheckpoint" : "baadf099eeb5430eb92600ca4426fbb6b1e12ea49c44316eb1d41e3416f86fc2",
"height" : 5634827,
"timestamp" : "2017-09-05 23:53:08 UTC",
"data" : {
"parsed" : {
"version" : 1,
"hash" : "baadf099eeb5430eb92600ca4426fbb6b1e12ea49c44316eb1d41e3416f86fc2"
},
"raw" : {
"data" : "01000000c26ff816341ed4b16e31449ca42ee1b1b6fb2644ca0026b90e43b5ee99f0adba",
"signature" : "304402205e4b0b13ab14903b5076f44e0e70a76d97ab36867335313b6b2389d8695295fd02207ef 46f989cfb7285eae7638f53843f7dd675d5d740775509862db8ca76eb5010"
}
},
"policy" : "strict"
}

[2xjO9M3P]

FYI I have turned off the checkpoint server for now.

Here are nodes that are on the right chain.

178.68.74.93:7372
109.227.254.135:7372
188.61.212.220:7372
[2001:0:9d38:6abd:38fe:22cc:e02c:118]:7372
178.248.4.130:7372
176.37.67.61:7372
5.103.138.97:7372
83.255.67.196:7372
94.143.245.5:7372


More as I find them.

This is confusing. My IP is on that list, but there's a rather large discrepancy (~3k blocks) on blockheight between getinfo and getcheckpoint.
Running 1.5.5.5, and my wallet has been online for the past 7~8 days non-stop

[lightspeedy]

Sad to hear this troubles.
I just closed my wallet and deleted the peer.dat file.
Made a new HoboNickels.conf file with the good nodes.

The current get info state:

Code:

getinfo
{
"version" : "v1.5.5.5-g87b0f55-V1.5",
"protocolversion" : 70009,
"blocks" : 5638860,
"timeoffset" : 2,
"moneysupply" : 59073379.12164500,
"connections" : 35,
"walletversion" : 60002,
"unspendable" : 0.00000000,
"wallets" : 1,
"proxy" : "",
"difficulty" : 0.32301550,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"errors" : ""
}

Hope i got the right chain.

[Tranz]

Hey everyone

So I said it yesterday, but I should say it again. I turned off the checkpoint server. So no new checkpoints right now. I wanted to eliminate as an issue, which is why it is off.

The best chain right now is:

ProcessBlock: ACCEPTED
setBestChain: new best=7adad1658be0dc68995b height=5639170 trust=87451079147069 blocktrust=16914002 date=09/06/17 21:48:11

You can check to make sure you match via the built in block explorer or getblockbynumber rpc.

I have messaged the explorer, to see if he can update at some point soon. But since it went bad once, it could again.

I should have the code done tonight and start testing tonight and up through tomorrow.

I talked to my friend at work, we thought 2 minutes and 10 seconds was a good block time.  So that is what I am going to set it as.

[HCLivess]

Hey everyone

So I said it yesterday, but I should say it again. I turned off the checkpoint server. So no new checkpoints right now. I wanted to eliminate as an issue, which is why it is off.

The best chain right now is:

ProcessBlock: ACCEPTED
setBestChain: new best=7adad1658be0dc68995b height=5639170 trust=87451079147069 blocktrust=16914002 date=09/06/17 21:48:11

You can check to make sure you match via the built in block explorer or getblockbynumber rpc.

I have messaged the explorer, to see if he can update at some point soon. But since it went bad once, it could again.

I should have the code done tonight and start testing tonight and up through tomorrow.

I talked to my friend at work, we thought 2 minutes and 10 seconds was a good block time.  So that is what I am going to set it as.

Amazing work dedication, thank you. These practical blockchain troubleshooting lessons are invaluable for me to see how things are operating, thanks.

[Tranz]

Here is where we sit for the night.

SetBestChain: new best=5e8a9295764aee17972a height=5640234 trust=87468177711117 blocktrust=17106897 date=09/07/17 03:30:16

So the BE is almost 6k off this chain. I only see a handful on the bad chain yet.

Once I get the newest version 1.5.6 out I will send high status alerts to all of the old wallets.

[Turrican]

The cryptoid explorer is on the wrong chain ?

[lightspeedy]

The cryptoid explorer is on the wrong chain ?

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.

[versprichnix]

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

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

[matsud2]

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?

[dnp]

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?

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.

[Turrican]

The cryptoid explorer is on the wrong chain ?

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.

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

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

[versprichnix]

My debug.log about this:

2017-09-07 19:26:51 SetBestChain: new best=f0c5046a3573f2c13d9f height=5641297 trust=87484931879282 blocktrust=16777472 date=07.09.2017 19:25:52
2017-09-07 19:26:51 ProcessBlock: ACCEPTED
2017-09-07 19:27:40 connect() failed after select(): Connection refused
2017-09-07 19:27:57 ProcessBlock: ORPHAN BLOCK, prev=4d38acbf11f3ade83235
2017-09-07 19:27:58 connect() failed after select(): Connection refused
2017-09-07 19:27:58 ProcessBlock: ORPHAN BLOCK, prev=f1fd8827aefec67707f7
2017-09-07 19:27:58 ProcessBlock: ORPHAN BLOCK, prev=5f28f283aab3f6bc2cf6
...
2017-09-07 19:27:59 ProcessBlock: ORPHAN BLOCK, prev=2a2dccadcb2e7f45e050
2017-09-07 19:28:00 ProcessBlock: ORPHAN BLOCK, prev=5f043680bbce2b736983
2017-09-07 19:28:00 ProcessBlock: ACCEPTED
2017-09-07 19:28:00 ProcessBlock: ACCEPTED
...
2017-09-07 19:28:25 ProcessBlock: ACCEPTED
2017-09-07 19:28:25 ProcessBlock: ACCEPTED
2017-09-07 19:28:25 ProcessBlock: ORPHAN BLOCK, prev=56adecaa2cea4bb8100a
2017-09-07 19:28:27 ProcessBlock: ORPHAN BLOCK, prev=a8807cfb941cb6d0a6e3
...
2017-09-07 19:28:30 ProcessBlock: ORPHAN BLOCK, prev=962f7175e52a55574a01
2017-09-07 19:28:32 ProcessBlock: ORPHAN BLOCK, prev=95b7f47174192440a6f1
2017-09-07 19:28:33 ProcessBlock: ACCEPTED
2017-09-07 19:28:33 ProcessBlock: ACCEPTED
...
2017-09-07 19:28:36 ProcessBlock: ACCEPTED
2017-09-07 19:28:36 ProcessBlock: ACCEPTED
2017-09-07 19:28:36 REORGANIZE
2017-09-07 19:28:36 REORGANIZE: Disconnect 663 blocks; 45f2528da281f7f3a6fd..f0c5046a3573f2c13d9f
2017-09-07 19:28:36 REORGANIZE: Connect 596 blocks; 45f2528da281f7f3a6fd..441665893f718ec05b59
2017-09-07 19:28:41 ERROR: FetchInputs() : 084844ec98 mempool Tx prev not found f15bd6564b
2017-09-07 19:28:41 ERROR: FetchInputs() : dd99ec4ac6 mempool Tx prev not found f15bd6564b
2017-09-07 19:28:41 ERROR: FetchInputs() : fd131759dc mempool Tx prev not found 1202d1b1f7
2017-09-07 19:28:41 ERROR: FetchInputs() : dd5bb3a956 mempool Tx prev not found 09785011f3
2017-09-07 19:28:41 REORGANIZE: done
2017-09-07 19:28:42 SetBestChain: new best=441665893f718ec05b59 height=5641230 trust=87484942373298 blocktrust=16777472 date=07.09.2017 16:13:06
2017-09-07 19:28:44 SetBestChain: new best=794d95dc8529ad663b04 height=5641231 trust=87484959172815 blocktrust=16799517 date=07.09.2017 16:14:27
...
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