Hi every one, I am another HBN supporter and was reading along with your discussion. This is what I make of it: If you check the chart of the the money supply, you'll notice the constant increase of HBN which consists of 14400 HBN every day being added to the existing amount. (makes sense: 1 block of 5 HBN every 30 sec.) POW and POS are competing for this daily amount but no matter much POS or POW, 14400 cannot be exceeded. So diff rises over time and stake% lowers over time. One influencing the other as well in order to maintain 14400 every day. So I think with a coincap of 120M we have 120M/(14K4*365) = 22 more years before this point is reached at which I understand from Tranz, nothing particular will happen anyway. And adding a daily fixed 14K4 also means inflation will be less and less every year. I would like to add that in my opinion, HBN is well designed, well balanced and well developed. That's why I am stacking them. As much as I can get hold of. Without being greedy of course  http://hobonickels.info/charts.phpTrue on a lot, but a few misconceptions. The algo only cares to keep the blocks at 30 seconds, what the block reward is, does not influence it. Looking at a few stats. We are at day 274.775 in the chain. Each day we try to make 2,880 blocks. So 274.775 * 2,800 = 791,352. The current block is 788,600 So we are slightly below the target blocks. But pretty close. PoW only should produce 14,400 coins a day. So at 274.775 days, we should be at 3,956,760. We are currently at 4,026,732.041296. Slightly ahead of PoW only target. Remember the current coin supply also takes into account the fees that are destroyed. Not sure on how much that really is right now. Maybe a few thousand at most. So in next year. I believe the inflation rate should pick up. Then by year 3 or 4, it should begin to slow. Eventually it could slow to lower then PoW only. This should be the goal, as we approach the 120MM mark. |
|
|
|
|
The 120 MM is a place holder in the code, if you trace it down you will see there is nothing preventing staking or mining from just that one line.
The real goal is to approach this amount over long time and keep it just out of reach.
One thing to realize is that as we enjoy more staking on the network, the payment(interest) goes down. So if every coin was staking the yearly ROI would not 100%, it will drop and the inflation rate will slow.
|
|
|
|
Tranz, Any thought on changing the algo to a more energy efficient one as well as ASIC resistant? With the first ASICs shipping around the end of May, this might be worth considering for the early adopters as well as new small miners who don't have money to burn like the whales...  asic is nice for this coin, dont fork!!! ASICS will only increase the value. Hold, don't fork. Correct I am not looking to fork for mining change. Remember as time goes, the scrypt part of this coin will mean less and less. PoS will continue to gain more and more of the mining share. Switching to a new PoW would be counterproductive at best and could cause huge problems. |
|
|
|
i dont understand the coin control, but i stake alot:
Nice looking history |
|
|
|
|
Version 1.4 takes care of the staking issue. There is almost nothing that has to be done. I upgraded my brothers computer, he had tons and tons of very small blocks down to .042. They had been splitting from the 5 blocks that he had mined. His version 1.3 couldn't handle it and it was unresponsive. After the upgrade, I did nothing but let it all go. Not a single problem and within a few mins it was staking the blocks.
I did show him and tell him to combine all his blocks of less then 1 into a bigger block. I said wait till all your little ones add up to 100 then combine them. But he is staking just fine with 1000+ blocks between 10 and .7..
Now this does take a full core out of your CPU. So if you want to be more efficient, then creating a new address in your wallet and combining blocks is also ok. I personally am good with giving HBN 25% of my quad core.
|
|
|
|
Well it's not really the same bug, the crashes I get is at startup. bitcoin's crashs seemed to happened some time after being running. But it's still somewhat random as it happens on some machines and not others. I have the same issue with 4 of the qt client I tried on the same machine. I just assumed it could be related since it was a new feature, but then again might be something completely unrelated. I could be due to leveldb. Quick way to test it would be to try version 1.2, just see if it crashes. https://github.com/Tranz5/HoboNickels/releases/tag/1.2.2.3It doesn't use leveldb. MarketNeutral. I did look through that thread a while ago. I'll give it another once over. |
|
|
|
We could improve some features on the mac wallet too, like notification "bubbles" (I don't know how to call them but the new bitcoin client and dodge client have it, looks like the bubble popup from windows but it's in the notification top right of the screen).
Also, I was talking with MystPhysX, and he suggested that the random crash of the mac wallet on some computer might be linked to the leveldb database (there was a bug on the bitcoin client 0.8.3 version I believe).
Since this a new feature for HBN, I taught it made sense. What do you think about that Tranz?
I was going to give this a shot. https://github.com/rat4/blackcoin/commit/a9c889cedaa9f06779107f12eaab7383a9884d88I used the newest version of leveldb, that was in btc .8.5. I didn't know the mac clients where getting random crashes. I just knew that sometimes the index becomes corrupt. Only manifested it self after shut down/restart. But yes, i assume they are related. |
|
|
|
I've updated all my wallets to the latest version. So far so good. I had to redownload the blockchain and later clear orphans with the 'repairwallet' command, which is a good command people ought to know anyway. In the OSX version, the text and graphics don't fit properly inside the 'New', 'Load', and 'Unload' buttons, and upon first starting, the window needs to be resized so the 'Recent Transactions' text doesn't overlap—a superficial and low-priority issue, since the wallet functions properly. OSX compiling is quirky, I know. The Windows and Linux versions are fine.
Compared to the early Thundertoe wallet—and to nearly all other altcoin wallets—Hobonickels really stands out in terms of its features and development.
Keep up the great work, Tranz.
Mac wallet is being worked on by Unick right now, and I believe Tranz is going to be helping get everything sorted out in the near future. I think the original goal was to successfully compile the client for Mac for version 1.4 wallet. Now that has been accomplished, some of the bugs will be worked out over time. And yes HBN has a great wallet. How many other coins have multi-wallet? Yes I will be able to trouble shoot the mac wallet, now that unick can compile and test. :-) I am still having issues with my dev box. So I am down for now. |
|
|
|
Has there, or will there be a fork due to the update?
There is no fork with this update. We will be discussing an upcoming update which most likely have a few forks in it, to fix some key issues. But as of right now all chains are compatible . |
|
|
|
Got 2 crashes while upgrading from 1.4.0.0 to 1.4.0.1 (all files were backuped, not "clean setup", old blockchain was left and started to reindex).
Going back to 1.4.0.0.
Update: reroll to 1.4.0.0. went fine, may be needed to do a clean setup while upgrading to 1.4.0.1.
What was the crash? You can try to start the 1.4.0.1 with -datadir=c:\hbn2 -listen=0 (will need to make that directory first) This will start it up in a fresh in that directory. After it is fully up to sync, you can shut it down(do 1 start up to make sure it works. ). Then you can swap out txleveldb and blk0001.dat into the normal directory and start 1.4.0.1 with no switches. I just got my brothers laptop up to speed, I used my blk0001 and txleveldb(from April 10th)( http://www.fileswap.com/dl/SnNNULZqH/ ), and moved those into his directory. Started up 1.4.0.1 and 10 min later all sync'd up and staking! |
|
|
|
i am running another coin wallet on the same computer and for some reason when i run both hbn wallet goes out of sync and won't sync until i closes the other wallet
is there a way to fix this?
You could try starting the client with -listen=0 or put that in the config file. Make sure that all the wallets are using are on different ports. |
|
|
|
Quit wallet, start latest "fast start" version: HoboNickels-qt: src/kernel.cpp:395: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.
Well quit was fast! I preferred previous non-fast versions..  The same bug was in the old version as well. I have a 5k HBN bounty for help in fixing it. https://cryptocointalk.com/topic/9588-hbn-trouble-shooting-guide-assert-failure/ |
|
|
|
Hey guys, sorry if this is a stupid question but is there a reason Hobonickels doesn't have the kimito gravity well?
HBN has always adjusted the difficulty for PoS/PoW for every block since the beginning. Changing to a more complex system to accomplish the same means is irrelevant. |
|
|
|
sigh...this has been such a painful blockchain sync. I'm running 1.4.0.1, have had checkpoint warnings off and on throughout the sync, which I assume are ok for now, seems all my peers are on older versions, and its been going > 24hrs now and still ~60k blocks to go. I've got a bad feeling its not going to be legit when its done, either.
Attempted using the linked blockchain from April 6th (or whenever), but it just started at block 0 anyways. Maybe I'll revisit that again if this ends up not working out as it is.
I've been getting the pi to re-sync. So far 3 days in at 670k. Most of the issue seems to be with new check points coming in and causing a slow down by searching for orphans.. I shut down at 400k and take a snapshot, just in case. Don't worry about checkpoints until you are 100%. Then a quick shutdown/snapshot/restart as a quick procedure to make sure all is good. I think we need a few fast dedicated seed nodes out there as well. Bootstrapping is quickly being the fastest method. |
|
|
|
i am using 1.4
all i did is i typed repairwallet and nothing else
If it is for the default wallet that should work. Otherwise you can also use the menu Wallet->repairwallet command. You will need to give focus to that current wallet first that has the orphans. |
|
|
|
|
HBN is on poolwarz.com, not sure if it ever gets hit or not.
|
|
|
|
|
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
|
|
|
|
i did the repairwallet command but it didn't clear the orphans
Which version are you using ryan? |
|
|
|
|
Show Posts
