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
Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 29. (Read 478852 times)
August 15, 2018, 05:03:47 PM
August 15, 2018, 09:41:27 AM
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.
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.
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.
August 14, 2018, 11:50:51 PM
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.
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.
August 14, 2018, 11:31:58 PM
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
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.
August 14, 2018, 11:25:47 PM
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
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!
August 14, 2018, 10:47:34 PM
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
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,
August 14, 2018, 10:27:14 PM
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
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.
August 14, 2018, 10:05:53 PM
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
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?
August 14, 2018, 09:55:39 PM
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
I did exactly what Tranz recommend: and I got
getcheckpoint
"height" : 5939276
getinfo
"blocks" : 5939276
August 14, 2018, 09:51:17 PM
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.
getinfo shows the block height, but thats about it. Looks like i'm close to being on the correct chain.
August 14, 2018, 06:35:06 PM
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.
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.
August 14, 2018, 06:06:58 PM
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.
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.
August 14, 2018, 05:09:19 PM
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
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.
August 14, 2018, 04:45:40 PM
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
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
August 14, 2018, 04:42:33 PM
Looks like there are a few splits. The checkpoint server went offline to do VPS failure. The chain had some issues and didn't' hold together. I would suggest holding all sends until this is resolved.
Cryptopia seems to be in the best shape. I am going to get the checkpoint server back online and on that chain then start issuing checkpoints. I will release a new tar ball with the full chain once I have it.
Cryptopia seems to be in the best shape. I am going to get the checkpoint server back online and on that chain then start issuing checkpoints. I will release a new tar ball with the full chain once I have it.
Thx Tranz 4 the information
August 14, 2018, 04:39:09 PM
Looks like there are a few splits. The checkpoint server went offline to do VPS failure. The chain had some issues and didn't' hold together. I would suggest holding all sends until this is resolved.
Cryptopia seems to be in the best shape. I am going to get the checkpoint server back online and on that chain then start issuing checkpoints. I will release a new tar ball with the full chain once I have it.
Cryptopia seems to be in the best shape. I am going to get the checkpoint server back online and on that chain then start issuing checkpoints. I will release a new tar ball with the full chain once I have it.
August 14, 2018, 03:37:08 PM
i don't see the point of this block chunk 
that stake wasn't accepted on any chain, prolly orphaned, isn't it normal..
that stake wasn't accepted on any chain, prolly orphaned, isn't it normal..
yep thats the point
why block 5938411 ?if you mean why it forked ask the dev and the checkpoint server guy, i can only help to sync when needed
ok thx 4 help
August 14, 2018, 03:20:03 PM
i don't see the point of this block chunk
that stake wasn't accepted on any chain, prolly orphaned, isn't it normal..
that stake wasn't accepted on any chain, prolly orphaned, isn't it normal..
yep thats the point
why block 5938411 ? August 14, 2018, 02:16:34 PM
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
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
2018-08-13 23:08:29 SetBestChain: new best=83098def1d6847f86f41 height=5938411 trust=4071788861351071 blocktrust=12008800421 date=08/13/18 23:08:20
2018-08-13 23:08:29 ProcessBlock: ACCEPTED
2018-08-13 23:08:30 socket recv error 10054
2018-08-13 23:08:40 CheckStake() : new proof-of-stake block found
hash: ad80e825a24331412c7088d7a9caecc84e84b62cce6de3366d99961271fdadd2
proofhash: 000013aa4bf1e6664c0dbb8285cb1758e8de0bde33a15234e06f7d160b06e569
target: 000062dad02fa400000000000000000000000000000000000000000000000000
2018-08-13 23:08:40 CBlock(hash=ad80e825a24331412c7088d7a9caecc84e84b62cce6de3366d99961271fdadd2, ver=4, hashPrevBlock=83098def1d6847f86f41b31ebad8ec444a5f8a6b59565cf9f9df472f07ee7db3, hashMerkleRoot=3b298f49b0cbb83f972c2a64a20159c1142f0f2cc2a5aba42d850b691219fe4b, nTime=1534201690, nBits=1c5a1e64, nNonce=0, vtx=2, vchBlockSig=3044022074a70e2e8f3daba11b1e8ef592a90ce7a152233220dac30614dc1306c50cf22802203b4899c53eda25d5772bda317d3a996cd23a23b7cceb7f4ec58a774544a38377)
Coinbase(hash=572f376171, nTime=1534201690, ver=1, vin.size=1 vout.size=1 nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 03ec9c5a0101)
CTxOut(empty)
Coinstake(hash=e856f357fc, nTime=1534201690, ver=1, vin.size=1 vout.size=2 nLockTime=0)
CTxIn(COutPoint(3e31620ef1, 1), scriptSig=3044022001face51e15720fd)
CTxOut(empty)
CTxOut(nValue=4351.111582, scriptPubKey=03cdfe32899bab013be0ba626d3afcd03634b6f1ef7642c2174b5a78d1092ac408 OP_CHECKSIG)
vMerkleTree: 572f376171f4e3e982d330907e5d13d8365e8f9b2c918b254a83bfdde11b7093 e856f357fccbe1a39e33202dee842070cfc64d9d76339de21b7a8c77b6ccb555 3b298f49b0cbb83f972c2a64a20159c1142f0f2cc2a5aba42d850b691219fe4b
2018-08-13 23:08:40 out 4351.111582
2018-08-13 23:08:40 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(3e31620ef1, 1), 1534201690) for block ad80e825a24331412c7088d7a9caecc84e84b62cce6de3366d99961271fdadd2
2018-08-13 23:08:40 ERROR: CheckStake() : ProcessBlock, block not accepted
2018-08-13 23:08:42 socket recv error 10053
August 14, 2018, 12:07:15 PM
I think the chain Cryptopia is ... I dont know ... it's important. It can be on a different chain, but if you can't trade the coin ...
Cryptopia is down to 2 connection.
Block Height 5938843 version 2.0.1.0-gV2.0
73.143.78.110:7372
88.110.55.193:7372
summon @Tranz
Cryptopia is down to 2 connection.
Block Height 5938843 version 2.0.1.0-gV2.0
73.143.78.110:7372
88.110.55.193:7372
summon @Tranz
from practical pov you're abs. right,
especially knowing how long it takes for topia to make any maintenance.
but this fork is not resolving on it's own, so i wonder where is that bloody checkpoint server right now,
on topia's chain or BE ?
if i sync unrestricted i always end up on BE one
I deposited HBN from topia yesterday, thats when I noticed. Difficulty is pretty low, wouldn't be hard to fork the coin, but honestly, I don't know (have never known) how the POW / POS verifies transactions. Which has priority. Last time I saw this it looked like Hash2Coin pool was mining a different chain. I don't know if any pools that mine HBN now, and havn't for a long time.
Difficulty has plummeted over this time as well
https://chainz.cryptoid.info/hbn/#@diff
Anyone have a link for instructions on how to mine a HBN QT wallet with a L3?
Jump to: