HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive

[cryptmebro]

Are you running version 1.5.1? Your potential stake amount seems high. I have a 4110 block with a potential stake of 113. I believe the max is 250

https://github.com/Tranz5/HoboNickels/releases/tag/1.5.1.0

[tokyoghetto]

would you guys be interested in a marketmaker?

Thanks for the first wave, you are great at it, your journal was one of the reasons that reassured me to stay in HBN, time for a second wave?

Possibly. I am considering something for hobonickels to breath life back into the project.

Long time, tokyoghetto!

Take care about CAP too?

How is CAP looking these days?

[kneim]

i m reading tokyoghetto hbn journal   dam i did not know that hbn get over 30000sat on the past  
what happen , it s not the dead of cryptsy what put the price so low because it was already under 2000sat

now this coins is definitely unevaluated, there are worse coins with 4 digit satochi value

does i have a bug in my wallet ?
because i notice i have a block of 3719 hbn that won't stake  age of 64days old  potential stake 649 (but max is 250 i think)

when i sow that around 40days i ask my self, should i split it, but if i do i lose the age, it s gonna stake soon   but it s don't lol

check your time settings

[carlo_0000]

yes running 1.5.1

i check time and date it s ok too

[kneim]

yes running 1.5.1

i check time and date it s ok too

Take a look into the debug.log file then. If you see something suspicious, especially at the time the staking fails, show it here.

[carlo_0000]

is there a code or something to upload the full log here ?

 

[cryptmebro]

is there a code or something to upload the full log here ?

 

Copy paste or if it's too long, dropbox link (or something similar)

[carlo_0000]

ok i upload it on first host i found
http://www.filedropper.com/debug

[kneim]

ok i upload it on first host i found
http://www.filedropper.com/debug

Carlo, your link identifies nothing but "debug". Better you choose one failed stake mining, select the context menu "show transaction details", note the date/time this occured, and cut the log entries around this date/time and copy and paste it here.

[kneim]

I found two log entries "coinstake timestamp violation". Are you sure, your time ist correct? Do you know the difference between local time and UTC (universal time zone)? I cannot help you, if you are using MS Windows.

Please give a hint about one concrete appearence, as a time stamp. I cannot go through the full log.

[carlo_0000]

I found two log entries "coinstake timestamp violation". Are you sure, your time ist correct? Do you know the difference between local time and UTC (universal time zone)? I cannot help you, if you are using MS Windows.

Please give a hint about one concrete appearence, as a time stamp. I cannot go through the full log.

yes my time is correct , runing windows 7, all my computer have same time syns with time.windows.com

i have 2 hbn wallet but not on the same computer

maybe  if i send all the coins what stake to an other wallet, to start a new one, i guess the problem gonna be solved ?

[carlo_0000]

i don't think 2 wallets on the same ip  get conflict, they both behind nat , they automatically already have 2 different port
otherwise the could not sync right

i have some other wallet in double too  dmd for example  

but most of the time they not on the same external ip, sometimes they on the same because they have slower speed so i change my getway when need to downlaod


the 2nd wallet look better
i gonna start a new wallet, gonna remember to check my ip's before staking  than

[carlo_0000]

i don't think 2 wallets on the same ip  get conflict, they both behind nat , they automatically already have 2 different port
otherwise the could not sync right

i have some other wallet in double too  dmd for example  

but most of the time they not on the same external ip, sometimes they on the same because they have slower speed so i change my getway when need to downlaod


the 2nd wallet look better
i gonna start a new wallet, gonna remember to check my ip's before staking  than

i see "misbehaving..." shit in log with local net ip, it's not good by all means
just for testing close the second wallet and let only one in question to run for awhile, what will it be....

2016-04-07 15:34:33 connected to self at 192.168.137.7:65243, disconnecting
2016-04-07 15:34:33 Misbehaving: 192.168.137.7:7372 (0 -> 1)
2016-04-07 15:34:33 ProcessMessage(ping, 8 bytes) FAILED

it s actually trying to connect  to itself, it s not the ip of the other computer

so i think this could be ignored

[carlo_0000]

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

[kiklo]

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

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

[kiklo]

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

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

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.

[kneim]

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.

[carlo_0000]

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.

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

[kiklo]

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

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.  


 

[carlo_0000]

so each time you making new blocks ?

i let my run 24/24
i only make new block with the very small ones