I am looking into the Min stake issue.  I will let you know what I find out.

You can see in coin control, the coins that are 1 day old and greater have weight. So they can stake. But with the higher difficulty can take a while to stake.   I'll try to find an example to ensure it is working correctly.

Sorry Zels If it makes you feel any better I had to do 2 rescans due to development issues. Lost 5 hours waiting for it. After the rescan, shouldn't have to do a repair, but won't hurt.

Thank you!!

The only person you were connected to was
"addr" : "51.175.41.140:55253",
"services" : "00000001",
"lastsend" : 1505512355,
"lastrecv" : 1505512353,
"conntime" : 1505480629,
"pingtime" : 78.02846300,
"bytessent" : 55657742,
"bytesrecv" : 13262893,
"blocksrequested" : 306,
"version" : 70010,
"subver" : "/HoboNickels:2.0.0/",
"inbound" : true,
"startingheight" : 5641272,
"banscore" : 0
},

Everyone else was just in a block download initialization . So you guys started creating your own chain with no one else there to tell it was not right.  Again I suspect when the fork started up, many clients struggled due to many blocks to quickly, you got caught up on that. I think a fresh re-sync form the last good backup should be good.

 

I assume you might have started on the bad chain? Or got forked off right at the beginning when there was much strife on the network.
In any event I would suggest turning off wallet. Removing Peers.dat downloading the blockchain and txlevel from hobonickels.info and start up with connections from cryptopia or from Explorer.

Also before you go can you type getpeerinfo in console and send it to me.

That is up to them. I am still solo mining it. With a single GAW Miner.

On another note the 2nd part of the Fork has now taken place. The PoS Difficulty is now at 1.7 and the PoS % is about 36% right now. So I think that is a bit lower then anticipated or wanted, but for now that is what we have.

It should fluctuate between 30 and 50% for a while as people come and go on the network.

No I think you are good. Just double check against the block explorer.  Did you get the getcheckpoint while catching up?

Let's give 2.0 a full week to burn in and then assuming all is well I will go ahead and start a conversation with them.

This is a thing of beauty though.

Love the ping times!

20% is the min. But with the 250 reward cap, this will continue to go down over time. As more coins are available, the difficulty will go up, and the amount of coins needed, or the length of time need will go up and you will hit the max.  This will take years to happen, but it will slow down more and more over time. And we will hopefully get close to that 120 million goal..

I think we will be in good shape, still high enough to allow new comers  to start, but not so high as to cause run-away inflation.


Thank you, this can be different for different compilers. What system were you compiling for?



Awesome!

So let's recap how we are looking.

The fork seems to have gone as planned, although it seems there was a bit of strife right after it became active. But otherwise the chain appears to be in good shape.  

I am seeing a very low orphan rate, and low CPU usage, and so far no side chains. So that is good!  

Spacing and difficulty appear to leveling out too.


I think the amount  of clients on the network is a bit low right now. But that should increase and get back to normal over time.

The reward is a bit lower then I anticipated, but we still have the change at Friday Night that should bring it back up.  I am guessing 40-60%. We shall see.

The Min reward is going to be at 20%, so no matter what happens to difficulty that will be the lowest you will earn.  Now the max reward cap is also staying at 250, so again over time the amount of coins it will take to stake will increase over time. There by continuing to lower the creation percentage for the block chain.  This will take many years to get to that point.    

In any even this is how this coin should have behaved from the start. But the 20 second block time was just too much for a global network of wallets that were also staking.  

So what is next?

Now that we have a stable network. I will have to spend less time ensuring the block chain is whole, and more time to development.

Immediate Goals:
Get a client out there for other platforms. Mac and Linux right away.  I would love help on the Mac wallet..
Get Cryptopia back online. I don't plan to push this until next week, after everything looks safe and sound.
Update the code to allow for higher, potentially unlimited combine/split threshold values.

Short/Medium term Goals:
Continue to update the code base for more security and lower cpu, lower memory, fix bugs and compiling issues and lots more functionality!

Longer Term Goals:
Hard Forks? Not sure what we will need yet, but anything will be 6-12 months out at this point.
Create a light weight wallet. Electrum type.  With eventual staking capabilities. Very low foot print.
Lots of other ideas I will share later.

But all of this is now possible because we moved to a reasonable block time and decent staking algo.

The section of the code that changes the reward won't take effect until Friday Sept 15.The reward should move back up then.


That is the minimum. The max is still 100% The current amount will depend on difficulty.  I suspect after the 2nd part of the Fork comes in to play we will move back to the 70% range.

250 is still the cap.

Do you have the full debug.log file? Can you upload it somewhere for me? Encrypt it if you want..

How many connection did you have? Were they older clients?  Did you compile yourself or use my download?
 
For now turn off your wallets and hang tight. I will get a fresh copy of the blockchain as soon as the fork takes place.  You can use that to get back up to speed quickly.


This is just a PoW block. The difficulty is low.


Just no connection to those nodes.
You can try a few others.
109.227.254.135
71.126.179.61
87.98.159.143


The fork is about 4k away. So I think we are looking about this time if not a little later tomorrow night. Stay vigilant. If you are not on the right chain, just shut off and wait. I will help you get right once the fork takes place.  I have 4 clients running and watching the block explore. All have been doing very well so far. I think after the fork, these side chains should be a thing of the past... Well I hope at least..

Looks like maybe?
https://chainz.cryptoid.info/hbn/block.dws?36874e4b721cb0b91f2263c9f4f0f103cea59aba91f59f6739fa0dbd873aea7c.htm

Let me know when you have time.
Version 2.0? How many peers?   Were you on right chain before 2.0? or after?

Might be best to shut down wallet until you can look.

Edit: Are these you?

Blocks coming in fast and furious!  We are only 8,500 blocks away from the first part of the fork.


So far the network seems to be hold together just fine.. Does anyone see anything different?

Thank you.  Let's wait until a week or two after the fork takes effect, before we celebrate.

I am still seeing lots of orphan blocks, so side chains may still getting created.   Such as these:

Do these belong to anybody?


Now granted I am still allowing the older clients on the chain until Sept 15.  After then I expect to see less and less of this type of thing.

BTW the Block Explorer is now on the right chain.  

But for the next 2 weeks we need to be vigilant.  If you do NOT match the BE then either you or it is wrong.  If that is the case then double check your block vs the checkpoint block. If you are wrong, best to remove turn off your wallet and get right..

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. 

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

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!