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

Create NFT Project Guide #414

Merged
merged 10 commits into from
Oct 19, 2023
Merged

Create NFT Project Guide #414

merged 10 commits into from
Oct 19, 2023

Conversation

chasefleming
Copy link
Member

Addresses: #413

@vercel
Copy link

vercel bot commented Oct 18, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 18, 2023 11:54pm

Copy link
Contributor

@gregsantos gregsantos left a comment

Choose a reason for hiding this comment

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

few comments then looks good to gizzo

docs/guides/nft.md Outdated Show resolved Hide resolved
}
```

For security reasons, you might not want to expose all the functions of the Collection to everyone. Instead, you can create an [interface](https://developers.flow.com/cadence/language/interfaces) that exposes only the methods you want to make public. In Cadence, interfaces act as a blueprint for resources and structures, ensuring that certain methods or properties exist. By leveraging these interfaces, you establish clear boundaries and standardized interactions. In this case, you might want to expose only the `deposit` and `getIDs` methods. This interface can then be used to create capabilities, ensuring that only the allowed methods are accessible.
Copy link
Contributor

Choose a reason for hiding this comment

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

🔥


## Fitting the Flow NFT Standard

To ensure compatibility and interoperability within the Flow ecosystem, it's crucial that your NFT contract adheres to the [Flow NFT standard](https://github.com/onflow/flow-nft). This standard defines the events, functions, resources, and other elements that a contract should have. By following this standard, your NFTs will be compatible with various marketplaces, apps, and other services within the Flow ecosystem.
Copy link
Contributor

Choose a reason for hiding this comment

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

🙏🏼

docs/guides/nft.md Outdated Show resolved Hide resolved
docs/guides/nft.md Outdated Show resolved Hide resolved
docs/guides/nft.md Outdated Show resolved Hide resolved
docs/guides/nft.md Outdated Show resolved Hide resolved
docs/guides/nft.md Outdated Show resolved Hide resolved
chasefleming and others added 6 commits October 18, 2023 16:44
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
@chasefleming
Copy link
Member Author

@gregsantos back to you

@chasefleming chasefleming merged commit 2bdda56 into main Oct 19, 2023
2 checks passed
@chasefleming chasefleming deleted the chasefleming/nft-guide branch October 19, 2023 17:25
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.

2 participants