Extension for NFT standart: destroyable NFTs

text/0000-nft-destroyable.md

@@ -0,0 +1,69 @@
+- **TEP**: [0](https://github.com/ton-blockchain/TEPs/pull/0)
+- **title**: Destroyable NFT Standart
+- **status**: Draft
+- **type**: Contract Interface
+- **authors**: [Daniil Markov](https://github.com/arkadiystena)
+- **created**: 10.12.2023
+- **replaces**: -
+- **replaced by**: -
+
+# Summary
+
+Extension for [NFT Standard](https://github.com/ton-blockchain/TEPs/blob/master/text/0062-nft-standard.md).
+
+A standard interface for non-fungible tokens which allow to destroy them similar to [SBTs] (https://github.com/ton-blockchain/TEPs/blob/master/text/0085-sbt-standard.md#3-destroy). Destroyed NFTs looks like they were never minted, and there is no possibility to re-mint them
+
+# Motivation
+
+Sometimes people want to get rid of an NFT in their wallet, but don't want to sell or gift it to anyone (for example, if the creator of NFT collection accidentally minted an extra NFT), and the only thing they can do is to send the NFT to a zero address. However, this solution has two problems:
+* Sending an NFT to a zero address is a loss for the user (a gas fee must be paid and the balance of the NFT smart contract cannot be withdrawn).
+* Indexers will continue to display this NFT as if it belongs to some user, which means the displayed supply of the NFT collection could be reduced, even though no actions can be performed with this NFT anymore.
+
+# Specification
+
+Destroyable NFT implements [NFT Standard](https://github.com/ton-blockchain/TEPs/blob/master/text/0062-nft-standard.md) but with additional destroy operation:
+
+TL-B schema of an internal message:
+```
+destroy#1f04537a query_id:uint64 = InternalMsgBody;
+```
+`query_id` -  arbitrary request number.
+
+Should be rejected if:
+* Sender address is not an owner's address.
+
+Otherwise should do:
+ * Should remove owner's address and nft content from contract storage (make NFT uninitialized like it wasn't minted).
+ * Set collection address to null so NFT can't be minted again
+ * Send message to sender with schema `excesses#d53276db query_id:uint64 = InternalMsgBody;` that will pass contract's balance amount.
+
+### Implementation example
+https://github.com/ArkadiyStena/nft-destroyable/blob/master/nft-destroyable.fc
+
+# Guide
+Mint can be done using basic NFT collection where nft-destroyable is an item. All operations are same with simple NFT besides destroy message.
+
+# Drawbacks
+
+After burning NFT it is impossible to get former NFT content. 
+
+# Rationale and alternatives
+
+- Why is this design the best in the space of possible designs?
+This design has all possible functions of burning NFT (NFT transfers its balance to the owner, NFT can't be reminted, NFT looks like it was never minted) 
+- What other designs have been considered and what is the rationale for not choosing them?
+Was considered displaying sended to zero address NFTs as burned, but this solution has problems described in the "Motivation" section
+- What is the impact of not doing this?
+Ignoring this or any similar standart for burning NFTs will affect users who wants to remove NFTs from their wallets and also creators of NFT collections who can accidentally mint unwanted NFT.
+
+# Prior art
+
+-
+
+# Unresolved questions
+
+-
+
+# Future possibilities
+
+Standard looks finalized.