ton-blockchain · Danielflord · Dec 20, 2023 · Dec 20, 2023 · Jan 21, 2024 · Jun 21, 2024
diff --git a/README.md b/README.md
@@ -28,3 +28,33 @@ Proposal management is done using GitHub pull requests, the process is described
 | [85](./text/0085-sbt-standard.md)            | SBT Contract                       | Contract Interface | 09.08.2022 |
 | [89](./text/0089-jetton-wallet-discovery.md) | Discoverable Jettons Wallets       | Contract Interface | 08.09.2022 |
 | [115](./text/0115-ton-connect.md)            | TON Connect                        | Core               | 20.10.2022 |
+
+
+## WIP
+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](https://github.com/ton-blockchain/TEPs/pull/91/files)            | Contract Source Registry             | Infrastructure     | 09.09.2022 | ✅Deployed✅ |
+| [92](https://github.com/ton-blockchain/TEPs/pull/92/files)            | Wallet Registry                      | Infrastructure     | 11.09.2022 | Proposed    |
+| [96](https://github.com/ton-blockchain/TEPs/pull/96/files)            | Dicts/Arrays in Metadata             | Contract Interface | 21.09.2022 | Proposed    |
+| [104](https://github.com/ton-blockchain/TEPs/pull/104/files)          | Data Signatures                      | Contract Interface | 13.12.2022 | Proposed    |
+| [121](https://github.com/ton-blockchain/TEPs/pull/121/files)          | Lockable Jetton Wallet               | Contract Interface | 13.04.2023 | Proposed    |
+| [122](https://github.com/ton-blockchain/TEPs/pull/122/files)          | Onchain reveal mechanic              | Contract Interface | 31.10.2022 | ✅Deployed✅ |
+| [123](https://github.com/ton-blockchain/TEPs/pull/123/files)          | Address Guideline update             | Guidelines         | 13.06.2023 | 🛠️Partially Deployed🛠️ |
+| [126](https://github.com/ton-blockchain/TEPs/pull/126/files)          | Compressed NFT Standard              | Contract Interface | 28.07.2023 | 🛠️Partially Deployed🛠️ |
+| [127](https://github.com/ton-blockchain/TEPs/pull/127/files)          | TON Storage in Metadata              | Contract Interface | 23.09.2023 | Proposed |
+| [130](https://github.com/ton-blockchain/TEPs/pull/130/files)          | Rebase Jettons standart              | Contract Interface | 04.12.2023 | Proposed |
+| [131](https://github.com/ton-blockchain/TEPs/pull/131/files)          | Referral code in Query ID            | Contract Interface | 26.12.2023 | 🛠️Partially Deployed🛠️ |
+| [137](https://github.com/ton-blockchain/TEPs/pull/137/files)          | Jetton Wallet Balance Query          | Contract Interface | 09.01.2024 | Proposed |
+| [140](https://github.com/ton-blockchain/TEPs/pull/140/files)          | Programmable Action Phase            | Core               | 20.01.2024 | Proposed |
+| [141](https://github.com/ton-blockchain/TEPs/pull/141)                | Remote onchain execution             | Core               | 20.01.2024 | Proposed |
+| [142](https://github.com/ton-blockchain/TEPs/pull/142/files)          | TBRC-20 Inscription Token Standard   | Contract Interface | 26.01.2024 | Proposed |
+| [145](https://github.com/ton-blockchain/TEPs/pull/145/files)          | Metadata "Hidden" render type        | Contract Interface | 26.01.2024 | ✅Deployed✅ |
+| [146](https://github.com/ton-blockchain/TEPs/pull/146/files)          | Semi-fungible token standard         | Contract Interface | 17.03.2024 | Proposed |
+| [160](https://github.com/ton-blockchain/TEPs/pull/160)                | Dispatch Queue                       | Core               | 13.06.2024 | 🛠️Partially Deployed🛠️ |
+| [161](https://github.com/ton-blockchain/TEPs/pull/161/files)          | Proxy TON (wTON)                     | Contract Interface | 13.06.2024 | 🛠️Partially Deployed🛠️ |
diff --git a/text/0064-token-data-standard.md b/text/0064-token-data-standard.md
@@ -82,6 +82,7 @@ Three options can be used:
    Data encoded as described in "2. On-chain content layout".
    The dictionary must have `uri` key with a value containing the URI pointing to the JSON document with token metadata.
    Clients in this case should merge the keys of the on-chain dictionary and off-chain JSON doc.
+   In case of collisions (the field exists in both off-chain data and on-chain data), on-chain values are used.
 
 ## Data serialization
 Data that does not fit in one cell can be stored in two ways:
@@ -107,9 +108,9 @@ If the prefix is not `0x00` or `0x01`, then the data is probably encoded by the
 ## Informal TL-B scheme:
 ```
 text#_ {n:#} data:(SnakeData ~n) = Text;
-snake#00 data:(SnakeData ~n) = ContentData;
+snake#00 {n:#} data:(SnakeData ~n) = ContentData;
 chunks#01 data:ChunkedData = ContentData;
-onchain#00 data:(HashMapE 256 ^ContentData) = FullContent;
+onchain#00 data:(HashmapE 256 ^ContentData) = FullContent;
 offchain#01 uri:Text = FullContent;
 ```
 
@@ -171,3 +172,5 @@ None
 * 31 Aug 2022 - added note about data encoded in TL-B schema in "Data serialization" paragraph.
 
 * 14 Oct 2022 - render_type and amount_style for Jetton metadata
+
+* 20 Dec 2023 - added clarification for semi-chain data: "In case of collisions (the field exists in both off-chain data and on-chain data), on-chain values are used."
diff --git a/text/0066-nft-royalty-standard.md b/text/0066-nft-royalty-standard.md
@@ -58,7 +58,7 @@ NFT Collection smart contract MUST implement:
    Send back message with the following layout and send-mode `64` (return msg amount except gas fees):
    TL-B schema `report_royalty_params#a8cb00ad query_id:uint64 numerator:uint16 denominator:uint16 destination:MsgAddress = InternalMsgBody;`
 
-It is expected that marketplaces which want to participate in royalty payments will send `muldiv(price, nominator, denominator)` to `destination` address after NFT sale.
+It is expected that marketplaces which want to participate in royalty payments will send `muldiv(price, numerator, denominator)` to `destination` address after NFT sale.
 
 Marketplaces SHOULD neglect zero-value royalty payments.
 

diff --git a/text/0074-jettons-standard.md b/text/0074-jettons-standard.md
@@ -25,7 +25,7 @@ Jetton standard describes:
 ## Useful links
 1. [Reference jetton implementation](https://github.com/ton-blockchain/token-contract/)
 2. [Jetton deployer](https://jetton.live/)
-3. FunC Jetton lesson ([en](https://github.com/romanovichim/TonFunClessons_Eng/blob/main/9lesson/ninthlesson.md)/[ru](https://github.com/romanovichim/TonFunClessons_ru/blob/main/9lesson/ninthlesson.md))
+3. FunC Jetton lesson ([en](https://github.com/romanovichim/TonFunClessons_Eng/blob/main/lessons/smartcontract/9lesson/ninthlesson.md)/[ru](https://github.com/romanovichim/TonFunClessons_ru/blob/main/lessons/smartcontract/9lesson/ninthlesson.md))
 
 # Specification
 

diff --git a/text/0081-dns-standard.md b/text/0081-dns-standard.md
@@ -143,10 +143,7 @@ proto_list_next$1 head:Protocol tail:ProtoList = ProtoList;
 
 
 
-cap_method_seqno#5371 = SmcCapability;
-cap_method_pubkey#71f4 = SmcCapability;
 cap_is_wallet#2177 = SmcCapability;
-cap_name#ff name:Text = SmcCapability;
 
 cap_list_nil$0 = SmcCapList;
 cap_list_next$1 head:SmcCapability tail:SmcCapList = SmcCapList;
@@ -193,3 +190,13 @@ None
 # Future possibilities
 
 1. Implement private (encrypted) fields
+
+# Changelog
+
+* 20 Dec 2023 - deleted unused capabilities:
+
+   ```
+   cap_method_seqno#5371 = SmcCapability;
+   cap_method_pubkey#71f4 = SmcCapability;
+   cap_name#ff name:Text = SmcCapability;
+   ```
diff --git a/text/0085-sbt-standard.md b/text/0085-sbt-standard.md
@@ -34,8 +34,10 @@ forward_payload:^Cell with_content:Bool = InternalMsgBody;
 
 `with_content` - if true, SBT's content cell will be included in message to contract.
 
-**Should do:**
+**Should be rejected if:**
+* Sender address is not the owner's address.
 
+**Otherwise should do:**
 Send message with TL-B schema to `dest` contract:
 ```
 ownership_proof#0524c7ae query_id:uint64 item_id:uint256 owner:MsgAddress 

diff --git a/text/Alex b/text/Alex
@@ -0,0 +1 @@
+