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

[Makitaki]

check out here to get a working copy of the blockchain just a few days back

http://wiki.hobonickels.info/index.php?title=Replace_Blockchain

Using this is ok. Best to create your own index, but this is safe enough. However you shouldn't replace your database directory, this is used for the wallet.dat.  Just need the blk0001.dat and the leveldb directory. Those 2 are for the block chain.  wallet.dat and database directory work for the wallet.dat

I just learned something new about the file structure... thanks

Yeah, live and learn!  I didn't know about this, too.

[1714498380]

1714498380

[1714498380]

1714498380

[1714498380]

1714498380

[1714498380]

1714498380

[semajjames]

check out here to get a working copy of the blockchain just a few days back

http://wiki.hobonickels.info/index.php?title=Replace_Blockchain

Using this is ok. Best to create your own index, but this is safe enough. However you shouldn't replace your database directory, this is used for the wallet.dat.  Just need the blk0001.dat and the leveldb directory. Those 2 are for the block chain.  wallet.dat and database directory work for the wallet.dat

It should have only been syncing about 4 days worth because i gave it my saved complete roaming folder to read

however now i let it download complete new blockchain and gave it my "saved database" directory and ".wallet" file and everything seem's fine but i do have a warning saying "checkpoint too old"

??

[signorama]

check out here to get a working copy of the blockchain just a few days back

http://wiki.hobonickels.info/index.php?title=Replace_Blockchain

Using this is ok. Best to create your own index, but this is safe enough. However you shouldn't replace your database directory, this is used for the wallet.dat.  Just need the blk0001.dat and the leveldb directory. Those 2 are for the block chain.  wallet.dat and database directory work for the wallet.dat

It should have only been syncing about 4 days worth because i gave it my saved complete roaming folder to read

however now i let it download complete new blockchain and gave it my "saved database" directory and ".wallet" file and everything seem's fine but i do have a warning saying "checkpoint too old"

??

If it says "checkpoint too old" it means something is still wrong. I'll suggest downloading or compiling a new wallet.

[Tranz]

check out here to get a working copy of the blockchain just a few days back

http://wiki.hobonickels.info/index.php?title=Replace_Blockchain

Using this is ok. Best to create your own index, but this is safe enough. However you shouldn't replace your database directory, this is used for the wallet.dat.  Just need the blk0001.dat and the leveldb directory. Those 2 are for the block chain.  wallet.dat and database directory work for the wallet.dat

It should have only been syncing about 4 days worth because i gave it my saved complete roaming folder to read

however now i let it download complete new blockchain and gave it my "saved database" directory and ".wallet" file and everything seem's fine but i do have a warning saying "checkpoint too old"

??

If it says "checkpoint too old" it means its not something is still wrong. I'll suggest downloading or compiling a new wallet.

Do you blocks match the explorer, in height and difficulty? http://162.217.249.198:1080/chains or  http://hbn.blockx.info/get/chain/HoboNickels

If so you are ok. next time you restart the wallet it will go away.

If you don't match, (off by many thousand or more) then yes you have some type of issue.

[Tranz]

I have released 1.4.0.1 tonight. I put in on the release page. https://github.com/Tranz5/HoboNickels/releases

This version will require you to re-index, as the block hash is now added to the index. This speeds up start up time by 10-20x. I personally went from 5 minutes to 15 seconds. The re-index will happen automatically, so if you want to keep your old version of files, please be sure to make a backup for blk001.dat and txleveldb folder before you start this up.

I have had mix results from re-indexing from peers. 2 out of 7 times, after I was up to current block and closed and re-opened it. I got the dreaded assert failure.

One thing that can be done, to help, is to stop the client every 200k blocks and take a quick snapshot of the blk0001.dat and txleveldb folder.  Then start it backup.

I have also put a copy for my blk0001.dat and txleveldb folder here  http://www.fileswap.com/dl/SnNNULZqH/   You can use this to overlay your files and then you should only have a few thousand blocks to catchup on.

md5sum block_chain_backup_April_10_1.4.1.zip
5910921e0633794c15343431ac88e4df *block_chain_backup_April_10_1.4.1.zip


These are only compatibly with version 1.4.0.1+

Please let me know if you have any problems.

Thanks all!

[dogechode]

Thanks guys!

I have released 1.4.0.1 tonight. I put in on the release page. https://github.com/Tranz5/HoboNickels/releases

This version will require you to re-index, as the block hash is now added to the index. This speeds up start up time by 10-20x. I personally went from 5 minutes to 15 seconds. The re-index will happen automatically, so if you want to keep your old version of files, please be sure to make a backup for blk001.dat and txleveldb folder before you start this up.

I have had mix results from re-indexing from peers. 2 out of 7 times, after I was up to current block and closed and re-opened it. I got the dreaded assert failure.

One thing that can be done, to help, is to stop the client every 200k blocks and take a quick snapshot of the blk0001.dat and txleveldb folder.  Then start it backup.

I have also put a copy for my blk0001.dat and txleveldb folder here  http://www.fileswap.com/dl/SnNNULZqH/   You can use this to overlay your files and then you should only have a few thousand blocks to catchup on.

md5sum block_chain_backup_April_10_1.4.1.zip
5910921e0633794c15343431ac88e4df *block_chain_backup_April_10_1.4.1.zip


These are only compatibly with version 1.4.0.1+

Please let me know if you have any problems.

Finally Unick. I will be posting a few more fixes for the Mac client here in the next few days. I'll let you know, but if you can try them out and let me know how it goes I would appreciate it.

Thanks all!

The file on top there says 1.4 - uploaded 4 days ago - are you sure the new version is there? Am I missing something? Also, do you mean we should delete the blockchain files and let it resync everything?

[presstab]

The link is on there for me. Look closely there are two zips.

[dogechode]

ahhh I missed the second zip to the right of the 1.4.0 one, sorry! Thanks for pointing this out. Re-syncing now...

[unick]

I'll take a look tomorrow

[dogechode]

well it went from 750k blocks or so remaining to 250k blocks remaining in just a few hours so it seems like the full re-sync doesn't take too long for anyone who was wondering. And, the wallet loads insanely fast now, took about 10 seconds to load for me, great work as always Tranz!!

[Tranz]

well it went from 750k blocks or so remaining to 250k blocks remaining in just a few hours so it seems like the full re-sync doesn't take too long for anyone who was wondering. And, the wallet loads insanely fast now, took about 10 seconds to load for me, great work as always Tranz!!

No problem, just remember once you are done, just do a quick shutdown and make a backup copy of txleveldb and blk001.dat. So you can always get up to speed even faster in the future should something go awry with that computer.

[alibabacool]

Very good, Tranz!
With 1.4.0.1 version start up take about 10 seconds on my pc with ssd storage.
Thanks!

[dogechode]

Tranz, one other question - After it finished syncing, my recent transactions shows the orphans I've generated rather than the most recent transactions. So like it shows 2 orphan transactions from 4/9 and one from 4/7, but if I go to the full transactions list and sort by date then I can clearly see several transactions on 4/10, 4/11, and 4/12 - so why is it randomly deciding to show me those three orphaned mining attempts from 4/9 and 4/7 under recent transactions?

[broken_pixel]

Tranz, one other question - After it finished syncing, my recent transactions shows the orphans I've generated rather than the most recent transactions. So like it shows 2 orphan transactions from 4/9 and one from 4/7, but if I go to the full transactions list and sort by date then I can clearly see several transactions on 4/10, 4/11, and 4/12 - so why is it randomly deciding to show me those three orphaned mining attempts from 4/9 and 4/7 under recent transactions?

Back up the wallet.dat file and run repair wallet and it will delete the orphans.

[Tranz]

Tranz, one other question - After it finished syncing, my recent transactions shows the orphans I've generated rather than the most recent transactions. So like it shows 2 orphan transactions from 4/9 and one from 4/7, but if I go to the full transactions list and sort by date then I can clearly see several transactions on 4/10, 4/11, and 4/12 - so why is it randomly deciding to show me those three orphaned mining attempts from 4/9 and 4/7 under recent transactions?

It sorts by status by default. You can resort it by date. You can also do as suggested and run repair wallet, which will remove them.

[tokyoghetto]

Any chance HBN can get a Multipool? That way we have three different ways to mine the coin.

[ryanb]

i did the repairwallet command but it didn't clear the orphans

[Tranz]

i did the repairwallet command but it didn't clear the orphans

Which version are you using ryan?

[unick]

Any chance HBN can get a Multipool? That way we have three different ways to mine the coin.

I was thinking about that too.

Is someone up for the task to set this up? Maybe Meska? since he already has a pool up and running

EDIT: PM him, will see 

[Tranz]

By Multipool I assume you guys mean, mine the most profitable coin and then dump it for HBN?

Yes I think Meska would be the one to hit up for that