Installed 1.5 beta 2 today. Looks good so far! (no issues). The network tab with the block explorer is really cool. Also like the new info screens (block/node/stake). The block explorer currently supports block and txid lookup. Are there plans to enable address lookup in the future? Stake for charity UI is another great addition. I noticed the icons for 'send' and 'charity' are the same which can be slightly confusing but no biggie. I've set it to donate 10% to F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL this month as a way to show my appreciation and support the dev  Thanks for the feedback and donations. Not necessary at all but thank you. That wallet has S4C running for Songs for Love so that will help support them as well. The info screens were available in 1.4 you just had to click the icons in the bottom right. Changing the S4C icon is in the works for final 1.5. I do have other plans for the block browser, including Address look-up. But for version 1.5 this is probably about it. |
|
|
|
Second Beta release of 1.5 is ready. Most of this dealt with the Block Browser. It needed a major work over. The code has been cleaned up and is now working with both PoW and PoS. The transaction page will now allow right click into the browser. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.8.0Please let me know if there are any issues. Thanks! |
|
|
|
I would add to this that it has historically been pretty accurate, up until the hole that nobody knew about hosed the coin. Once the fix was made, the steady progression of stakes had been interrupted and a whole swarm of stake ready wallets hit the network all at once. There were a number of unforseen problems with this, most of which were FAR more troublesome than the nvcs adjustment. Besides, it's likely to return to normal levels *IF* we all use coin control to spread out our blocks. Consider it incentive to not be lazy.
I will tell you all the issue. It is simple. This one line was changed: https://github.com/maxxine/TEK/blob/master/src/main.cpp#L39The base difficulty was lowered as part of the fix. This allows/causes a few things. 1) Easier/lower CPU intensive staking 2) Easier chance of attacking with PoS 3) Lower stake reward, as now the starting point of the reward calc is much lower (see here): https://github.com/maxxine/TEK/blob/master/src/main.cpp#L992-L1006 The chance of this going back to this difficulty are low, therefor the chance of getting the full reward (500%) are also low.. This can not be changed again without a hard fork. Yep. I posted about this but nobody cared. https://bitcointalk.org/index.php?topic=320404.2100 https://bitcointalk.org/index.php?topic=320404.msg8574529#msg8574529 Yup. Missed that post. But the question really is what was the underlying reason for this change. It didn't need to be changed to fix the stuck PoS block. It was extra on top of the other code that was changed. |
|
|
|
I would add to this that it has historically been pretty accurate, up until the hole that nobody knew about hosed the coin. Once the fix was made, the steady progression of stakes had been interrupted and a whole swarm of stake ready wallets hit the network all at once. There were a number of unforseen problems with this, most of which were FAR more troublesome than the nvcs adjustment. Besides, it's likely to return to normal levels *IF* we all use coin control to spread out our blocks. Consider it incentive to not be lazy.
I will tell you all the issue. It is simple. This one line was changed: https://github.com/maxxine/TEK/blob/master/src/main.cpp#L39The base difficulty was lowered as part of the fix. This allows/causes a few things. 1) Easier/lower CPU intensive staking 2) Easier chance of attacking with PoS 3) Lower stake reward, as now the starting point of the reward calc is much lower (see here): https://github.com/maxxine/TEK/blob/master/src/main.cpp#L992-L1006 The chance of this going back to this difficulty are low, therefor the chance of getting the full reward (500%) are also low.. This can not be changed again without a hard fork. |
|
|
|
Wow much quicker start up now for QT, changing that scan size did wonders!
Yes it did help. The thing that I like the best that has changed was the locking scheme. The GUI is a lot more responsive for most operations, like rescan operations. Which also helps with things like syncing, as the core won't be waiting for the GUI. On the surface it may see like the gui is less responsive when it comes to syncing, but that is only because the gui will be updated less often, so the time between updates is larger but the jumps in block counts will also be larger. Anyway thanks for feedback. |
|
|
|
Dropped in another bit of donation.
Cool I do appreciate it. At this point the CCE has been paid for and is good till 2015. I didn't get a chance to get a new wallet with a few new features and the updated splash screen going yet. The first beta of hbn took me a bit longer then I anticipated. But I hope to get to it this week. |
|
|
|
thanks to all! Errors was in wallet.dat. rescan, salwagewallet and repair didn't fix it, but import/export keys solved problem  Good to hear. Honestly I am a bit confused as to what happened. You sent coins to yourself but ended up missing some other coins? And you were sure these just weren't change address. Anyway glad you got it sorted out. |
|
|
|
If you access coin control you'll find them under the address you mentioned.
Just noticed your signature. Cool Address! |
|
|
|
Like the new S4C addition. Will I still have to enable S4C every time I start up the wallet?
Nope, it is written to the wallet.dat file. So it will persist between shutdown and start up, and moving from one client to another. |
|
|
|
Thanks Fixed. I am actually going to do a production compile today and release a beta version, so I'll see if I missed anything else. Just tried to compile: Makefile:320: recipe for target 'HoboNickels-qt' failed Code: cd ~/cryptos && rm -rf HoboNickels && git clone git://github.com/Tranz5/HoboNickels && cd HoboNickels && qmake-qt4 HoboNickels-qt.pro && make
David I'll look into your issue as soon as I can. I did change the pro file a bit. See if any of these recent commits maybe your issue. https://github.com/Tranz5/HoboNickels/commits/master/HoboNickels-qt.pro |
|
|
|
I have the first beta version for 1.5 ready. I'll put up the full change log on github in the next day or so. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.7.0Although I have had no issues, I do highly suggest you take the time (after you shutdown the client) to backup your wallet(s).dat, blk0001.dat and database/txleveldb directories, before starting up the new client. Please let me know if you see anything odd or have any issues. Enjoy! |
|
|
|
src/qt/blockbrowser.{cpp,h} are not in HoboNickels-qt.pro, therefore src/walletview.cpp:58: undefined reference to `BlockBrowser::BlockBrowser(QWidget*)'
Thanks Fixed. I am actually going to do a production compile today and release a beta version, so I'll see if I missed anything else. |
|
|
|
Any chance the new wallet version will be more efficient with memory and CPU usage? The current wallet uses over 50% CPU and almost 500MB of memory.
CPU Yes, although more so once we are in 1.5. Memory no, the more wallets, the faster the block chain, the higher the memory grows. You will notice it will all clients. There are some things to help, but not enough to make much of a difference yet. |
|
|
|
Good work Tranz. When 1.4.7 beta will be released? I wasn't planning on releasing it till 1.4.9, but I may go head and throw one up here this weekend. |
|
|
|
|
Show Posts
