Multi-party payouts (DIP-0026) made the reward side of a shared masternode non-custodial, but the collateral still has to be a single output controlled by one party, so pooled masternodes remain custodial today. I have drafted a design for closing that gap, a covenant opcode (an output-template commitment, the CheckTemplateVerify idea from Bitcoin) plus an application that pools the collateral into one output that can only ever be refunded to its funders, with rewards split through DIP-0026.
These are early drafts, offered for directional feedback rather than as a formal submission. They have been through several rounds of independent adversarial review, which caught real issues that are now fixed, and the principal-safety side has held up. There is no reference implementation yet, and a few items are left open in the text.
Drafts: https://github.com/hilawe/dash-multiparty-collateral-dips
I would value guidance on two things before taking this further:
- Is a CheckTemplateVerify-style covenant opcode a sound foundation, given Dash is ECDSA-only with no SegWit, or is there a direction you would steer this toward instead?
- For the first version, is fixed-term and fixed-membership the right place to start, with dynamic membership and recursion deferred?
cc @PastaPastaPasta and @UdjinM6, I would value your directional take if either of you has a moment.
Thanks for any time you can give it.
Multi-party payouts (DIP-0026) made the reward side of a shared masternode non-custodial, but the collateral still has to be a single output controlled by one party, so pooled masternodes remain custodial today. I have drafted a design for closing that gap, a covenant opcode (an output-template commitment, the CheckTemplateVerify idea from Bitcoin) plus an application that pools the collateral into one output that can only ever be refunded to its funders, with rewards split through DIP-0026.
These are early drafts, offered for directional feedback rather than as a formal submission. They have been through several rounds of independent adversarial review, which caught real issues that are now fixed, and the principal-safety side has held up. There is no reference implementation yet, and a few items are left open in the text.
Drafts: https://github.com/hilawe/dash-multiparty-collateral-dips
I would value guidance on two things before taking this further:
cc @PastaPastaPasta and @UdjinM6, I would value your directional take if either of you has a moment.
Thanks for any time you can give it.