SIP-040: SIP for improved post-conditions #257
+186
−0
Conversation
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
This was referenced Feb 7, 2026
5 tasks
wileyj
reviewed
Feb 11, 2026
Contributor
|
@brice-stacks can you move the files into the expected structure? |
wileyj
changed the title
Co-authored-by: wileyj <2847772+wileyj@users.noreply.github.com>
wileyj
reviewed
Feb 11, 2026
Co-authored-by: wileyj <2847772+wileyj@users.noreply.github.com>
wileyj
reviewed
Feb 11, 2026
|
|
||
| - https://forum.stacks.org/t/improved-post-conditions/18661 | ||
|
|
||
| # Abstract |
Contributor
There was a problem hiding this comment.
Is it worth mentioning that this sip is a rider for SIP-039, and if that sip is approved this one follows the same activation?
or is this SIP intended to activate separately?
wileyj
reviewed
Feb 11, 2026
Comment on lines
+63
to
+69
| reverting to signing `Allow` mode transactions, just to make it work. This is a | ||
| very bad habit to teach our users, and we can do better. What the user really | ||
| cares about is something like, "When I call contract X, at most `m` STX and `n` | ||
| USDCx may be moved from my wallet." They don't care if contract X sends sBTC to | ||
| contract Y, which sends USDCx to contract Z, etc. `Originator` mode allows the | ||
| user to specify only the restrictions on their own assets, allowing any | ||
| movements of assets amongst other principals. |
Contributor
There was a problem hiding this comment.
Suggested change
| reverting to signing `Allow` mode transactions, just to make it work. This is a | |
| very bad habit to teach our users, and we can do better. What the user really | |
| cares about is something like, "When I call contract X, at most `m` STX and `n` | |
| USDCx may be moved from my wallet." They don't care if contract X sends sBTC to | |
| contract Y, which sends USDCx to contract Z, etc. `Originator` mode allows the | |
| user to specify only the restrictions on their own assets, allowing any | |
| movements of assets amongst other principals. | |
| reverting to signing `Allow` mode transactions, just to make it work. What users typically | |
| prefer is something like, "When I call contract X, at most `m` STX and `n` | |
| USDCx may be moved from my wallet.", and less so if contract X sends sBTC to | |
| contract Y, which sends USDCx to contract Z, etc. `Originator` mode allows the | |
| user to specify only the restrictions on their own assets, allowing any | |
| movements of assets amongst other principals. |
I hope i kept the intent in this section, but i felt it was important to not ascribe emotion to what users may or may not want.
wileyj
reviewed
Feb 11, 2026
| The transaction encoding reserves 1-byte for the non-fungible condition code. | ||
| `MAY SEND` adds a new acceptable value for this byte, `0x12`. | ||
|
|
||
| ## Updates to the SIP-005 Specification |
Contributor
There was a problem hiding this comment.
hmmm - i wonder if we need a way to differentiate when a SIP replaces an older one -as well as- updates an existing spec. 🤔
wileyj
reviewed
Feb 11, 2026
Comment on lines
+163
to
+164
| - This SIP will activate in epoch 3.4 together with | ||
| [SIP-clarity5](../sip-clarity5/sip-clarity5.md) |
Contributor
There was a problem hiding this comment.
Please update with SIP numbers (039).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This SIP proposes two new post-condition improvements,
Originatormode, and aMAY SENDcondition for NFTs.