⚠️ WARNING: this proposal system is experimental now, the process is a subject to change.
The main goal of TON Enhancement Proposals is to provide a convenient and formal way to propose changes to TON Blockchain and standardize ways of interaction between different parts of ecosystem.
Proposal management is done using GitHub pull requests, the process is described formally in TEP-1.
- Discuss your proposal with community first, for example in TON Dev chat (en/ru).
- Read TEP-1 to understand proposal management process.
- Fork this repo and copy
./0000-template.md
to./text/0000-my-new-standard.md
where "my-new-standard" is a short title of your TEP. - Fill all sections and answer questions stated in template. If you need to include images, upload them to
./assets/0000-my-new-standard/
folder. - Submit a pull request.
TEP | Title | Type | Created |
---|---|---|---|
1 | TEP Lifecycle | Meta | 11.06.2022 |
2 | TON Addresses | Core | 07.09.2019 |
62 | NFT Standard | Contract Interface | 01.02.2022 |
64 | Token Data Standard | Contract Interface | 03.02.2022 |
66 | NFTRoyalty Standard Extension | Contract Interface | 12.02.2022 |
74 | Fungible tokens (Jettons) standard | Contract Interface | 12.03.2022 |
81 | TON DNS Standard | Contract Interface | 25.06.2022 |
85 | SBT Contract | Contract Interface | 09.08.2022 |
89 | Discoverable Jettons Wallets | Contract Interface | 08.09.2022 |
115 | TON Connect | Core | 20.10.2022 |
Since standard truly become a Standard not when it gets merged into this repository, but when multiple parties accept it and use to interact with each other, below we list proposals to which developers may refer in documentation and so on. In particular "Status" below has the following sense:
- "Proposed" - this standard hasn't implementation or implementation is used only by authors
- "Partially Deployed" - this standard is used by pair of actors (for instance one dApp and one wallet, or similar), but not by interconnected set of actors
- "Deployed" - this standard is used by multiple actors (and generally should be on the way of merging)
TEP | Title | Type | Created | Status |
---|---|---|---|---|
91 | Contract Source Registry | Infrastructure | 09.09.2022 | ✅Deployed✅ |
92 | Wallet Registry | Infrastructure | 11.09.2022 | Proposed |
96 | Dicts/Arrays in Metadata | Contract Interface | 21.09.2022 | Proposed |
104 | Data Signatures | Contract Interface | 13.12.2022 | Proposed |
121 | Lockable Jetton Wallet | Contract Interface | 13.04.2023 | Proposed |
122 | Onchain reveal mechanic | Contract Interface | 31.10.2022 | ✅Deployed✅ |
123 | Address Guideline update | Guidelines | 13.06.2023 | 🛠️Partially Deployed🛠️ |
126 | Compressed NFT Standard | Contract Interface | 28.07.2023 | 🛠️Partially Deployed🛠️ |
127 | TON Storage in Metadata | Contract Interface | 23.09.2023 | Proposed |
130 | Rebase Jettons standart | Contract Interface | 04.12.2023 | Proposed |
131 | Referral code in Query ID | Contract Interface | 26.12.2023 | 🛠️Partially Deployed🛠️ |
137 | Jetton Wallet Balance Query | Contract Interface | 09.01.2024 | Proposed |
140 | Programmable Action Phase | Core | 20.01.2024 | Proposed |
141 | Remote onchain execution | Core | 20.01.2024 | Proposed |
142 | TBRC-20 Inscription Token Standard | Contract Interface | 26.01.2024 | Proposed |
145 | Metadata "Hidden" render type | Contract Interface | 26.01.2024 | ✅Deployed✅ |
146 | Semi-fungible token standard | Contract Interface | 17.03.2024 | Proposed |
160 | Dispatch Queue | Core | 13.06.2024 | 🛠️Partially Deployed🛠️ |
161 | Proxy TON (wTON) | Contract Interface | 13.06.2024 | 🛠️Partially Deployed🛠️ |