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

[HCLivess]

I was once inspired by this commit, I wonder whether it is mergeable into HBN https://github.com/hyperstake/HyperStake/commit/3b253ac048b99f462a5ea181df3db037eac84d54
I am trying to look at the code, but it's quite hard for me. I would like real delays between block maturity, I get constant green arrow and attempts at stake, does split/combine help with this? 200/200 is certainly not enough.

[1714910210]

1714910210

[1714910210]

1714910210

[1714910210]

1714910210

[Tranz]

If whomever IPs this is, could you please PM me?

24.129.112.198

[screaming_trees]

I got my wallet to sync, it is really sluggish, but is synced. Is it supposed to be staking still? If not is there a command to stop staking?

[panpine]

I got my wallet to sync, it is really sluggish, but is synced. Is it supposed to be staking still? If not is there a command to stop staking?

In  the menu you can choose Stop staking ( wallet 1.5.5.5)

[PeterTheGrape]

I got my wallet to sync, it is really sluggish, but is synced. Is it supposed to be staking still? If not is there a command to stop staking?

In  the menu you can choose Stop staking ( wallet 1.5.5.5)

Whether staking or just synching, this is not really a coin you can leave the wallet running, it has always been like that, a very heavy wallet that uses a lot of resources and advances very slowly. It can take one day to synch one weeks worth of blocks. I've had hobonickels since almost the very beginning and I only use the wallet once every long while then put it back in storage.

[Tranz]

Hi everyone. I am sorry to report, there does appear to be an issue with the network.

There is eitehr some bug that is causing people to create their own chain, or it is an orphan attack.

Basically, there are wallets that are running their own chain. For those of us that are on the correct chain, we just ignore the bad blocks. But when a new wallet comes online and it ask for blocks, if they connect to the bad wallet(s) they also begin to propagate the bad chain.


You can see the block explorer has now began to get the bad chain .

5633463   3 hours 48 minutes    20.4 kB   100.901936 HBN   0.0041    Proof of Stake   <--   Bad
5633462   4 hours 18 minutes    20.4 kB   96.319193 HBN   0.0041    Proof of Stake   <-- Good

Never should a block wait more then 1 or 2 mins, let alone almost 30.


You can always tell if you are on the correct chain by running these 2 commands.

Code:

getinfo
{
"version" : "v1.5.5.4-g87b0f55-V1.5",
"protocolversion" : 70009,
[u][b]"blocks" : 5634393,[/b][/u]
"timeoffset" : -18,
"moneysupply" : 58921229.54781200,
"connections" : 7,
...
}

getcheckpoint

{
"synccheckpoint" : "45a8a0fa9c5f83d50dbe39cb21bf1bbc19b4809f3d2c92ad1ecd5a5089451606",
[u][b]"height" : 5634393,[/b][/u]
"timestamp" : "2017-09-05 21:36:01 UTC",
"data" : {
"parsed" : {
"version" : 1,
"hash" : "45a8a0fa9c5f83d50dbe39cb21bf1bbc19b4809f3d2c92ad1ecd5a5089451606"
},
"raw" : {
"data" : "0100000006164589505acd1ead922c3d9f80b419bc1bbf21cb39be0dd5835f9cfaa0a845",
"signature" : "304402200daecb0af88c43f3792f0d92ddb111eed05a98917a1703b9e28fb63c3825a8d502204584d18e8484855e17d9ad6710bc102b3ce5e7d1bff77a1e83c9580bd5769af2"
}
},
"policy" : "strict"
}

If these 2 do not match, you might as well shut off the wallet, your chain is only making it worse.

I don't know the reason yet, nor do I have a fix. I'll be investigating as much as possible. Sadly this is a very bad time, as work is very busy as is school and family.

[Digi7ech]

That's no good.
I just saw my wallet was unsync'd for about 4-5 days.

Could we get a list of approved/known nodes?

I've got quite a few and don't want to be attached to any bad ones if possible.

[HCLivess]

Are the old clients disconnected for sure?
Aren't there too many people generating PoS coins at the same time?

Switching a codebase might be the worst-case option

Code:


getinfo
{
"version" : "v1.5.5.5-g87b0f55-V1.5",
"protocolversion" : 70009,
"blocks" : 5633655,
"timeoffset" : -47,
"moneysupply" : 58886915.28573300,
"connections" : 18,
"walletversion" : 60002,
"balance" : 0.00000000,
"unspendable" : 0.00000000,
"wallets" : 2,
"tolbal-all-wallets" : ---,
"proxy" : "",
"ip" : ---,
"difficulty" : 0.15742026,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"errors" : ""
}

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

[versprichnix]

I will release version 1.5.5.5 here tonight or tomorrow that will disconnect bad clients. Pleas ensure you are at version least version 1.5.3+ or preferably at 1.5.5.4 (soon 1.5.5.5).

Could this be the reason? Are old versions creating their own chain?

[HCLivess]

I will release version 1.5.5.5 here tonight or tomorrow that will disconnect bad clients. Pleas ensure you are at version least version 1.5.3+ or preferably at 1.5.5.4 (soon 1.5.5.5).

Could this be the reason? Are old versions creating their own chain?

old versions get disconnected as expected.
technically right now i see someone made a longer but less difficult chain which can't win, just making a mess.
now it's ~800 blocks longer, perhaps initially much longer than main one.
lets hope all this resolves soon.

How is that possible? Isn't difficulty based on number of blocks?

[Tranz]

No not good. As I said I don't the for sure reason yet. But I do know this. These forks are happening when the difficulty is at the lowest. They would be very difficult if not impossible to happen if we had difficulty that was higher.

So here is my game plan.

I am going to issue an immediate fork, that I will need at least a good 5-10 of you that have good stakes to update right away.   This will turn off PoW and set the block time for PoS to 3 mins. I will also update the degrading percentage to offset this, so as the difficulty goes up, the percentage the stake reward goes down will only be changed a little.

We will let this new version burn in for a few weeks and if the issue still exists, and I haven't found the under lying reason. We will.... *sigh*.... look at a coin swap.......  But that is the last resort.

The fork will take some to code, hopefully I can have something ready by tomorrow or Thursday and have it take effect by Friday or Saturday.  So if you are able to, please stayed tuned I will need some nodes out there running 24/7 for a bit.

[Tranz]

I will release version 1.5.5.5 here tonight or tomorrow that will disconnect bad clients. Pleas ensure you are at version least version 1.5.3+ or preferably at 1.5.5.4 (soon 1.5.5.5).

Could this be the reason? Are old versions creating their own chain?

old versions get disconnected as expected.
technically right now i see someone made a longer but less difficult chain which can't win, just making a mess.
now it's ~800 blocks longer, perhaps initially much longer than main one.
lets hope all this resolves soon.

How is that possible? Isn't difficulty based on number of blocks?

This is not true. The longer chain right now is the correct chain.

"blocks" : 5634793,

The bad chain I see is currently at 5633693  almost 1k behind....

Edit:

Has anyone been connected for multiple days now that is not on the correct chain??  Every client I have connected is still on the right chain, even though they are all getting bad blocks.

[Tranz]

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.

[Tranz]

on the right chain now, not a problem to make it to any chain,
just need to know which one is right !
good nodes i see so far:

addnode=109.227.254.135:7372
addnode=188.61.212.220:7372
addnode=5.103.138.97:7372
addnode=178.68.74.93:7372

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

Best chain right now.
2017-09-06 00:12:42 SetBestChain: new best=81c8158a98331357e02c height=5634889 trust=87382706892653 blocktrust=16887504 date=09/06/17 00:11:10

[Tranz]

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

of course not, i love em suffer for their sins.
just a tip:
revert to earlier chain, before the fork,
restrict your wallet connections ONLY to good nodes
(on default port, showing the right starting height),
and sync up to the right chain.
when done reopen wallet to all connections.

actually it's not quick if you haven't a backup chain of no more than days ago

Well the .zip on hobonickels.info is pretty new. I will keep it updated as well.  Working on a bit of coding for 1.5.6 fork..

[Digi7ech]

Looks like I was on the bad chain.

Trimmed my nodes to the ones you listed and am reverting back to a 8/10 chain I had downloaded. Will see if it pulls onto the right one.

[CoinEraser]

on the right chain now, not a problem to make it to any chain,
just need to know which one is right !
good nodes i see so far:

addnode=109.227.254.135:7372
addnode=188.61.212.220:7372
addnode=5.103.138.97:7372
addnode=178.68.74.93:7372

Thank you for this Nodes.  
First i was on the wrong chain and full sync.
I closed my wallet and i delete my peers.dat and add this Nodes.
Now my wallet jumps to the right chain and orphan the wrong blocks from my wallet

[Tranz]

on the right chain now, not a problem to make it to any chain,
just need to know which one is right !
good nodes i see so far:

addnode=109.227.254.135:7372
addnode=188.61.212.220:7372
addnode=5.103.138.97:7372
addnode=178.68.74.93:7372

Thank you for this Nodes.  
First i was on the wrong chain and full sync.
I closed my wallet and i delete my peers.dat and add this Nodes.
Now my wallet jumps to the right chain and orphan the wrong blocks from my wallet

Good deal!

[Tranz]

Hey Everyone,

It's me again!

I got about 1/2 way done with the coding tonight for what I hope to be the last hard fork in a while.   But I believe this will give us the stable network we need.

Here is what I landed on. (Subject to changes or additions)

• Target Spacing goes from 30 seconds (effectively 20 seconds with PoW) to 3min 30 secs (effectively 3min with PoW).
• Lower Bound Interest rate goes from 10% to 20%.  So the lowest you will ever get is 20% yearly on any stake.
• Min Stake Age goes from 10 days to 1 day. So you can get your first stake faster.
• Stake Reward Degradation goes from cutting in half every 64x difficulty to cutting in half every 128x difficulty.
• PoW will contiune on until block 6million as per 1.5.3 fork code.

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!

[HCLivess]

I will release version 1.5.5.5 here tonight or tomorrow that will disconnect bad clients. Pleas ensure you are at version least version 1.5.3+ or preferably at 1.5.5.4 (soon 1.5.5.5).

Could this be the reason? Are old versions creating their own chain?

old versions get disconnected as expected.
technically right now i see someone made a longer but less difficult chain which can't win, just making a mess.
now it's ~800 blocks longer, perhaps initially much longer than main one.
lets hope all this resolves soon.

How is that possible? Isn't difficulty based on number of blocks?

This is not true. The longer chain right now is the correct chain.

"blocks" : 5634793,

The bad chain I see is currently at 5633693  almost 1k behind....

Edit:

Has anyone been connected for multiple days now that is not on the correct chain??  Every client I have connected is still on the right chain, even though they are all getting bad blocks.

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