Repository navigation
Conversation
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.
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
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. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.