Skip to content

docs: propose EvoNode Platform reward withdrawals - #193

Draft
shumkov wants to merge 1 commit into
masterfrom
shumkov/evonode-platform-payouts
Draft

shumkov wants to merge 1 commit into
masterfrom
shumkov/evonode-platform-payouts

Conversation

@shumkov

@shumkov shumkov commented Oct 6, 2026

Copy link
Copy Markdown

Core v24 allows EvoNodes to register multiple owner payout scripts, but Platform's single-recipient withdrawal model cannot safely represent those recipients or arbitrary Core P2SH destinations. This draft DIP proposes owner-authorized withdrawals to the exact registered scripts, with a signed payout-policy commitment and one Asset Unlock transaction whose outputs and fee are fixed at acceptance.

Rewards continue accumulating on the existing identity. The current policy applies to all unwithdrawn funds, including earlier rewards and incoming credits; this does not create independent beneficiary claims. Unlike automatic Core coinbase payouts, the owner must initiate Platform withdrawals. The draft also specifies rounding, fees, policy changes, queue compatibility, activation ordering, and the recovery boundary for EvoNodes removed before activation.

The proposal complements the Core payout specification in #184. It uses an alias filename and leaves DIP numbering to the editors. Protocol/wire assignments, storage/query encodings, fee floors, and network migration evidence remain open before activation. No Platform implementation is included.

Validation: three independent design reviews covering scope, authorization, and migration/accounting; all identified pre-review corrections incorporated. Both changed Markdown files pass the repository's markdownlint configuration, and the numeric split examples were checked. Runtime tests do not apply to this documentation-only change; the DIP's test cases are implementation requirements, not executed results.

Define policy-bound owner withdrawals to Core payout scripts, with explicit balance semantics, migration, and queue compatibility. Documentation only; no runtime behavior change or runtime tests.
@coderabbitai

coderabbitai Bot commented Oct 6, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant