Skip to content

docs(dip-26): align collateral payout reuse rule #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
thepastaclaw wants to merge 1 commit into
base: codex/masternode-reward-shares
Choose a base branch
from
Open

docs(dip-26): align collateral payout reuse rule #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions dip-0026.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,8 +250,8 @@ conditions are true:
7. The same payout script appears more than once in the payout list.
8. A P2PKH payout destination equals the owner key ID.
9. A P2PKH payout destination equals the voting key ID.
10. A P2PKH payout destination equals the collateral key ID when the collateral
output destination can be extracted as a P2PKH destination.
10. A payout destination equals the collateral output destination when both
destinations can be extracted.

The 100-basis-point minimum is a consensus anti-dust bound. It prevents
intentionally tiny micro-owner entries from creating nuisance coinbase outputs.
Expand Down Expand Up @@ -346,8 +346,9 @@ Implementations should include tests for the following cases:
6. A payout list whose rewards sum to 9999 or 10001 is invalid.
7. A payout list containing duplicate scripts is invalid.
8. A payout list containing a non-P2PKH and non-P2SH script is invalid.
9. A payout script that reuses the owner, voting, or collateral key is invalid
where the corresponding key comparison is possible.
9. A payout script that reuses the owner or voting key, or whose destination
equals the collateral output destination, is invalid where the corresponding
comparison is possible.
10. A ProUpRegTx can replace the payout list without reviving a PoSe-banned
masternode.
11. A masternode with an operator payout first subtracts the operator reward and
Expand All @@ -366,10 +367,10 @@ the registrar owner's authority to update masternode registration metadata. A
share arrangement that requires immutable payout rights must use additional
contractual, wallet, or protocol mechanisms outside the scope of this DIP.

Payout scripts must not reuse owner, voting, or collateral keys for the same
Payout scripts must not reuse owner or voting keys or the collateral destination for the same
reason that DIP-0003 restricts current payout key reuse: payout keys may be used
in less secure wallet environments, while owner, voting, and collateral keys
control higher-value masternode functions.
in less secure wallet environments, while owner and voting keys and the
collateral itself control higher-value masternode functions and funds.

The payout count and minimum share limits reduce the risk of using masternode
registrations to create large numbers of tiny recurring coinbase outputs.
Expand Down
Loading