-
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-20 Transaction Payload with TIP-18 Output Types #40
Conversation
New output types, unlock blocks and output feature blocks are introduced in RFC-0038 that modify the Transaction Payload structure and validation rules.
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 Address reuse
and Rationale and alternatives
sections still have information from the old RFC about W-OTS, which shouldn't be there anymore, since we removed that already with Chrysalis Part 2
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.
oooohhh man. What a rabbit hole I've fallen into now. I just wanted to look at NFT outputs again 😅
What a mess. I hope this review helps somehow.
Created lzpap#1 to add |
Update TIP-20: Add network ID to essence
- Bump Tx Payload type to 6 - Bump Tx Essence type to 1 - Add Tagged Data as supported payload type instead of Indexation
Minting and melting are restricted to the foundry, while burning is performed by the user without the need for the foundry to be update.
<td valign="top">Unlocks <code>anyOf</code></td> | ||
<td colspan="2"> | ||
<details> | ||
<summary>Signature Unlock</summary> |
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 table looks broken in my browser.
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.
Is it fixed now?
Co-authored-by: Thoralf-M <46689931+Thoralf-M@users.noreply.github.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Description
TIP-18 Introduces new output types, unlocks and output features that modify Transaction Payload structure and validation rules.
This PR adds these modification to the original Transaction Payload definition (#18) with the goal of replacing TIP-7.
View
Rendered Document