-
Notifications
You must be signed in to change notification settings - Fork 54
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.
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
TIP-52: Multi Address #152
base: main
Are you sure you want to change the base?
Conversation
TIP-47: Storage Deposit
Remove TIP-47
GitHub and the Wiki both auto-generate a ToC, so it's unnecessary to maintain it.
Co-authored-by: Thibault Martinez <[email protected]>
Unlocks other than _Empty Unlocks_, which do not add to this sum. | ||
- `Cumulative Unlocked Weight >= Threshold`. | ||
|
||
### Empty Unlock |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be a syntactic rule that it can't be used outside of a MultiUnlock or are we fine waiting semantic and see that address/unlock is not a good match?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The schemas tell you where the Empty Unlock is allowed - only in Multi Unlocks.
It's somewhat similar for implicit account creation addresses. They are also not allowed in Address Unlock Conditions within NFT Outputs, but are allowed in Basic Outputs. Neither are they allowed in Expiration Unlock Conditions. Those rules are not defined explicitly (but can be derived from TIP-42 when being creative), but really the rule is encoded in the schema of the Expiration UC.
Since we already have the schemas and they are much easier to maintain in the TIPs I would like to avoid duplicating those rules in text were it cannot be automatically updated.
Rendered Version
Note that: