chore: improve the NFT comparison article#954
Draft
aigerimu wants to merge 6 commits into
Draft
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Contributor
|
Thanks for the updates across the docs page ( |
skywardboundd
suggested changes
Oct 24, 2025
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
skywardboundd
suggested changes
Oct 28, 2025
| | ---------------------------- | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | | ||
| | Deployment and minting flow | Creator mints an item. | Any user with a valid proof can deploy an item. | | ||
| | Who pays for item deployment | Creators pay in most cases. | Audience pays. | | ||
| | Eligibility or allowlist | Creator controls custom off-chain or on-chain logic. | On-chain Merkle allowlist; users verify proofs using root from [Merkle root](/foundations/proofs/overview). | |
Contributor
There was a problem hiding this comment.
"users verify proofs using root from", proof is not only from root( it from backend ), may be we can just delete sentence about root.
| Royalty defines the percentage of NFT sales paid to the collection creator. It is set at the collection level and available using the `get_royalty_params`. For full specification, refer to [TEP‑66](https://github.com/ton-blockchain/TEPs/blob/1e5b2c4c8290d88d6bc3ddc4729812e3ac232c00/text/0066-nft-royalty-standard.md). | ||
|
|
||
| Marketplaces can rely on this model and pay royalties to the collection creator regardless of how the collection was deployed. | ||
| Any collection, including cNFT, can implement royalties. Marketplaces automatically pay royalties to the creator, regardless of the collection type. |
Contributor
There was a problem hiding this comment.
"Marketplaces automatically pay royalties"
Not really, they can pay, but can not to pay
| - When to use: one-off assets, experimental pieces, or cases where collection-level coordination is unnecessary | ||
| - Metadata: stored entirely on the item | ||
| - Discoverability: no collection index; external indexers or explicit links are required to surface the item | ||
| - Trade-offs: simpler setup but fewer shared features, including no collection-wide royalties or configuration, no batch queries by index. |
Contributor
There was a problem hiding this comment.
may be just "no index", it seems more simpler
novusnota
changed the title
novusnota
changed the title
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
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.
fix #935