Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 48. (Read 478852 times)
September 26, 2017, 03:15:09 AM
I like this realistic thinking. And apply to your test team
September 25, 2017, 08:11:08 PM
Since we now have a network that appears to be fairly stable. I am going to code up some of the user requests we have had over the days.
Here is what I have so far anything else I maybe missing?
What else?
I want to focus my time for now, on bettering the wallet and network, continuing to re-base with newest bitcoin, creating a light weight and Android wallet that can stake, and adding other functionality.
Here is what I have so far anything else I maybe missing?
- Fix Coin Control to only show weight after 8.8 days (Temporary until fork is coded and date set)
- Allow for larger split/combine threshold settings
- Allow for 100% stake for charity
- Fix the estimated time to stake in gui
- Code up stub function, but do not yet implement the stake modifier change. To get stake min at 1 day.
What else?
One step closer to decentralized crypto exchange. Hbn should jump on the train.
https://bitsonline.com/first-litecoin-bitcoin-atomic-swap/
Seqwit is a huge undertaking. I would love to implement it. But unless I have a team of developer and testers, it is not going to happen anytime soon. https://bitsonline.com/first-litecoin-bitcoin-atomic-swap/
I want to focus my time for now, on bettering the wallet and network, continuing to re-base with newest bitcoin, creating a light weight and Android wallet that can stake, and adding other functionality.
September 24, 2017, 03:39:12 PM
One step closer to decentralized crypto exchange. Hbn should jump on the train.
https://bitsonline.com/first-litecoin-bitcoin-atomic-swap/
https://bitsonline.com/first-litecoin-bitcoin-atomic-swap/
September 24, 2017, 10:33:33 AM
Well it's no worse then the 10 days it was, but at 8.8 you should start gaining weight. If you type getmininginfo in the rpc console the minimum still says 0?
It works smooth now, it's minting.
September 23, 2017, 09:07:02 AM
Bye the way; Do you have a twitter account Tranz???
No I don't have a twitter. But thanks!
I have a block that is 19 days old which has not staked. Other blocks, younger than this one have staked. Is this normal? Is there anything I need to do for this block?
Thanks again.
Luck and weight are the 2 main ingredients. If those that are that old are smaller in size they could take longer. I have some that are approaching 30 days 1 -2k in size.
You can never predict when a block will stake, you can only, with fairly good accuracy, predict when the half of a group of blocks will hit. Similar to half life of a decaying atom.
@Tranz
My new organized stakes have reached an aging time of over 8.8 days, but nevertheless the message is "not staking because you don't have mature coins", and "Current Wallet PoS Weight: 0". I hope staking begins after day 10, otherwise we had a real problem.
Well it's no worse then the 10 days it was, but at 8.8 you should start gaining weight. If you type getmininginfo in the rpc console the minimum still says 0?
September 23, 2017, 03:56:17 AM
So the answer was to slow the chain down. The slow down of the chain triggered a higher PoS difficulty and in turn a lower stake rate. This is what you are seeing now. The benefits are much lower inflation rate, very little wallet lag, much lower orphan rate, and a network that works much better.
Thank you for the explanation, Tranz. I understand a little better now.
I have a block that is 19 days old which has not staked. Other blocks, younger than this one have staked. Is this normal? Is there anything I need to do for this block?
Thanks again.
You know, if you get a stake reward, is highly based on fortune. The chance rises with the stake weight. or the mature time.
With less blocks created, for larger stakes it becomes advantageous to collect them into blocks of around 20k HBN.
@Tranz
My new organized stakes have reached an aging time of over 8.8 days, but nevertheless the message is "not staking because you don't have mature coins", and "Current Wallet PoS Weight: 0". I hope staking begins after day 10, otherwise we had a real problem.
September 22, 2017, 10:11:10 PM
A small announcement
HOBOBOT - THE TWITTER TIP BOT!!
I have installed a TipBot for HoboNickels on Twitter.
The whole community is invited to give their followers a bit of HoboNickels to spread the HoboNickels to the people.
How does it work:
1. Follow HoboNickels_HBN on Twitter
2. Make a Tweet: Hobobot address -> The Hobobot will return your HBN deposit address.
3. Send some HoboNickels to your wallet which the bot gives you
4. Send your followers a tip: Hobobot tip @USER
Example:
Hobobot tip @Tranz 100
This command would send a tip of 100HBN to the Twitter Account of @Tranz
Cool Hah??
Bye the way; Do you have a twitter account Tranz???
I want to create later a custom website specially for this bot.
Unfortunately I'm a bit short in time, but I try my best.
HoboNickels to the MOON !!
September 22, 2017, 04:55:38 PM
Thanks lightspeedy and hi Randall.
The original development of the coin did not have long term value and use in mind. It was meant to be one and done. Due to this things were major issues. Most notably starting with wallet lag and bad orphan rate. This was due to among many things 20 second block time. For a global network of wallets that were accepting blocks, relaying transactions and creating PoS blocks, it was not a long term feasible setting.
Also the PoW structured allowed for pools and users with high hash power to basically take over the chain and potentially cause other issues. To fix this I first made the first change to limit PoW by only allowing it to come after a PoS block, and eventually at block 6.0 million it will be turned off.
Then I made further enhancements to the wallet to allow for more efficient quicker staking. This has the unintended consequences of causing lager wallets the ability take over chain, because they could calculate stake so quickly. This only increased the issue of wallet lag and orphans and eventually caused a network split.
So the answer was to slow the chain down. The slow down of the chain triggered a higher PoS difficulty and in turn a lower stake rate. This is what you are seeing now. The benefits are much lower inflation rate, very little wallet lag, much lower orphan rate, and a network that works much better.
The original development of the coin did not have long term value and use in mind. It was meant to be one and done. Due to this things were major issues. Most notably starting with wallet lag and bad orphan rate. This was due to among many things 20 second block time. For a global network of wallets that were accepting blocks, relaying transactions and creating PoS blocks, it was not a long term feasible setting.
Also the PoW structured allowed for pools and users with high hash power to basically take over the chain and potentially cause other issues. To fix this I first made the first change to limit PoW by only allowing it to come after a PoS block, and eventually at block 6.0 million it will be turned off.
Then I made further enhancements to the wallet to allow for more efficient quicker staking. This has the unintended consequences of causing lager wallets the ability take over chain, because they could calculate stake so quickly. This only increased the issue of wallet lag and orphans and eventually caused a network split.
So the answer was to slow the chain down. The slow down of the chain triggered a higher PoS difficulty and in turn a lower stake rate. This is what you are seeing now. The benefits are much lower inflation rate, very little wallet lag, much lower orphan rate, and a network that works much better.
September 22, 2017, 01:02:01 PM
What Happened?
Newbie here.
Several years ago I mined HBN for a short while, and then turned to POS, which I have been doing ever since. I manged to build up to around 60K HBN coins. Prior to this change, my blocks (averaging 1,200 coins) staked in around 11 days and generated 30-35 coins per block.
Now, my blocks are taking much longer to stake, with one block already over 18 days. The coins generated by the stake have also dropped by at least 50%.
I'm not very knowledgeable about crypto-currencies, and I'm not clear on what changed and why it changed. Could someone please explain this in plain English?
Newbie here.
Several years ago I mined HBN for a short while, and then turned to POS, which I have been doing ever since. I manged to build up to around 60K HBN coins. Prior to this change, my blocks (averaging 1,200 coins) staked in around 11 days and generated 30-35 coins per block.
Now, my blocks are taking much longer to stake, with one block already over 18 days. The coins generated by the stake have also dropped by at least 50%.
I'm not very knowledgeable about crypto-currencies, and I'm not clear on what changed and why it changed. Could someone please explain this in plain English?
Welcome back Randall.
There were some challenges with the chain and Tranz (the dev) made some tweaks and forked to V.2.0.0 to get rid of the issues.
You just can read the posts to know what happened.
https://bitcointalk.org/index.php?topic=303749.4820
Quote
Should I be concerned? Is this normal behavior or is there something wrong with my wallet (on on version 2.0 by the way)?
Is a block size of 1200 coins too small? Should I combine my blocks to get them up to 5K or 10K?
I've spent a lot of time over the years working the POS stakes, which I hope was not for naught.
Thanks,
Randall
Keep calm and drink a beer.
The behavior is "normal" at the moment.
Just follow Updates here and listen to the dev.
September 21, 2017, 10:37:28 PM
what is the ideal block size for staking?
is it still 5000 HBN?
is it still 5000 HBN?
I think you can safety double it at this point and not worry about hitting the cap. Would hit it around day 30.
September 21, 2017, 09:47:22 PM
what is the ideal block size for staking?
is it still 5000 HBN?
is it still 5000 HBN?
September 21, 2017, 04:51:35 PM
I think those attacks are hashpools who still think we have full PoW - they calculate how rewarding mining is and switch
Might be possible. But I would still assume they are using wallet 2.0 and it would limit which blocks are even allowed to make it the network. But the odd thing was other wallets accepted it and relayed it. They should have just ignored it and banned that one bad block. 
September 21, 2017, 03:52:31 PM
I think those attacks are hashpools who still think we have full PoW - they calculate how rewarding mining is and switch
September 20, 2017, 07:38:13 PM
Socket errors aren't bad in and of themselves. They simply mean the connection was lost for some reason. Those reasons can be a bad internent connection between the peers, it can be that the peer you are connected too will not accept any more connections because they are at the max.
The reason I had brought it up is that, it can also be if a peer bans you for misbehaving. That was what I saw. I banned 3 or 4 clients, and I think 5 banned me as well. before I knew it i was down to 3 or 4. Now I am back to normal since the bans only last 24hrs. But for the most part, they are nothing to worry about.
The reason I had brought it up is that, it can also be if a peer bans you for misbehaving. That was what I saw. I banned 3 or 4 clients, and I think 5 banned me as well. before I knew it i was down to 3 or 4. Now I am back to normal since the bans only last 24hrs. But for the most part, they are nothing to worry about.
September 20, 2017, 01:05:49 PM
Good Job
2017-08-31 18:34:36 partner [2a01:4f8:202:7021::1806]:42221 using obsolete version 70007; disconnecting
What is this ? :
2017-08-31 18:31:06 socket recv error 10054
2017-08-31 18:33:48 socket recv error 10053
2017-08-31 18:34:36 partner [2a01:4f8:202:7021::1806]:42221 using obsolete version 70007; disconnecting
What is this ? :
2017-08-31 18:31:06 socket recv error 10054
2017-08-31 18:33:48 socket recv error 10053
Hmm i have the socket recv error on the old client .... what is the problem ?
Code:
2017-09-20 17:55:09 socket recv error 10054
2017-09-20 17:55:15 socket recv error 10054
2017-09-20 17:55:42 SetBestChain: new best=2233da1903d4933779ab height=5672511 trust=134536583948663 blocktrust=14506116091 date=09/20/17 17:55:10
2017-09-20 17:55:42 ProcessBlock: ACCEPTED
2017-09-20 17:56:56 SetBestChain: new best=b033df4fdbdee969bd4a height=5672512 trust=134551289535082 blocktrust=14705586419 date=09/20/17 17:56:37
2017-09-20 17:56:56 ProcessBlock: ACCEPTED
2017-09-20 17:57:00 Flushed 9403 addresses to peers.dat 31ms
2017-09-20 17:57:22 socket recv error 10054
2017-09-20 17:57:30 SetBestChain: new best=00000000b57276dd4136 height=5672513 trust=134551289537837 blocktrust=2755 date=09/20/17 17:57:02
2017-09-20 17:57:30 ProcessBlock: ACCEPTED
2017-09-20 17:58:13 SetBestChain: new best=70461a170d8918c48d18 height=5672514 trust=134566078351824 blocktrust=14788813987 date=09/20/17 17:57:40
2017-09-20 17:58:13 ProcessBlock: ACCEPTED
2017-09-20 17:58:39 SetBestChain: new best=c5e38c08602c725a1953 height=5672515 trust=134581002843313 blocktrust=14924491489 date=09/20/17 17:58:17
2017-09-20 17:58:39 ProcessBlock: ACCEPTED
2017-09-20 17:58:52 SetBestChain: new best=14ea79886bb1b16039b9 height=5672516 trust=134596121501051 blocktrust=15118657738 date=09/20/17 17:58:43
2017-09-20 17:58:52 ProcessBlock: ACCEPTED
2017-09-20 17:59:14 SetBestChain: new best=00000001086f860e45d8 height=5672517 trust=134596121503869 blocktrust=2818 date=09/20/17 17:58:53
2017-09-20 17:59:14 ProcessBlock: ACCEPTED
2017-09-20 17:59:34 socket recv error 10054
2017-09-20 17:59:40 socket recv error 10054
2017-09-20 18:00:33 SetBestChain: new best=e787534a9c882d9eac7e height=5672518 trust=134611461520111 blocktrust=15340016242 date=09/20/17 17:59:44
2017-09-20 18:00:33 ProcessBlock: ACCEPTED
2017-09-20 18:01:42 ResendWalletTransactions()
2017-09-20 18:01:46 SetBestChain: new best=f19708d23b82d05d4bca height=5672519 trust=134626946780693 blocktrust=15485260582 date=09/20/17 18:01:40
2017-09-20 18:01:46 ProcessBlock: ACCEPTED
2017-09-20 18:01:52 socket recv error 10054
2017-09-20 18:02:23 ERROR: AcceptBlock() : rejected by synchronized checkpoint
2017-09-20 18:02:23 ERROR: ProcessBlock() : AcceptBlock FAILED
2017-09-20 18:04:04 socket recv error 10054
2017-09-20 17:55:15 socket recv error 10054
2017-09-20 17:55:42 SetBestChain: new best=2233da1903d4933779ab height=5672511 trust=134536583948663 blocktrust=14506116091 date=09/20/17 17:55:10
2017-09-20 17:55:42 ProcessBlock: ACCEPTED
2017-09-20 17:56:56 SetBestChain: new best=b033df4fdbdee969bd4a height=5672512 trust=134551289535082 blocktrust=14705586419 date=09/20/17 17:56:37
2017-09-20 17:56:56 ProcessBlock: ACCEPTED
2017-09-20 17:57:00 Flushed 9403 addresses to peers.dat 31ms
2017-09-20 17:57:22 socket recv error 10054
2017-09-20 17:57:30 SetBestChain: new best=00000000b57276dd4136 height=5672513 trust=134551289537837 blocktrust=2755 date=09/20/17 17:57:02
2017-09-20 17:57:30 ProcessBlock: ACCEPTED
2017-09-20 17:58:13 SetBestChain: new best=70461a170d8918c48d18 height=5672514 trust=134566078351824 blocktrust=14788813987 date=09/20/17 17:57:40
2017-09-20 17:58:13 ProcessBlock: ACCEPTED
2017-09-20 17:58:39 SetBestChain: new best=c5e38c08602c725a1953 height=5672515 trust=134581002843313 blocktrust=14924491489 date=09/20/17 17:58:17
2017-09-20 17:58:39 ProcessBlock: ACCEPTED
2017-09-20 17:58:52 SetBestChain: new best=14ea79886bb1b16039b9 height=5672516 trust=134596121501051 blocktrust=15118657738 date=09/20/17 17:58:43
2017-09-20 17:58:52 ProcessBlock: ACCEPTED
2017-09-20 17:59:14 SetBestChain: new best=00000001086f860e45d8 height=5672517 trust=134596121503869 blocktrust=2818 date=09/20/17 17:58:53
2017-09-20 17:59:14 ProcessBlock: ACCEPTED
2017-09-20 17:59:34 socket recv error 10054
2017-09-20 17:59:40 socket recv error 10054
2017-09-20 18:00:33 SetBestChain: new best=e787534a9c882d9eac7e height=5672518 trust=134611461520111 blocktrust=15340016242 date=09/20/17 17:59:44
2017-09-20 18:00:33 ProcessBlock: ACCEPTED
2017-09-20 18:01:42 ResendWalletTransactions()
2017-09-20 18:01:46 SetBestChain: new best=f19708d23b82d05d4bca height=5672519 trust=134626946780693 blocktrust=15485260582 date=09/20/17 18:01:40
2017-09-20 18:01:46 ProcessBlock: ACCEPTED
2017-09-20 18:01:52 socket recv error 10054
2017-09-20 18:02:23 ERROR: AcceptBlock() : rejected by synchronized checkpoint
2017-09-20 18:02:23 ERROR: ProcessBlock() : AcceptBlock FAILED
2017-09-20 18:04:04 socket recv error 10054
September 20, 2017, 12:19:12 PM
Anyone experiencing any turbulence recently?
A few of my clients have received a large number of socket 10054 errors, followed by Misbehaving peers for too little proof of work?
A few of my clients have received a large number of socket 10054 errors, followed by Misbehaving peers for too little proof of work?
Not at all!
It works like a charm!
Got the last 24hrs only 3 Orphans of 51 Stakes
September 19, 2017, 06:06:37 PM
Anyone experiencing any turbulence recently?
A few of my clients have received a large number of socket 10054 errors, followed by Misbehaving peers for too little proof of work?
A few of my clients have received a large number of socket 10054 errors, followed by Misbehaving peers for too little proof of work?
September 19, 2017, 08:04:41 AM
yeah I was just starring at it for about 20 seconds when I first noticed thinking it wa going to pop but nothing .. for days now
not restarted since the fork, no. I was thinking about a restart and watch and you all made me think twice.
I only have the info task manager gives so .. go figure ...
ask the hubby to restart it
hehehe .. you're a funny fellow
Actually thanks for the Kung Fury comment ... What a find!
September 19, 2017, 07:49:33 AM
Also you say 115mb ram? I have not observed this at all ! I am still at 2 gb on all my wallets. Now granted all my wallets go back to the first few months, but 115mb?!
beats me too, mine eats ~2.1GB no matter old or new
OK .. that would be weird then
I have been looking this morning at it on and off
An observed low of 60Mb and a current high of 125.9MB
Caps 930 MB
Clam 680 MB
HYP 546 MB
and others as expected.
scared to turn it off now .. praps I should just start a staking service while my luck is in
sounds to me like real fp minus 2GB
did you ever watch how it grows (in task manager) from the wallet start until fully functional ?
yeah I was just starring at it for about 20 seconds when I first noticed thinking it wa going to pop but nothing .. for days now
not restarted since the fork, no. I was thinking about a restart and watch and you all made me think twice.
I only have the info task manager gives so .. go figure ...
September 19, 2017, 07:24:40 AM
Also you say 115mb ram? I have not observed this at all ! I am still at 2 gb on all my wallets. Now granted all my wallets go back to the first few months, but 115mb?!
beats me too, mine eats ~2.1GB no matter old or new
OK .. that would be weird then
I have been looking this morning at it on and off
An observed low of 60Mb and a current high of 125.9MB
Caps 930 MB
Clam 680 MB
HYP 546 MB
and others as expected.
scared to turn it off now .. praps I should just start a staking service while my luck is in
Jump to: