Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 175. (Read 478852 times)

Thanks, I agree! 

one of coolest scrypt coins IMO

Ok usually these type of issue happen when the wallet suddenly gets shut off either via update, or power failure. Unusual to have it happen while the wallet was running. Don't think I have seen that.

Yes it is a windows 7 PC. I usually turn windows updates off. They can be trouble. I have not seen an update run on this pc in many months.

Glad to hear it.

Follow up question; Was your computer(win 7?) recently updated and rebooted, while HBN was running?

good old coin!

Well my friend, good news at last! The second pass worked I deleted everything but the two blockchain files. I ran salvage wallet twice. The wallet has finally passed the bad block. Man I am feeling good. Let me know if you need anymore testing as I now have a test setup and can do testing for you whenever you may need it.
I learned a lot in this adventure.

Yes I have already tried that maneuver twice. I have run the wallet with new/empty wallets and it still hangs.

I think I may need to get the latest and greatest nodes for my config file. I think maybe something may be insufficient there.

Could also try this.
Remove database, use 9-16 block files, rename wallet.dat to noloadwallet.dat. This will create a new fresh wallet.

If it syncs rename noloadwallet.dat to wallet-old.dat and use the load wallet function.

Actually one note to mention right now. The wallet is not working on both PCs. It has been down for 3 days now.  I have also tried 1.4.8 1.4.7 and 1.4.0 all fail at the same point.

Okay, trying the experiment right now. I am using the golden 9-16 files I got from you. I have removed the database directory as well. I started from DOS prompt using the -salvagewallet command. I will let you know when the test finishes.

1st pass failed at the same spot I will try one more time with total refresh of files.

If you can get me an updated blockchain not more than 12 or so hours old I will load that on my main PC and get the hobowallet working on that PC. I still have the test setup so we can continue testing on that PC as necessary.















----------------------------------------------------------------

Welcome back! We miss you.. 

I did see that change.  Not sure what I am going to do with it quite yet. I was thinking of creating a entirely new transaction type, so it will show up on the message as well as the transaction page.

Eventually my goal was to actually incorporate S4C directly into the staking transaction. So if the block is staked, it will split the transaction into the percentage to give to them and the rest back to you.  This way it will be faster and free. It does require quite a bit of change, so it is a ways off, but it is my eventual goal..

So I just sync'd up from the 9-16 to current. No issues went right through, as I suspected.

I do believe the issue is here, for you.


To me this means there is something askew with your wallet.dat or your database.

Here is what I would like you to try, if you have time. On your 2nd pc, since you already have it running ok on your other.

1) Replace txleveldb/block001.dat with the 9-16 file. Just so it is faster. Full sync should work as well.
2) Remove the database dir (Normally I wouldn't recommend this, but for this test it should be ok)
3) Start the client with -salvagewallet
4) See if it syncs.

If you want to clear our your debug.log and then send it to me again, in case it doesn't work I would appreciate it.  Also feel free to post an address for helping debug issues. Always appreciated.


Thanks!

You generally do not have to, and should right away just erase everything.  You should first backup the wallet and database dir, then try to start the client with -salvagewallet . This usually fixes any corruption.

Regarding your question, if you created the export wallet(plain txt) file, you can use the import wallet to combine wallets. You can also use the importprivkey rpc command if you know have the privatekeys.

Ok got the log, yes your client is rejecting block 1,241,290 I am testing a few things on my end. I'll let you know what I come up with.

Thank you for your help too.

my hobo wallet.dat is probably corrupted
I could not start the client with that .dat
and I was forced to erase everything (took a back up of wallet.dat) and restarted with an empty wallet

is there a way to import that wallet ?
wallet has been encrypted

currently waiting for the blockchain to redownload

Also, version 1.4.0.1 works flawless for me under WinXP sp3.

listen=1
daemon=1
server=1
rpcuser=
rpcpassword=
port=7372
rpcport=7373
rpcconnect=127.0.0.1
maxconnections=100
addnode=5.228.253.141
addnode=5.249.152.30
addnode=23.28.66.198
addnode=23.92.80.107
addnode=24.255.246.67
addnode=24.249.152.169
addnode=46.237.89.248
addnode=54.201.183.106
addnode=54.186.69.238
addnode=54.83.3.49
addnode=54.85.17.31
addnode=54.200.138.226
addnode=63.155.67.204
addnode=65.186.210.229
addnode=65.24.235.56
addnode=67.166.0.82
addnode=67.55.10.47
addnode=69.85.86.195
addnode=71.9.234.158
addnode=71.15.25.28
addnode=72.83.4.150
addnode=72.52.231.153
addnode=74.83.19.68
addnode=74.208.97.13
addnode=74.196.48.62
addnode=76.14.215.153
addnode=81.247.105.90
addnode=83.81.97.1
addnode=86.178.61.241
addnode=86.151.253.206
addnode=87.205.193.178
addnode=91.121.177.181
addnode=93.131.188.211
addnode=94.224.109.177
addnode=94.251.132.2
addnode=94.23.31.223
addnode=97.88.160.74
addnode=98.148.179.13
addnode=107.15.231.157
addnode=107.170.101.69
addnode=108.193.130.242
addnode=109.242.36.205
addnode=109.235.190.7
addnode=162.243.28.252
addnode=162.243.123.132
addnode=162.217.249.198
addnode=173.11.82.114
addnode=173.218.212.131
addnode=178.149.57.165
addnode=188.165.223.132
addnode=188.104.141.34
addnode=192.99.44.159
addnode=195.91.216.170
addnode=198.101.10.109
addnode=203.12.171.66
addnode=213.7.8.12

-------------------------------------------------
websitetrafficdelivery[dot]tk - HBN/DOGE/PayPal accepted

I sent you the link in a PM  file via file dropper. I tried reloading from scratch and the wallet hung at about half way through. I then retried using the blockchain you sent a couple of weeks ago. This time I hardwired my PC to the network instead of wireless. Still hangs. I then tried setting up a wireless hotspot using my phone thinking that it might be something wrong with my router or home network. It still would not progress beyond this block number 1241289. This is the last block processed. So far I have eliminated the PC as the problem, I tried it on two PCs. I have eliminated my home network as the problem. I tried it on two networks. I eliminated the wallet as the problem it even sticks with an empty wallet. It appears to me to be a network / code problem where a certain condition occurs and when this condition happens the wallet looses its ability to sync.

There is only one way I can think of to fix this problem without some sort of code change. I will have to obtain a blockchain that is only a few hours old. One that is beyond the block that causes the freeze. This will probably be a temporary fix as this has happened 2 times this month so I am thinking it may happen again until we find what the root cause of this problem is. I used to test software and hardware for a living so let me know if you need some testing help in the future or with this current problem. I like hobonickles and I want to see it be very successful.

Thanks for the support...

Ahhh my first crypto "home" - HoboNickels.

Tranz not sure if you saw this, or if HBN already has this, but I added S4C flag to the notificator.

https://github.com/presstab/HyperStake/commit/867a7dbc1b68a4d07dd886bc8dd646ecdceb18c9
https://github.com/presstab/HyperStake/commit/15fa632dfecb18c331103ffac9ba81aef3fc64f8

nevermind, got there eventually I'm good