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

[lightspeedy]

the fork point (last block identical in both chains) is 5938411, time Aug 13, 2018 23:08:20 GMT
for those who want to jump on cryptopia chain:
close wallet, backup your chain and your conf file,
roll back your chain to any state before the fork time (use any snapshot you're confident in),
restrict your connections in conf this way (only temporary!):
connect=23.233.2.252
listen=0
sync up, restore conf file, restart

P.S. i hate checkpoint servers

Can you please explain how to rollback the chain within the hobonickels wallet?
Would much appreciate it.
thanks

"rollback" simply means you replace your chain data with a snapshot dated back enough,
i believe an official one is here:
http://hobonickels.info/HBNBlockChain.zip

Thanks for explaining. Tought there is a feature that i missed out. ** FOMO 


Happy Tranz is here to help. Hope we get this glitch fixed witout interruption of cryptopia.

[1713891501]

1713891501

[Tranz]

The checkpoint server is now up and running on the following chain.

2018-08-14 23:05:31 SetBestChain: new best=000000351e1028c9358d height=5939094 trust=4072614652097797 blocktrust=69 date=08/14/18 23:04:15

I am working on a block chain download right now. But it will be a few hours before it is ready.

[Tranz]

While it is getting ready. You can revert to your own older copy and do the following.

rename peers.dat to peers.dat_old

and set your conf file to these nodes

connect=89.236.137.142:7372
connect=69.197.188.186:7372
connect=77.121.153.138:7372
connect=88.110.55.193:7372

Then after you are caught backup and up to speed with the checkpoint (getinfo should equal getcheckpoint)

Then you can shutdown and and restart without the connect nodes.

[B3dr0ck]

so how can you tell if your on the correct chain?

getinfo shows the block height, but thats about it.  Looks like i'm close to being on the correct chain.

[Sam123]

How do I know if I'm in the correct chain

I did exactly what Tranz recommend: and I got


getcheckpoint
"height" : 5939276

getinfo
"blocks" : 5939276

[B3dr0ck]

How do I know if I'm in the correct chain

I did exactly what Tranz recommend: and I got


getcheckpoint
"height" : 5939276

getinfo
"blocks" : 5939276

well the blocks are gonna change every 30secs?  (I don't remember the block time)  Just as long as the checkpoint and the block count from getinfo match?  Is that what Im looking for?

[Tranz]

How do I know if I'm in the correct chain

I did exactly what Tranz recommend: and I got


getcheckpoint
"height" : 5939276

getinfo
"blocks" : 5939276

well the blocks are gonna change every 30secs?  (I don't remember the block time)  Just as long as the checkpoint and the block count from getinfo match?  Is that what Im looking for?

yes pretty much.

You can also check to make sure that block 5939314 has a hash value of 000000000e135c69438581060c15d5c616bee04475df7811b8f957d149e9a1f5 via the block browser or the rpc call.

[Sam123]

How do I know if I'm in the correct chain

I did exactly what Tranz recommend: and I got


getcheckpoint
"height" : 5939276

getinfo
"blocks" : 5939276

well the blocks are gonna change every 30secs?  (I don't remember the block time)  Just as long as the checkpoint and the block count from getinfo match?  Is that what Im looking for?

yes pretty much.

You can also check to make sure that block 5939314 has a hash value of 000000000e135c69438581060c15d5c616bee04475df7811b8f957d149e9a1f5 via the block browser or the rpc call.

Yes
Thanks,

[dnp]

How do I know if I'm in the correct chain

I did exactly what Tranz recommend: and I got


getcheckpoint
"height" : 5939276

getinfo
"blocks" : 5939276

LOL. my OCD is twitching that its called 'height' in one place and 'blocks' in another.
inconsitent labelling. ow ow ow ow!

[dnp]

the fork point (last block identical in both chains) is 5938411, time Aug 13, 2018 23:08:20 GMT
for those who want to jump on cryptopia chain:
close wallet, backup your chain and your conf file,
roll back your chain to any state before the fork time (use any snapshot you're confident in),
restrict your connections in conf this way (only temporary!):
connect=23.233.2.252
listen=0
sync up, restore conf file, restart

P.S. i hate checkpoint servers

blush, that's my IP
my 24/7 hobo daemon.

however, my ip number does change every couple months, better to use
addnode (or connect)=coins.dognose.net

names, not numbers.

[B3dr0ck]

can someone help me out with mining HBN?

it has been about 6 years since I've solo mined a coin, and I dont want to piece it all together.  This is what I'm thinkin

1 - I create a .conf file - but i'm not sure what its name is supposed to be.  wallet.conf, hobonickle.conf ?
2 - I put the RPC information in there - the u/n p/w port and IP address
3- Then I point the Asic to the local IP address of the QT wallet, with the u/n p/w and port number

Is that it?

Might help stabilize the network some, and there's another 61K blocks until POW goes away, so ... why not.

[CoinEraser]

The checkpoint server is now up and running on the following chain.

2018-08-14 23:05:31 SetBestChain: new best=000000351e1028c9358d height=5939094 trust=4072614652097797 blocktrust=69 date=08/14/18 23:04:15

I am working on a block chain download right now. But it will be a few hours before it is ready.

Thank you Tranz for your work. Now everything seems to be going right again. Well it was not an attack and only the checkpoint server.  

can someone help me out with mining HBN?

it has been about 6 years since I've solo mined a coin, and I dont want to piece it all together.  This is what I'm thinkin

1 - I create a .conf file - but i'm not sure what its name is supposed to be.  wallet.conf, hobonickle.conf ?
2 - I put the RPC information in there - the u/n p/w port and IP address
3- Then I point the Asic to the local IP address of the QT wallet, with the u/n p/w and port number

Is that it?

Might help stabilize the network some, and there's another 61K blocks until POW goes away, so ... why not.

If I'm not mistaken, the .conf filename must be hobonickles.conf. I believe the rest you have done so far right.  

[poke@]

Am I on a different chain for the 3rd time? Jesus what is going on. I keep going from a snapshot back in march and it keeps updating to a different chain than chainz. Is chainz correct?

It is at  5940110
I am at 5939314

At what point am I getting off track? Gonna try it again with a new conf and no peers.dat I guess

[Tranz]

Sorry took so long. For those that are having trouble, please do the following.

#1 Shutdown the client
#2 Goto your %appdata%/HoboNickels folder
#3 rename peers.dat to peers.dat_old
#4 rename or delete blk0001.dat, blk0002.dat and folder txleveldb
#5 Download the blockchain bootstrap here https://hobonickels.info/HBNBlockChain.zip
#6 unpack the files from #4 out of the zip(#5) and place them in %appdata%/HoboNickels folder
#7 create or add to HoboNickels.conf the following lines.

connect=89.236.137.142:7372
connect=69.197.188.186:7372
connect=77.121.153.138:7372
connect=88.110.55.193:7372
connect=87.98.159.143:7372
connect=95.22.226.36:7372
connect=154.20.58.222:7372

#8 Restart client.
#9 After you are caught up to current, and your getinfo = getcheckpoint, shut down the client.
#10 Remove the connects from your HoboNickels.conf and restart the client as normal.


FYI, it can take a while to rescan the block chain after you start it up the first time, just be patient and let the client come up.

EDIT: You may not have to do #3 and #7, I was able to just replace the blockchain on one of my PCs and just start it backup and I was in good shape. I think there are enough people on the correct chain now, it should be easy to pick up the right one.

[Tranz]

The checkpoint server is now up and running on the following chain.

2018-08-14 23:05:31 SetBestChain: new best=000000351e1028c9358d height=5939094 trust=4072614652097797 blocktrust=69 date=08/14/18 23:04:15

I am working on a block chain download right now. But it will be a few hours before it is ready.

Thank you Tranz for your work. Now everything seems to be going right again. Well it was not an attack and only the checkpoint server.  

Actually there was nothing wrong with the CP server. It just shutdown on the 10th, and then something crazy happened, on the 13th?. Not sure if it was just bad luck or some type of attack. But I beleive it was due to PoW, which is now on it's last leg.

[poke@]

What's the current right chain to be on? Is there a block explorer website that's current? Thanks in advance!

[Tranz]

What's the current right chain to be on? Is there a block explorer website that's current? Thanks in advance!

Yes BE is correct.

[B3dr0ck]

there was a massive hash drop off, around the time of the fork, not sure the cause or affect there, makes sense that would cause a fork, someone mining on an old wallet or something.

speaking of that, to mine HBN with a L3+ looks like you'd have to create a whole mining pool, solo mining isn't really an option, you could probably do it with a USB asic.  I have a little usb asic on a shelf somewhere, I could probably use that for fun - not sure how much fun that would be.

since there's only 60K blocks left for POW, not worth it for me.

If anyone wanted to set up a mining pool for fun, I'll help, but can't invest that much time.

Dude - the hash for POW went to almost 0 for a couple of days
https://chainz.cryptoid.info/hbn/#@diff

[CoinEraser]

If I'm not mistaken, the .conf filename must be hobonickles.conf. I believe the rest you have done so far right.  

HoboNickels.conf

Ups, thank you for correction. I should just look what I write so. 

The checkpoint server is now up and running on the following chain.

2018-08-14 23:05:31 SetBestChain: new best=000000351e1028c9358d height=5939094 trust=4072614652097797 blocktrust=69 date=08/14/18 23:04:15

I am working on a block chain download right now. But it will be a few hours before it is ready.

Thank you Tranz for your work. Now everything seems to be going right again. Well it was not an attack and only the checkpoint server. 

Actually there was nothing wrong with the CP server. It just shutdown on the 10th, and then something crazy happened, on the 13th?. Not sure if it was just bad luck or some type of attack. But I beleive it was due to PoW, which is now on it's last leg.

The main thing is, everything works again as it should. 

Dude - the hash for POW went to almost 0 for a couple of days
https://chainz.cryptoid.info/hbn/#@diff

Yes, on this part of the blockchain we have no PoW for this timeframe, but on the other part of the blockchain (in a fork) we have a lot of Pow blocks. But you can not see that in BE anymore. 

[B3dr0ck]

Dude - the hash for POW went to almost 0 for a couple of days
https://chainz.cryptoid.info/hbn/#@diff

Yes, on this part of the blockchain we have no PoW for this timeframe, but on the other part of the blockchain (in a fork) we have a lot of Pow blocks. But you can not see that in BE anymore. 
[/quote]

right, right ... the hash didn't disappear it forked to another chain.   Makes me think a single pool somewhere, is all the hash.  (A pool I do not know of)  It's basically a 51% attack without the malice.