TGViewer
TON Contests TON Contests @toncontests · 129K subscribers
Post #148 36.7K

Forwarded from TON Tech

TonTech NFT Royalty standard contest

Hey everyone! We're excited to reveal the results of the NFT Royalty Standard contest. We received four submissions, but unfortunately, none of them met our expectations in terms of proposal quality. Here's a detailed review of each project:



1. hitaspdotnet's solution:

    - The solution lacks a guarantee on the size of royalties paid.
    - Its architecture opens up possibilities for scam use cases.
    - Involves too many transactions (4) for a single transfer.
    - Does not align with the current NFT standard and violates the transfer operation.
    - Allows the NFT to be put on sale to multiple contracts due to the ability for multiple users to transfer it.

2. Roman22022000's submission:

    - Unfortunately, we were unable to comprehend the ideas presented by Roman.

3. Ton-Dynasty's solution:

    - Considered overcomplicated and lacking practicality in terms of royalty enforcement.

4. coalus's implementation:

    - Although the idea is interesting, the problem remains unsolved as normal transfers still exist in this implementation.



In our internal research at TonTech, we've explored potential solutions and believe that a public whitelist of code hashes could be effective in ensuring the safe transfer of NFTs. 

This whitelist, which can be stored on-chain as Merkle proofs in the global config for decentralized control, contains contracts which are proven to be safe to transfer NFT to, like wallets, NFT sale contracts, etc.

This could be achieved by adding the state initialization of the new_owner contract to the transfer message with a proof verifying that the contract code is indeed on the whitelist. This approach allows the NFT to:

- Check the code against a whitelist.
- Verify that the state initialization leads to the correct new_owner address.

However, it's crucial to acknowledge a major drawback: we cannot guarantee the security of the solution if the new_owner contract is an updatable contract. This is particularly problematic since the contract code could be updated to become something else. Given that the wallet w5 contract is likely to be updatable, this solution poses inherent challenges.

Despite not finding a satisfactory solution in the contest, we would like to express our gratitude to all participants for their time and effort. Recognizing their contributions, we have decided to reward each participant with 200 TON for their commitment and dedication. We understand that the contest may not have yielded the desired outcomes, but we value the creativity and tenacity shown by the participants.

Let's continue exploring innovative solutions to address these complexities and enhance the security and reliability of NFT royalty enforcement.
More from @toncontests
  1. Apr 21, 2026🏆 AppKit Motion Design Challenge: Winners $3000 prize pool, 42 submissions, 10 days, thre…
  2. Apr 17, 2026🏆 TON AI Agent Hackathon: Winners Two weeks. 160+ submissions. An incredible amount of ta…
  3. Apr 6, 2026🎬 AppKit Motion Challenge — $3,000 Prize Pool Create a short motion video for AppKit and…
  4. Mar 11, 2026💎 TON AI Agent Hackathon is here! $20,000. Two tracks. Two weeks. Track 1: Agent Infrastr…
  5. Oct 10, 2025TON x Ignyte Hackathon: Building the Web3 SuperApp Economy TON Foundation and Ignyte invit…
  6. Oct 9, 2025TON Demo Days are Back, and BIGGER than ever! 🚀 This fall, TON Demo Days are back with a…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →