Great information, thank you!
I tried, but these commands do not work: "Method not found".
Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 105. (Read 478852 times)
April 19, 2016, 10:29:07 AM
April 19, 2016, 10:07:39 AM
nice coin, but it seems impossible to sync without bootstrap...
Yes, the coin could use some maintenance, but nobody wants to do it.
The only thing that needs to happen is HBN users quit microstaking small amounts which is what is killing the sync with orphans.
If everyone would just use coin control, to correct the orphan issue the network would run smoothly.
Combine your coins into blocks of a minimum of 5000 or 6000 HBN per Block and sync will return to normal.
A great feature to add would be auto combine.
This feature doesn't need to be added because it's already there.
At your console prompt type: 'splitthreshold 1000' and blocks won't split any more when they are smaller than 1000.
You can choose any threshold you like as long as it is smaller then the total amount you own on that address divided by 500
So in order to use 1000 as a splitthreshold you need at least 500x1000= 500.000 HBN
As you understand, this is a perk for people who own a lot of HBN because the big wallets provide most of the safety for the HBN blockchain.
So everyone who is tired of manually combining, buy more HBN and let it handle itself. It's not that HBN is very expensive right now..
BTW, the same thing goes for 'combinethreshold 1000' to combine smaller blocks when they stake. This one goes as far as your stash divided by 250.
Cheers!
April 19, 2016, 09:43:17 AM
nice coin, but it seems impossible to sync without bootstrap...
Yes, the coin could use some maintenance, but nobody wants to do it.
The only thing that needs to happen is HBN users quit microstaking small amounts which is what is killing the sync with orphans.
If everyone would just use coin control, to correct the orphan issue the network would run smoothly.
Combine your coins into blocks of a minimum of 5000 or 6000 HBN per Block and sync will return to normal.
A great feature to add would be auto combine.
April 19, 2016, 01:04:27 AM
nice coin, but it seems impossible to sync without bootstrap...
Yes, the coin could use some maintenance, but nobody wants to do it.
The only thing that needs to happen is HBN users quit microstaking small amounts which is what is killing the sync with orphans.
If everyone would just use coin control, to correct the orphan issue the network would run smoothly.
Combine your coins into blocks of a minimum of 5000 or 6000 HBN per Block and sync will return to normal.
April 18, 2016, 09:29:35 PM
nice coin, but it seems impossible to sync without bootstrap...
Yes, the coin could use some maintenance, but nobody wants to do it.
April 18, 2016, 08:20:43 PM
nice coin, but it seems impossible to sync without bootstrap...
April 17, 2016, 01:55:20 AM
April 16, 2016, 05:24:52 PM
i wanna buy them too but i already buy all the dmd what i could, no btc left 
April 16, 2016, 05:01:32 PM
those guys dumping right now are ruining the coin
it's ok, i'll buy them all.
April 16, 2016, 04:12:39 PM
those guys dumping right now are ruining the coin
April 16, 2016, 01:47:15 PM
someone is duping his hbn 500sat
April 14, 2016, 11:27:06 PM
Hobonickels blockchain, current as of 4/14/16, is available on CryptoChainer.com
April 14, 2016, 04:28:16 PM
so each time you making new blocks ?
i let my run 24/24
i only make new block with the very small ones
i let my run 24/24
i only make new block with the very small ones
Yes,
with 6000 HBN per block , I activate my wallet every 14 days and all of my blocks stakes within 24 hours , without going over the max cap.
Consider the fact that HBN tries to stake every 30 seconds, so there is a maximum of ~ 2880 times per day that interest can be earned.
Everyone that is keeping their HBN very low so they don't have to worry about the max cap , is using up most of that 2880 chances to stake as few as 70 HBN.
This causes massive amounts of orphans , which would be ok if it was not so bad it was actually blocking the ability of some wallets to sync.
If a large amount of users just combine their coins into blocks with higher amounts, it will be a more efficient use of the limited chances per day to stake.
Example, I am trying to sync HBN from scratch on my VPS, so I can offer a HBN bootstrap.dat & blockchain snapshots so others don't have to wait to sync from scratch,
but the orphans storm is so bad , my wallet can sit at 92 days to go for 48 hours and get nothing but orphans and never get any closer to getting synced, that is a major issue and fewer competing blocks will decrease the orphans and make HBN a lot better & smoother to use for everyone.
Plus you will earn more HBN due to increased compound interest.
April 14, 2016, 02:56:22 PM
so each time you making new blocks ?
i let my run 24/24
i only make new block with the very small ones
i let my run 24/24
i only make new block with the very small ones
April 13, 2016, 08:22:48 PM
Easy way to say this " You're Wrong! "
Your Blocks are going over the max stake cap because you don't have enough weight per Block to stake, and when they do achieve enough weight they are over the max stake cap.
I keep exactly 6000 HBN for every one of my Blocks, open my HBN wallet every 14 days and all of my blocks staked within 24 hours under the max stake cap.
So if you are going over the max cap and I am not, whose system do you think is better configured? Hmmm?
And to correct the error of apparently all of your Math Teachers.
http://www.basic-mathematics.com/simple-vs-compound-interest.html
Your Blocks are going over the max stake cap because you don't have enough weight per Block to stake, and when they do achieve enough weight they are over the max stake cap.
I keep exactly 6000 HBN for every one of my Blocks, open my HBN wallet every 14 days and all of my blocks staked within 24 hours under the max stake cap.
So if you are going over the max cap and I am not, whose system do you think is better configured? Hmmm?
And to correct the error of apparently all of your Math Teachers.
http://www.basic-mathematics.com/simple-vs-compound-interest.html
Quote
As you can see, compound interest yield better result, so you make more money.
The sooner you stake the more compound interest you can earn. April 13, 2016, 08:44:54 AM
Quote
You should make at least 4000 to 5000 HBN per block,
1. because you are losing out on compound interest.
2. HBN has too many orphans as it is , the more people that consolidate their HBN into fewer blocks the less orphans that will be generated and the smoother the HBN network will run.
Blocks with 4000 or 5000 should stake before the max cap affects you.
1. because you are losing out on compound interest.
2. HBN has too many orphans as it is , the more people that consolidate their HBN into fewer blocks the less orphans that will be generated and the smoother the HBN network will run.
Blocks with 4000 or 5000 should stake before the max cap affects you.
when i check my wallet, you are wrong, i have blocks bigger than 2000 and with have more than 250hbn reward so i lose definitely reward with big blocks
and you not losing interest with small block, they just need litle more time bloks around 1000 looks good because if they orthan they still can shake with reward below 250
if your 4000 block make orphan you lose because it s more than 250 after
April 13, 2016, 04:11:00 AM
And no transaction above 8500 HBN at this time, because this produces a first stake reward slightly below the limit of 250 HBN.
There are two metrics in the HBN client:
+ Stake Split Threshold: 5.00 HBN
+ Stake Combine Threshold: 10.00 HBN
This should solve the problem with manually combine small stakes, if they could be configured individually. But I don't know, if this is technically possible. If it is, make it configurable for the next version of the client. Perhaps these thresholds can be made adaptive automatically, in dependancy of the stake size.
There are two metrics in the HBN client:
+ Stake Split Threshold: 5.00 HBN
+ Stake Combine Threshold: 10.00 HBN
This should solve the problem with manually combine small stakes, if they could be configured individually. But I don't know, if this is technically possible. If it is, make it configurable for the next version of the client. Perhaps these thresholds can be made adaptive automatically, in dependancy of the stake size.
April 13, 2016, 01:35:40 AM
i already move the wallet to an other computer, because i started a new wallet on that one
and delete the old when all is transferred , i make blocs between 500 -2000 hbn with the coins what have less than 2 days
so i don't loss to much stakes days
i also clear the log, see what happen, and i keep the old block what won't shake, maybe could see something in the log
and delete the old when all is transferred , i make blocs between 500 -2000 hbn with the coins what have less than 2 days
so i don't loss to much stakes days
i also clear the log, see what happen, and i keep the old block what won't shake, maybe could see something in the log
You should make at least 4000 to 5000 HBN per block,
1. because you are losing out on compound interest.
2. HBN has too many orphans as it is , the more people that consolidate their HBN into fewer blocks the less orphans that will be generated and the smoother the HBN network will run.
Blocks with 4000 or 5000 should stake before the max cap affects you.
almost all folks know the drill, i suspect smth was done deliberately,
at least what i see in AMS network is nothing but a huuuge pile of garbage
at least what i see in AMS network is nothing but a huuuge pile of garbage
Well , if it is being done on Purpose, if everyone else combines their coins into 4000 & 5000 per block it should help counter that.
FYI:
Just looked at Presstab Block explorer (Stake Weight Spent)
http://www.presstab.pw/phpexplorer/HBN/index.php
The problem is too many small blocks, average amount is 30 to 500 HBN per block that are causing all of the sync congestion.
People start combining blocks and it will help fix this issue.
April 13, 2016, 01:23:07 AM
VERY IMPORTANT
Syncing Tips for PoS
Please Keep your Wallet Locked when you are not Synced with the network if you have coins in your wallet.
The Orphans that are being generated are greatly slowing down syncing process for everyone.
(If you are not fully synced , PoS will not mint more coins for you only orphans are generated.)
If you have not encrypted your HBN wallet do so and only Unlock it for PoS after Fully synced.
Thanks.
FYI:
Cause My HBN Debug Log looks like this
Syncing Tips for PoS
Please Keep your Wallet Locked when you are not Synced with the network if you have coins in your wallet.
The Orphans that are being generated are greatly slowing down syncing process for everyone.
(If you are not fully synced , PoS will not mint more coins for you only orphans are generated.)
If you have not encrypted your HBN wallet do so and only Unlock it for PoS after Fully synced.
Thanks.
FYI:
Cause My HBN Debug Log looks like this
Quote
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=eb0b2cb1e947ff10eaa9
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=1c45da5cae97134b508c
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=5bc1c2a9d8755350a3e9
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=a410f0219e9859d471b7
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=f8e5a7fbd9e795c74ceb
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=d528ccb3ef7be210ced1
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=24c205e72a47ea922160
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=b5c23b8c15ad4afc60d1
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=e20fecc554ba7c29f398
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=f32f543ed7fbf69ecbf8
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=38ed71a6aa70f72c5606
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=283b7ff355ae0eb61ba3
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0687f044bf48c136cb65
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=02a0baf805c10635944b
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=859b935870aab0b07ca6
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=4c35c0c371338ee91575
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=ca31293354248f8c94f9
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=e333fa13dfaba9b9ae6b
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=b848b75d8050f31d4652
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=45c81857e6d0519d1fc0
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=13a66d5ba4b672b32199
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=59bc1476b91f5e5f5b07
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=7aaafb76efcd6d969b34
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=2d0a42c4bb528a87161c
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=97491432a6d3bc546594
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=2a95be3a19d412b16ec1
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=d9780b19a839b7dc00e5
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0909d7a324e103124cef
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=ab674b44b6295564719f
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=e90d53b0754d998b2399
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0853cc5477cb8fbc7a36
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=b4e891ee21db9b80d279
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=d65c2adfe7e73807ad7a
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=9df03d14c70c4276baaf
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0edaf0ef4f4ca105648c
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=4ac9666a373305b82ceb
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=1c45da5cae97134b508c
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=5bc1c2a9d8755350a3e9
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=a410f0219e9859d471b7
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=f8e5a7fbd9e795c74ceb
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=d528ccb3ef7be210ced1
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=24c205e72a47ea922160
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=b5c23b8c15ad4afc60d1
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=e20fecc554ba7c29f398
2016-04-13 06:21:24 ProcessBlock: ORPHAN BLOCK, prev=f32f543ed7fbf69ecbf8
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=38ed71a6aa70f72c5606
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=283b7ff355ae0eb61ba3
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0687f044bf48c136cb65
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=02a0baf805c10635944b
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=859b935870aab0b07ca6
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=4c35c0c371338ee91575
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=ca31293354248f8c94f9
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=e333fa13dfaba9b9ae6b
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=b848b75d8050f31d4652
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=45c81857e6d0519d1fc0
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=13a66d5ba4b672b32199
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=59bc1476b91f5e5f5b07
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=7aaafb76efcd6d969b34
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=2d0a42c4bb528a87161c
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=97491432a6d3bc546594
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=2a95be3a19d412b16ec1
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=d9780b19a839b7dc00e5
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0909d7a324e103124cef
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=ab674b44b6295564719f
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=e90d53b0754d998b2399
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0853cc5477cb8fbc7a36
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=b4e891ee21db9b80d279
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=d65c2adfe7e73807ad7a
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=9df03d14c70c4276baaf
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=0edaf0ef4f4ca105648c
2016-04-13 06:21:25 ProcessBlock: ORPHAN BLOCK, prev=4ac9666a373305b82ceb
April 12, 2016, 09:07:54 PM
i already move the wallet to an other computer, because i started a new wallet on that one
and delete the old when all is transferred , i make blocs between 500 -2000 hbn with the coins what have less than 2 days
so i don't loss to much stakes days
i also clear the log, see what happen, and i keep the old block what won't shake, maybe could see something in the log
and delete the old when all is transferred , i make blocs between 500 -2000 hbn with the coins what have less than 2 days
so i don't loss to much stakes days
i also clear the log, see what happen, and i keep the old block what won't shake, maybe could see something in the log
Jump to: