A way to resolve activenode penalty issue

[John222]

Hi guys. As you all know. When the network does have an issue and activenodes goes down because of invalid blocks and misses more than 50%. The activenode gets a penatly. First it's just 1 day then 2 days, 4 days and as last 8 days. Can you implement a feature to bring down that penalty. Let's say we have a penalty of 2 days on one of your activenodes. Then you to pay, lets's say 5 llc to bring it down to 1 day. If the activenode does have 4 days of penalty then you have to pay 10 llc to bring it down to 1 day again and if you have a penalty of 8 days. then you have to pay 20 llc to bring it down to 1 day.

Here the list to bring penalty down to one day:

2 days penalty = 5 llc to bring it down to 1 day penalty
4 days penalty = 10 llc to bring it down to 1 day penalty
8 days penalty = 20 llc to bring it down to 1 day penalty

This is just a suggestion how it can be resolved. I think this should be implemented as a operation in the blockchain similar to the "Activenode create" operation.

[ninetor]

Hi. Right now we got vesting balance bug, so some nodes get out of sync, that why you are getting penalties.
In normal state we use penalty for activenodes, which doesnt work well for our network. So if node skipping 50% of blocks it must be kicked from network.

For now activenode gets ~60llc each day, penalty of 5llc this is almost nothing (you will get back this amount in few minutes).

You can "reset" your activenode by putting your balance lower than 500LLC, so node will delete your activenode object. And you can create under your account a new activenode object without penalty.
But you must be careful with this operation - vesting balance is connected with activenode object, so if you delete activenode obj, vesting will be locked.
With new activenode object you will get a new one vesting balance for it.

There is no need in having "reset_activenode_operation" because in normal state it will harm our network in future with unstable nodes.

[John222]

Hello @ninetor. I understand your point. Do you have a clue when this is fixed? Do you also know, if everyone of the activenode holders does have to download a new witness_node binary then?

[ninetor]

We are testing new vesting balance policy, v1.0.2 will be released next week.

[ninetor]

It's not finished yet. Release post with pre-release label, it works unstable on current network. It for our testers for now.