Skip to content
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

Update sip-009-nft-standard.md #1

Closed
wants to merge 2 commits into from
Closed

Conversation

muneebm
Copy link

@muneebm muneebm commented Mar 16, 2021

@friedger First of all, thank you very much for taking the initiative (as always) for creating this standard. I have made a few changes to make it consistent with SIP-010 and rearranged the content a little bit. Please see if the changes can be merged.

 Rearranged the content to be consistent with SIP-010
| function | error | description |
|----------|-------|-------------|
|`transfer`|`{kind: "nft-transfer-failed", code: from-nft-transfer}`| Error if the call failed due to the underlying asset transfer. The code `from-nft-transfer` is the error code from the native asset transfer function|
In addition to built-in methods for non-fungible token contracts, the Stacks blockchain includes a feature known as Post Conditions. By defining post conditions, users can create transactions that include pre-defined guarantees about what might happen in that contract.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be part of the standard

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was trying to accommodate this implementation rule you listed: "Contracts must use a least one NFT asset. A post-condition with deny mode and without any NFT condition about a changed owner must fail for transfer function calls." Isn't it not a post condition? should I rephrase it or remove it?

@friedger
Copy link
Owner

@muneebm Thank you for the contribution! The changes has been added. Due to conflicts in a new commit.

Would you like to add your email address in the author section as a PR

@friedger friedger closed this Mar 17, 2021
friedger pushed a commit that referenced this pull request Jan 20, 2022
Add specifics for bitcoin vote op, proposed changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants