What effect would be created by increasing the minimum required coins to stake?
Changing the minimum coin age would put more coins out there available for stake. This would increase the net stake weight, which would increase the PoS difficulty, which would lower the Annual Stake Percentage, which would help keep inflation from running away. At least that's my theory. Yeah. Sorry, I guess I wasn't super clear. I was saying rather than raising block target, what if instead the minimum number of coins to create stake was raised? Possibly raise it to 1000hbn, which is approxiamtely $5 right now. It seems like it could help alleviate a lot of the issues that are occurring including the CPU/memory reqs as smaller claims could be effectively ignored by the wallet, and would also force what PoS was originally intended for, which was allow for people with significant investment in the chain to have a majority. I want more people staking now less. |
|
|
|
presstab has a solution for the cpu bottleneck
I think less blocks is fine - orphans also cause unnecessary strain
Yes lots of solutions can be done for CPU. That is the easy part. I am leaning towards 45 -50 sec target time, and stake starting age of 1 day right now. It is not purely my decision. What effect would be created by increasing the minimum required coins to stake? Changing the minimum coin age would put more coins out there available for stake. This would increase the net stake weight, which would increase the PoS difficulty, which would lower the Annual Stake Percentage, which would help keep inflation from running away. At least that's my theory. |
|
|
|
presstab has a solution for the cpu bottleneck
I think less blocks is fine - orphans also cause unnecessary strain
Yes lots of solutions can be done for CPU. That is the easy part. I am leaning towards 45 -50 sec target time, and stake starting age of 1 day right now. It is not purely my decision. |
|
|
|
I also think 10 days minimum stake time is too long. Instant gratification sells.
it can be more but not be too late please because wait for any thing is unbearable for us. So my first gut response was no, I am not changing the staking algorithm. However I decided to check out how the money supply was looking.  As you can see the annualized money supply rate should be heading closer towards zero, but is sticking in the 70% range. Also, the time between blocks is averaging 20-22 seconds. This is hard to see from the chart, but the time between each bar(100,000 blocks) should be about 35 days, but speeds up as we begin more aggressive staking. You can click on the chart to download the spreadsheet. So we can slow down the money creation but allow blocks to stake earlier. This should cause the PoS weight to increase which would lower the annualized staking percentage. We can also, or only, change the time between blocks to increase a bit to say 45, which would again slow down the annualized money supply by increasing the difficulty of staking. Anyway this is just thoughts for now. What say ye? Any change that I would make, would come well after CPU is lower and possibly memory. As more coins in your wallet trying to stake or having to do more hashing will increase load. So we have to take care of that first. But good to talk about this now. |
|
|
|
i see nova is about to delist hbn, i didn't know they listed lol,
anyway maybe dev could check the subject
I have very little, or rather no, control of the market. Either people put coins out there and trade or they don't. I would love to see more trading across multiple platforms, but this is up to you all. |
|
|
|
I also think 10 days minimum stake time is too long. Instant gratification sells.
it can be more but not be too late please because wait for any thing is unbearable for us. So my first gut response was no, I am not changing the staking algorithm. However I decided to check out how the money supply was looking. As you can see the annualized money supply rate should be heading closer towards zero, but is sticking in the 70% range. Also, the time between blocks is averaging 20-22 seconds. This is hard to see from the chart, but the time between each bar(100,000 blocks) should be about 35 days, but speeds up as we begin more aggressive staking. You can click on the chart to download the spreadsheet. So we can slow down the money creation but allow blocks to stake earlier. This should cause the PoS weight to increase which would lower the annualized staking percentage. We can also, or only, change the time between blocks to increase a bit to say 45, which would again slow down the annualized money supply by increasing the difficulty of staking. Anyway this is just thoughts for now. What say ye? |
|
|
|
|
There are no forks that I know of. I have done a few syncs recently. One from 2 years ago, no issues. And now I am trying a full one. The full one has had one issue. Going form 2y 250d to 23mins instantly at one point. I knew it wasn't correct, so I restarted and it picked back up correctly, and is moving on.
Have you tried to restart the wallet?
Check your peer list and make sure the peers have the correct number of blocks, perhaps you are on another coin that is similar?
Using that sync from HCLivess can save sometime as well.
If you do get up to correct block and still not right balance, then you can restart with the -rescan, or more harsh-zapwallettxes. Be patient, it will take time!
|
|
|
|
Finally got back to the dev server. Took me about 20 mins but I remember how to compile!  Put in leveldb 1.19 and testing that out right now. Seems good so far. |
|
|
|
i guess swap is inevitable
Nope. Totally against everything crypto stands for. And I will never do it. |
|
|
|
Tranz happy to see you back sir! Hope to see some great progress made. If you were able to get the resource consumption reduced for HBN, I think it would really be a game changer.  For info above... HYP is at 1028083 blocks with 462MB memory usage. HBN is at 5242362 blocks with 2.2GB... so the memory usage is about equal per block... Keep in mind that blocks is not the only contributor to memory consumption. I have about 100mb more memory consumption than that on HYP, and thats running headless. So transaction count is a major contributor. Yes presstab, good to be back! Yes the number of transaction in your wallet is also a factor, albeit much less then number of blocks. |
|
|
|
...
Been trying to get my bitcoin wallet syn'd from start. It has been 5 days and numerous problems. Hopefully it finishes. But still estimates 2+ days....
If you haven't synched a bitcoin wallet for a while, you are in for a little surprise. Getting closer, 6 hours left. Has taken about 3 days so far. |
|
|
|
|
Well I got the first step of the dev server complete. I got my wallet syn'd up. It was about 2 year behind, and took a little more then 2 days to catch up. I don't think 1 day per year is too bad.
Been trying to get my bitcoin wallet syn'd from start. It has been 5 days and numerous problems. Hopefully it finishes. But still estimates 2+ days....
|
|
|
|
Not that I've seen...
I'm thinking the only way to get the memory usage down is to decrease the number of blocks... or use compression... either way it's hard because the blockchain needs to be from #0 to current... I'm really thinking a new genesis block like compression where all current balances get fed into block #0... call me crazy...
I think you could be able to unload spent inputs, and only load in unspent. Also you could even only load in the last 100 days of unspent or something. Would require more disk reads and more CPU usage, but could save memory. Anyway just a thought right now, till I can dig into it more. |
|
|
|
Hey, is there any way to find the effective interest rate right now? I know it changes with difficulty, just looking for ball park estimate.
Click the staking arrow or network -> Current POS info (may take a few clicks), it will bring up a box with information. |
|
|
|
Current requests:
Change S4C to 100% - I think I will likely do 75 or 90% for the first change. Then if that goes well change to 100%. But I can bump it, yes.
Lower CPU - This will be one of the first one. Multiple changes for this.
Lower Memory - Most important but also most difficult. Will take much time, but will begin to investigate this and see what can be done. Need help from the crowd on this one. What POS coins are out there that have the least memory? New coins don't count. Have to have few years under their belt.
What else?
For info above... HYP is at 1028083 blocks with 462MB memory usage. HBN is at 5242362 blocks with 2.2GB... so the memory usage is about equal per block... Right on, so are there any that are lower per block? Mint, nvc, black coin, ppc? Ect... |
|
|
|
Current requests:
Change S4C to 100% - I think I will likely do 75 or 90% for the first change. Then if that goes well change to 100%. But I can bump it, yes.
Lower CPU - This will be one of the first one. Multiple changes for this.
Lower Memory - Most important but also most difficult. Will take much time, but will begin to investigate this and see what can be done. Need help from the crowd on this one. What POS coins are out there that have the least memory? New coins don't count. Have to have few years under their belt.
What else?
GenStake is another PoS/PoW coin that runs much less CPU and memory than HBN. 2GiveCoin runs with very little resources but is much differently structured kind of PoS/PoW coin. Hyperstake and Truckcoin are also lower in memory and CPU use but do not use PoW. (Truckcoin runs higher on CPU use) The GreenCoin daemon runs with very little CPU and memory use but is also PoS only. However greencoin has problems of its own which i need to take care of when i get time. Its based on the old blackcoin. Likely going to be upgraded to the new blackcoin base when i have some time. The main issue with it is that peer discovery isnt working (may be due to faulty seed nodes) and the blockchain sync stalls at certain blocks Ahmed Hi Ahmed, good to see you still around. Hopefully I can keep you busy with a few pull requests in the next few months.. hehe. |
|
|
|
Halving the stake reward maybe? I know it's been mentioned before.
I figured it out. Just typed in threshold limits on command line, super easy. On another note the blockchain doesn't seem to be synchronizing. I'm doing it over wifi, not sure if that's an issue. Seems to be stuck at 3 years 310 days. How long should it take? AM I doing something wrong? Try downloading and using a zipped blockchain. It won't be three years behind, it will probably be a few months behind instead. http://108.61.216.160/cryptochainer.chains/chains/HoboNickels_blockchain.zipAfter I download it, do I need to do anything specific with it? Thanks! Unzip it and put the contents of the unzipped folder in the HoboNickels folder inside appdata\Roaming, Appdata is a folder that's hidden by default in windows. To see it you have to go to appearance and personalisation in the windows settings, select folder options, then select "show hidden files, folder or drives". You can find your HoboNickels folder in appdata at C:\Users\<your username>\AppData\Roaming\HoboNickels where <your username> is your windows username. Thank you Mike. I'm really getting frustrated. After downloading your link and inserting zip file into appdata/roaming it won't unzip...says zip file is invalid. So right now I can't synchronize the blockchain via wallet and cant open downloaded zip file. Grrrr. Need help. Thank you. Do you have peers? use the peer connections from crytopia coin info page and in the debug window console type |
|
|
|
Current requests:
Change S4C to 100% - I think I will likely do 75 or 90% for the first change. Then if that goes well change to 100%. But I can bump it, yes.
Lower CPU - This will be one of the first one. Multiple changes for this.
Lower Memory - Most important but also most difficult. Will take much time, but will begin to investigate this and see what can be done. Need help from the crowd on this one. What POS coins are out there that have the least memory? New coins don't count. Have to have few years under their belt.
What else?
HYP does a pretty good job for what you're looking for memory and cpu as well as resolves the S4C issue. I also mention some general issues most crypto wallets have in the last few pages of the thread. Have a look: https://bitcointalk.org/index.php?topic=678849.6360Yes I know HYP well. Again look at # of blocks vs amt of memory used. The ratio is still close. I authored S4C originally I know what it can and can't do. I am just not sure what it should do yet.. |
|
|
|
Halving the stake reward maybe? I know it's been mentioned before.
This is already part of the code. It simply require active wallets staking. As the staking difficulty goes up the reward goes down. We could tighten it, but a hard fork is my last thing I want to do. |
|
|
|
GenStake is another PoS/PoW coin that runs much less CPU and memory than HBN. 2GiveCoin runs with very little resources but is much differently structured kind of PoS/PoW coin. Hyperstake and Truckcoin are also lower in memory and CPU use but do not use PoW. (Truckcoin runs higher on CPU use) The GreenCoin daemon runs with very little CPU and memory use but is also PoS only.
CPU will be solved, so take that out of the equation. But with memory, you have to compare apples to apples. We are at block 5.2 million. What are those coins at? When HBN was only at block 1 mill, it used a reasonable 300megs. More blocks, more memory. Run a spread sheet on Memory vs number of blocks, and tell me which is the lowest. We can go from there. |
|
|
|
|
Show Posts
