Finished up 1.5.4.0. This will be for self compilers only. I will eventually release a FAQ on best pracites for watch-only. Short of it is, best to use the "New Wallet" Function and add your watch only to that wallet. Add all of them with the false rescan flag, and then add the last one with true rescan flag. Have to add both public address and public script script separately if you want to watch both send/receives and stakes. https://github.com/Tranz5/HoboNickels/commit/6a88e8f06508503d6e5efe2aaed5878bded2c138 Changes:
Script Validation Change, must upgrade by March 1, 2018
Fix some mutability potential problems.
Removed uneeded opcodes
Removed getpubkey and validatepubkey, should be using getaddress and
validateaddress instead
Renamed threads to hobocoin
Addnew script checking threads
split and combine threashold now use all loaded wallets for max combine
number.
Bump Version and Bump protocol.
Added WatchOnly ability
Added importaddress used in watchonly addition
Added |
|
|
|
I don't really have these problems with orphans... I get some... but because I manually keep my blocks around 8-9k I don't see the shit ton that everyone complains about. My only complaint is that it's not done automatically, ala how paycon worked when we were having fun with our favorite soon to be jailbird Homero... small blocks gets combined through the wallet software. It's not the 30s, although that's not exactly what I was talking about when I said you shouldn't futz with the coin basics... I was talking more along with the increasing stake or whatever... the more you let loose on inflation the worse the coin will be.
EDIT: Oh and if you haven't already can you put the new wallet link in the first post... that's probably what is taking the exchange so long to update...
The wallet does combine automatically. The rules are: - same address - the input is at max time (30 Days) - It won't put you past the 250 max reward - and a few others. I will update the main post, but they compile from the main depo, which has the most current version. I let them know that. Feel free to open a ticket, it may help.
Yeah did the same with block sizes and always wondered what the fuss was about. But ... I'm experiencing how grim it CAN get. probably an extreme case I'll admit
I'm actually having to restart the wallet every now and then as transactions just start pending as offline and successful stakes are ~ 1:100
I imagine its got something to do with memory management and other things going on on my PC along with a couple of thousand blocks trying to stake at once.
Block numbers get out of hand fast if you're lazy so dug my own hole over here to some extent.
The issue of many blocks coming in from the outside also slow down wallet. Ala block spamming with 30 second block time.. |
|
|
|
Any tendency to increase block time, for any reason, is probably a mistake. As coins get more popular, they will start making shorter and shorter block times to be more attractive as currencies. Longer block times are penny wise pound foolish in this case.
I do agree with this to an extent. However I think the most transactions that have been in a block for HBN have been like 10... We will likely never even get close to capacity.. 90 seconds is still very quick.. Will the maximum stake of 250 HBN per block be increased to compensate for the 3X decrease in daily staking chances? TIA. ╥Aztek Actually this would not be necessary. The chance of getting to 250 woudl be less with longer block times, due to increase in difficulty. I hope not... don't screw with the basics of the coin... it is what it is and it's why the coin isn't being de-listed or valued at .00000001btc... or worse... dodge...
On the exchange side of things, cryptopia will take their sweet time getting around to updating as they always do... but as long as we're using the coin they'll keep it... even at 2.23GB of memory...
Fair enough, we can wait until block 6.0million and see what happens once PoW leaves us. I still feel like 30 seconds is way too fast. The original creator of the coin did not understand the implications of 30 seconds, and for the last few years the biggest complaints are CPU usage, wallet lag, orphans and lot of memory usage. All of which are exacerbated due to 30 second or faster block time. |
|
|
|
Out of interest does the number of transactions in a wallet have any effect on efficiency?
Only if you have to re-scan or re-sync the block chain. It takes longer for wallets that are larger. It also does slightly increase memory usage as you have more transactions. |
|
|
|
Any tendency to increase block time, for any reason, is probably a mistake. As coins get more popular, they will start making shorter and shorter block times to be more attractive as currencies. Longer block times are penny wise pound foolish in this case.
I do agree with this to an extent. However I think the most transactions that have been in a block for HBN have been like 10... We will likely never even get close to capacity.. 90 seconds is still very quick.. |
|
|
|
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. |
|
|
|
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.  |
|
|
|
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. 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. |
|
|
|
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/ |
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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 ? |
|
|
|
Getting this error on start up
Runaway exception
A fatal error occurred. HoboNickes can no longer continue safely ....
EXCEPTION: st9bad_alloc
std::bad_alloc
version 1.5.3.0
Windows 7 Pro 32bit
(taking a guess ... this is a 64bit wallet?)
No, it is 32 bit. Will work on just about every Windows. Likley whatever you did for you block chain download was not correct. You need to replace both blk001.dat and blk0002.dat and the entire txleveldb folder. If you don't do all 3 of these you will get errors as such. I've uncompressed the ZIP and re-apply the files, made sure the files were in the right place. Still getting the same error. C:\....1.5.3.0\HoboNickels-qt.exe in Runaway exception I copied over the backup'd wallat.dat before the first start up. Ok mabye those were bad zip file? You can try the one I am doing to hobonickels.info here in a bit, once it is done. I applied it to another computer and it came right up. |
|
|
|
Uploading a new bootstrap to hobonickels.info. http://ftp://ftp.hobonickels.infouser: hbn@hobonickels.infopass: H0b0Nickels Will take a few hours to upload, but should be a good fresh copy. Edit - Files name: block_chain_20170712.rar Size (once complete):3,609,497,600 |
|
|
|
Help please with hobonickels.info file, what it have to contain to connect? I have no connects with hbn net.
You can get nodes from the chainz website. https://chainz.cryptoid.info/hbn/#!networkJust get some of those and type "addnode IP add" in the debug/console |
|
|
|
Getting this error on start up
Runaway exception
A fatal error occurred. HoboNickes can no longer continue safely ....
EXCEPTION: st9bad_alloc
std::bad_alloc
version 1.5.3.0
Windows 7 Pro 32bit
(taking a guess ... this is a 64bit wallet?)
No, it is 32 bit. Will work on just about every Windows. Likley whatever you did for you block chain download was not correct. You need to replace both blk001.dat and blk0002.dat and the entire txleveldb folder. If you don't do all 3 of these you will get errors as such.  Damn. Was still trying to accumulate these. Oh well, I got some.
No worries, after the wallet comes back online the price will come down some. My guess is it stabilizes in the 300 range. Never thought it would be this high though.. |
|
|
|
Nice... One thing to keep in mind, that when a wallet is turned off (no deposits) the price can be artificially inflated due to lack of new coins. 1.5.3 update done here  Thanks! Went ahead and updated to 1.5.3.1. This will now allow you to start and stop staking with a click of a button or rpc command. Also as a startup switch. https://github.com/Crypto-Expert/HoboNickels/pull/29 Also do we have any Mac Compilers here? I do have an old Mac, but I have not done it before. So I can learn it, but it will take away from my dev time to set that all up. If someone can help out, that would be great! |
|
|
|
Cool, updated to 1.5.3 with no issue.
Looks like Cryptopia is in the process of updating their wallet.
Yes but they are saying they will not update until it is pulled into the main repo https://github.com/Crypto-Expert/HoboNickels. I have messaged Ahmed, but he is away. Does anyone have another contact for him? Edit: Ok I did get hold of him and he pulled it in. Mr reliable. Unlike devs that take 2 year vacations!  |
|
|
|
I updated hobonickels.info to make links correct. Not to much change to front page content. Does anyone want to give it some time to check it over make sure I didn't miss anything?
Also does anyone want to work on the wiki or news section? I will add a few news posts here soon, and maybe to the wiki, but it is very low priority. If others want to contribute just let me know. It is a private wiki page due to bots! But I can add others.
Thanks!
Glad to help Great. I will send you a message later today with user and pass. Anyone else? |
|
|
|
|
Show Posts
