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.
Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 56. (Read 478852 times)
September 05, 2017, 06:59:29 PM
September 05, 2017, 06:43:43 PM
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.
September 05, 2017, 06:40:48 PM
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.
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.
September 05, 2017, 06:38:20 PM
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?
September 05, 2017, 05:54:09 PM
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?
September 05, 2017, 05:47:18 PM
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
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"
}
September 05, 2017, 05:12:53 PM
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.
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.
September 05, 2017, 04:39:34 PM
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.
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.
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.
September 05, 2017, 11:10:00 AM
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.
September 05, 2017, 11:00:25 AM
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) September 05, 2017, 10:15:36 AM
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?
September 04, 2017, 09:26:06 PM
If whomever IPs this is, could you please PM me?
24.129.112.198
24.129.112.198
September 04, 2017, 04:26:39 PM
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.
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.
September 03, 2017, 08:24:28 PM
How long until cryptopia resumes trading on HBN?
Out of my hands. I have opened ticket and let them know whatever they need I can make it happen. My guess is a week or 2.
September 03, 2017, 05:24:28 PM
How long until cryptopia resumes trading on HBN?
September 03, 2017, 05:00:04 PM
Hi!
Do we have any other mining pools, now that H2C is in maintance.
Thanx
Do we have any other mining pools, now that H2C is in maintance.
Thanx
No but solo mining works great!
September 03, 2017, 03:12:43 PM
I am still unable to sync even with an empty wallet with the newest version that had the newest block information added to the app data folder.
Could someone please post the current addnodes, thanks.
Could someone please post the current addnodes, thanks.
Here you can find current nodes: https://chainz.cryptoid.info/hbn/#!network
addnode=104.230.143.200
addnode=109.227.254.135
addnode=118.210.65.144
addnode=119.4.220.173
addnode=119.4.220.48
addnode=153.167.128.232
addnode=172.221.219.6
addnode=172.58.201.178
addnode=173.216.69.133
addnode=173.246.10.52
addnode=175.152.105.145
addnode=175.152.105.31
addnode=178.248.4.130
addnode=181.41.40.164
addnode=181.41.41.251
addnode=184.54.5.230
addnode=188.61.212.220
addnode=192.64.4.114
addnode=192.64.5.210
addnode=24.212.140.163
addnode=5.103.138.97
addnode=65.60.236.56
addnode=73.121.216.227
addnode=73.228.39.117
addnode=75.71.127.100
addnode=77.22.251.50
addnode=89.236.135.220
addnode=94.113.207.67
addnode=95.222.25.22
Hope that helps.
September 03, 2017, 12:03:40 PM
I am still unable to sync even with an empty wallet with the newest version that had the newest block information added to the app data folder.
Could someone please post the current addnodes, thanks.
Could someone please post the current addnodes, thanks.
September 03, 2017, 10:58:06 AM
Hi!
Do we have any other mining pools, now that H2C is in maintance.
Thanx
Do we have any other mining pools, now that H2C is in maintance.
Thanx
September 03, 2017, 08:52:48 AM
Version 1.5.5.5 is out and so is the new blockchain.
https://github.com/Tranz5/HoboNickels/releases/latest
http://hobonickels.info/HBNBlockChain.zip
If you had trouble please upgrade and download the zip to get back to current. The Block Explorer has updated and is in good shape now.
https://github.com/Tranz5/HoboNickels/releases/latest
http://hobonickels.info/HBNBlockChain.zip
If you had trouble please upgrade and download the zip to get back to current. The Block Explorer has updated and is in good shape now.
I get the error loading blkindex.dat message with the v.1.5.5.5 Do i realy need to resync the whole chain?
Might there be an initialisation bug? It's because I dont have such a file in my AppData folder..
Currently there is a blk0001.dat and blk0002 file available.
Just a bad error message. But likely something was wrong with your index.
http://hobonickels.info/HBNBlockChain.zip
Just grab this .zip and replace your blk0001.dat nad blk0002.dat and rename or remove your txleveldb folder and replace it with the one in the .zip
i was going to mention that pre-leveldb error message, but it slipped my mind.
i got it too last week.
i had copied the txleveldb subfolder files over Samba networking and most of the files and folder had ownership/group set incorrectly. essentially that message was trying to say "permissions denied" to those files.
so "check ownership and read/write access to files" is always good generic advice
Nah, that was not the issue in my case.
The permissions on the files are "full access" and the owner is the user itself.
Thank you Tranz for the download link, i try this one.
Jump to: