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

[Digi7ech]

It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.

[1714956498]

1714956498

[1714956498]

1714956498

[1714956498]

1714956498

[Tranz]

It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.

Naw, there is a bitcoin at 300.  It would eat your 389k.. Also during those huge dumps the bots come out and play and create liquidity as well.

[CrazyLoaf]

HBN and HYP had market caps of roughly $30k each at the start of May 2017. I am not buying that the devs finally showing up warrants them to pump up to $1.5mil each. If you all can sustain those higher market caps, more power to you, but the dumps will come as they always do in high PoS coins. Or, hey, if it looks like demand is picking up for the high PoS model again, I am sure iGotSpots will come back and flood the market with clones

[workshop35]

I'm having wallet issues as well. I get the following error

Critical error loading wallet "reset" from wallet-reset.dat: CDB() : cant open
database file wallet-reset.dat, error 22

I had renamed this wallet file a long time ago when doing some coin cleanup to rest all my stakes into one large chunk. I can't seem to get this to work, and google isnt helping. Any tips how to remedy an error 22? thanks

There is no easy way currently to run salvagewallet  on a secondary wallet .If you have a wallet-reset.dat backup, try using that one instead. If not try these steps below.

1) Shutdown client
2) rename wallet.dat to noloadwallet.dat
3) rename wallet-reset.dat to wallet.dat
4) Startclient with -salvagewallet
5) Be patient, after fixing keys, it will rescan 5million blocks, this can take a fair amount of time. Possibly hours depending on your computer.
6) After complete, shutdown client
7) rename your wallet.dat (previously wallet-reset.dat) back to wallet-reset.dat
rename your noloadwallet.dat to wallet.dat
9) start client up
10) do more frequent wallet backups!

You can alway monitor that progress by looking at the debug.log file.

I will work on adding an extra switch to salvagewallet to work on a secondary wallet For version 1.6.

Edit: If you are good with startups switches you can also also do this to save time.
1) Shutdown client
2) Create new dir called C:\hbn_fix
3) copy wallet-reset.dat to c:\hbn_fix\wallet.dat
4) startup client with -salavgewallet -datadir=c:\hbn_fix
5) After client is done and wallet is working, shut it down.
6) rename your wallet-reset.dat in your normal datadir %appdata% to brokewallet-reset.dat
7) Copy your wallet.dat form c:\hbn_fix to your normal datadir as wallet-reset.dat

This method may save a bit of time.

This is what happens whenever I have tried to -salvagewallet this one

2017-07-14 19:52:55 Renamed wallet.dat to wallet.1500061975.bak
2017-07-14 19:52:55 Error: Salvage found errors, all data may not be recoverable.
2017-07-14 19:52:55 Salvage(aggressive) found no records in wallet.1500061975.bak.

2017-07-14 19:54:03 Failed to rename wallet.dat to wallet.1500062043.bak

and the client exits. I gave up before when this happened because I couldnt figure it out. Is it doing this because the wallet was encrypted?

also, db.log gives me a bunch of errors. heres the last one

wallet.1488662875.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 359/6987529, past end of log at 71/4537095
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment

[Digi7ech]

It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.

Naw, there is a bitcoin at 300.  It would eat your 389k.. Also during those huge dumps the bots come out and play and create liquidity as well.

You're right. I was reading the depth chart wrong. There's some decent buys in place, but any human trader watching his stuff should pull out his stops as it falls.

I'd love to see it settle higher than what we were at. It's an OG coin compared to some of the stuff out there now.

[Tranz]

This is what happens whenever I have tried to -salvagewallet this one

2017-07-14 19:52:55 Renamed wallet.dat to wallet.1500061975.bak
2017-07-14 19:52:55 Error: Salvage found errors, all data may not be recoverable.
2017-07-14 19:52:55 Salvage(aggressive) found no records in wallet.1500061975.bak.

2017-07-14 19:54:03 Failed to rename wallet.dat to wallet.1500062043.bak

and the client exits. I gave up before when this happened because I couldnt figure it out. Is it doing this because the wallet was encrypted?

also, db.log gives me a bunch of errors. heres the last one

wallet.1488662875.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 359/6987529, past end of log at 71/4537095
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment

Hmm A possibly corrupted encrypted wallet.. I am not sure I have dealt with that yet. I will ask the obvious, do you have a backup before it was encrypted, or one that was encrypted but from a while ago?

I don't know if the database dir has much do to with it. But you should attempt to salvage on a clean database dir as well. Under a separate datadir, so you don't mess up your normal wallet.

[Majormax]

It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.

Why would you say that ?

You never know what forces will come into play on price changes, either + or - 

[HCLivess]

HBN and HYP had market caps of roughly $30k each at the start of May 2017. I am not buying that the devs finally showing up warrants them to pump up to $1.5mil each. If you all can sustain those higher market caps, more power to you, but the dumps will come as they always do in high PoS coins. Or, hey, if it looks like demand is picking up for the high PoS model again, I am sure iGotSpots will come back and flood the market with clones

I think the coin age and the development activity are important, plus 100% yearly is not that high

[Cryptorast]

Deposit on cryptopia still off I need money now, want to sale 50000 HBN for 0.17 BTC, PM please.

[B3dr0ck]

OK so I copied over a fresh blockchain
- I deleted the Hobonickels contents from the %appdata% folder
- I started the wallet QT files, It starts the wallet fine, and creates the contents of the HoboNickels folder
- I close the wallet, delete out the 2 Blk..dat files, and the wallet.dat, and the txleveldb dir
- I copy over my wallet.dat, the 2 Blk...dat files, and the txleveldb dir from the new downloaded
- I start the wallet back, and get the same error, I've been getting

Could my wallet.dat be off somehow?  I've got other copies, I can dig out.
Is my process off somewhere?

Is is possible your wallet.dat got corrupted. Have you tried -salvagewallet startup switch ?

OK this seems crazy to me but, here we go ....
I tried the -salvagewallet - still crashes same way
I tried a lower version HoboNickel wallet - dies same way
I tried it with the original wallat.dat - it still dies, OK yea, that got me thinking too
So I tried the same procedures on another computer, another Windows 7 Pro, this one is 64bit - and it comes up fine.

That original computer that it kept crashing on was a freshly formatted PC, with a fresh OS installed.  What in the world could be wrong with that PC?  That is hates the HBN wallet so much?


I have 0 (zero) network connections, what am I missing.  (I only rebuild wallets about once a year, so I have to learn most of the stuff all over again)

[Tranz]

OK so I copied over a fresh blockchain
- I deleted the Hobonickels contents from the %appdata% folder
- I started the wallet QT files, It starts the wallet fine, and creates the contents of the HoboNickels folder
- I close the wallet, delete out the 2 Blk..dat files, and the wallet.dat, and the txleveldb dir
- I copy over my wallet.dat, the 2 Blk...dat files, and the txleveldb dir from the new downloaded
- I start the wallet back, and get the same error, I've been getting

Could my wallet.dat be off somehow?  I've got other copies, I can dig out.
Is my process off somewhere?

Is is possible your wallet.dat got corrupted. Have you tried -salvagewallet startup switch ?

OK this seems crazy to me but, here we go ....
I tried the -salvagewallet - still crashes same way
I tried a lower version HoboNickel wallet - dies same way
I tried it with the original wallat.dat - it still dies, OK yea, that got me thinking too
So I tried the same procedures on another computer, another Windows 7 Pro, this one is 64bit - and it comes up fine.

That original computer that it kept crashing on was a freshly formatted PC, with a fresh OS installed.  What in the world could be wrong with that PC?  That is hates the HBN wallet so much?

Well I am glad you got it work. Have you tried to Scandisk on the original computer? It could be lost clusters which cause read errors, or possibly bad memory chip or CPU?  I have burnt out a CPU before, so I know it is possible.  Although most likely is some issue with HDD.

I have 0 (zero) network connections, what am I missing.  (I only rebuild wallets about once a year, so I have to learn most of the stuff all over again)

https://cryptocurrencytalk.com/topic/85150-no-peer-connections-on-wallet/

[ph4nt0m]

Hey Tranz, I have a problem with 1.5.2.0. It crashes on start up.

hobonickels-qt: src/kernel.cpp:372: unsigned int GetStakeModifierChecksum(const CBlockIndex*, bool): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.
Aborted

If I comment out that line in the code, it dies anyway.

Code:

2017-07-15 14:40:59 HoboNickels version v1.5.2.0-gf46fa0c-V1.5 (2017-06-27 00:03:06 -0400)
2017-07-15 14:40:59 Using OpenSSL version OpenSSL 1.0.1t  3 May 2016
2017-07-15 14:40:59 Default data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 Used data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 init message: Verifying database integrity...
2017-07-15 14:40:59 dbenv.open LogDir=/home/ph4nt0m/.HoboNickels/database ErrorFile=/home/ph4nt0m/.HoboNickels/db.log
2017-07-15 14:41:00 splitthreshold set to 100000000
2017-07-15 14:41:00 combinethreshold set to 200000000
2017-07-15 14:41:00 Bound to [::]:7372
2017-07-15 14:41:00 Bound to 0.0.0.0:7372
2017-07-15 14:41:00 init message: Loading block index...
2017-07-15 14:41:00 Opening LevelDB in /home/ph4nt0m/.HoboNickels/txleveldb
2017-07-15 14:41:00 Transaction index version is 70600
2017-07-15 14:41:00 Opened LevelDB successfully
2017-07-15 14:42:43 ERROR: CTxDB::LoadBlockIndex() : Failed stake modifier checkpoint height=0, modifier=0x0000000000000000

If I delete the chain data and sync again, it gets stuck at 90-something days ago. Restart and the same crap happens.

[Tranz]

Hey Tranz, I have a problem with 1.5.2.0. It crashes on start up.

hobonickels-qt: src/kernel.cpp:372: unsigned int GetStakeModifierChecksum(const CBlockIndex*, bool): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.
Aborted

If I comment out that line in the code, it dies anyway.

Code:

2017-07-15 14:40:59 HoboNickels version v1.5.2.0-gf46fa0c-V1.5 (2017-06-27 00:03:06 -0400)
2017-07-15 14:40:59 Using OpenSSL version OpenSSL 1.0.1t  3 May 2016
2017-07-15 14:40:59 Default data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 Used data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 init message: Verifying database integrity...
2017-07-15 14:40:59 dbenv.open LogDir=/home/ph4nt0m/.HoboNickels/database ErrorFile=/home/ph4nt0m/.HoboNickels/db.log
2017-07-15 14:41:00 splitthreshold set to 100000000
2017-07-15 14:41:00 combinethreshold set to 200000000
2017-07-15 14:41:00 Bound to [::]:7372
2017-07-15 14:41:00 Bound to 0.0.0.0:7372
2017-07-15 14:41:00 init message: Loading block index...
2017-07-15 14:41:00 Opening LevelDB in /home/ph4nt0m/.HoboNickels/txleveldb
2017-07-15 14:41:00 Transaction index version is 70600
2017-07-15 14:41:00 Opened LevelDB successfully
2017-07-15 14:42:43 ERROR: CTxDB::LoadBlockIndex() : Failed stake modifier checkpoint height=0, modifier=0x0000000000000000

If I delete the chain data and sync again, it gets stuck at 90-something days ago. Restart and the same crap happens.

Please move to 1.5.3.(0 or 1).  That version messed up the txleveldb  and blk0001.dat versions. You get that version and then grab the block chain from hobonickels.info.

[Cryptorast]

Does anyone know what heppen with cryptopia wallet?

[Tranz]

Does anyone know what heppen with cryptopia wallet?

I informed them there was a wallet update, and they needed to upgrade before September. They immediately took the wallet down.  And haven't updated to 1.5.3 yet. It takes about 5 min to compile and change the executable. So I have no idea why it has been such a delay. They said the are super busy with updates to the site due to the demand and would get to it within a week.   

[FlungSpun]

Bit of an orphan fest right now?

Either 1.5.3 or the fact I have let my stakes run down to many small blocks this time around. The hit rate is 5 stakes / 105 orphans overnight

New client did struggle a bit to get in sync and stay there - last block time is laggy but I'm not sure that isn't just GUI update lag
POS block info window seems very shy these days.

I'll get a transaction stuck on 1 confirm for 5-10 mins and then suddenly 24 confirms and a bunch of stakes go orphan with it.

Also seems to be behaving worse @ 1.6GB ram usage than @ 2GB

Are we are waiting this out for block 5.6M?


.. wow this is like going to the doctor. In the time taken to type this a flurry of confirmed Stakes arrives

[strawie]

tbh I keep my blocks at 9k all the time. safes me alot of headache...

[FlungSpun]

tbh I keep my blocks at 9k all the time. safes me alot of headache...

Yeah me too but started to feel guilty about not holding up the network so decided to let thinks take a natural course.
I think I have found the red line.

[2xjO9M3P]

Bit of an orphan fest right now?

Either 1.5.3 or the fact I have let my stakes run down to many small blocks this time around. The hit rate is 5 stakes / 105 orphans overnight
[...]

I've had a 4k block orphan 11 times in the past 12 hours, so not necessarily due to "many small blocks"..

[Tranz]

Orphans are caused by lots of things. For HBN the reasons are many, but not without solutions.

1) 30 Second block time. This is very hard to get a block transmitted around the world in 30 seconds. ALso each block times CPU and time to process, which cause GUI and Staking lag.
2) PoW and PoS which effectively changes the block time to 20 seconds or lower.
3) Low difficultly with a lot of coins and a lot of hash out there. This allows people to generate many blocks very very quickly. Which can cause the network issues while everyone is catching up.
4) Staking efficiency.


To fix these here is what we can do.

1) We need to talk about changing the block time to something a bit longer. I am thinking 90 seconds.
2) PoW is going to be slowed down and eventually effectively eliminated.  So this will help
3) This will be fixed with #2 and #1.
4) This is in progress right now and I am hoping to have it released in version 1.5.5

I am going to commit version 1.5.4 tonight. It will contain some malleability fixes and adds the ability to watch and report on other address that you do not own. Usually referred to as Watch Only. So you can use it to watch all of you wallets in 1 place, or spy on a large address to watch what is going on. 

It required by Feb 2018, which is approx when all of the forks, whatever the happen to be, will take place. Those not in version 1.5.3 that is.