Announcing DIP 31 - Platform Proof of Service

[thephez]

We're pleased to announce the release of DIP 31! To ensure that evonodes provide service on Dash Platform and that non-functioning evonodes do not participate in the Platform validator set, Platform needs a way to exclude faulty evonodes from future Platform validator sets / quorums. Since these nodes are not properly providing service, they should be proof-of-service (PoSe) banned. This DIP outlines a method for Platform to securely notify Core that an evonode should be banned.

You can read all the details about DIP 31 on GitHub. Thanks to the authors that assisted in creating this DIP, and special thanks to everyone who contributed to writing and reviewing it.

 

[vazaki3]

And what about the BUG of the POSE_BANNED masternodes, whose votes are still calculated in the voting results of the Dash Budget?

If you dont deal with that problem in your DIP31, by banning more masternodes you will create more inaccurate voting results ...

...and of course, as always, @qwizzie agrees with you. Whatever shit appears, @qwizzie is underneath. The bee goes to honey, the fly goes to shit.

 

[GrandMasterDash]

I have nothing against improving PoSe but I don't understand what is stopping malicious Platform nodes from compiling and running Core without the tests. Okay, needs collision but not exactly impossible.

 

[thephez]

I have nothing against improving PoSe but I don't understand what is stopping malicious Platform nodes from compiling and running Core without the tests. Okay, needs collision but not exactly impossible.

I can't speak for the Core/Platform devs, but my understanding is that this is a first step rather than a comprehensive solution. I'd expect to see the design improve over time - similar to the expansion of the PoSe system for regular masternodes has over the years. As I recall, prior to DKG / DIP-6, someone with sufficient motivation could completely fake PoSe participation and never be banned.