That's not my understanding of it at all. It's a leak, not a slash. Go offline briefly & you get a small penalty proportional to the time.
Agreed on this being unproductive
for the last time, PoW miners have the option of going offline to save cost when price drops. PoS validators don’t.
-
-
and the fact that you think this kind of thing is infeasible... well I don’t know what to say to that...
-
What's infeasible is to keep a staker offline long enough to come anywhere near costing his full stake. Cost to attacker >> cost to staker.
-
Again, applies for PoW too. DDOSing miners is doable (more doable, since speed matters much more under PoW). But not a major system risk.
-
And the argument against the inactivity leak is contingent on the slashed stake being burned or non-returnable. I haven’t seen a definitive decision made that that will be the case. I have seen proposals for escrow and returning after return to duty.
-
If you can afford to DDoS someone indefinitely such that they are bled dry and “give up” on retrieving slashed stake or earning it back, then it’s likely the staker didn’t understand the risks to begin with. Standard risk assessment/acceptance process here.
End of conversation
New conversation -
-
-
True, harder for PoS to go offline. Point is that this DDOS risk is bogus. Connectivity is v cheap, cost of losing it low & only per-minute.
-
Is there not a mechanism / process which the staking node can opt out of inclusion in the validator set and be offline without the inactivity leak being applied. Pretty sure I saw that in the documentation.
-
Just kidding it was actually your own discussion of validator states on gitter. That makes sense to me, especially for instances where maintenance may require the node to be offline, or planned lapses in ability to fulfill duties.
-
That was just from poking at the draft FFG code, https://github.com/ethereum/casper/blob/master/casper/contracts/simple_casper.v.py …, whose comments (but not code) refer to logging back in
-
Hmm that would definitely be worth pursuing, though. A state equal to not logged in or in the validator set, but not slashed for inactivity.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
