Merge pull request #12983 from ethereum/tokenContentStructure

Token standards IA refactor

Author: corwintines

public/content/developers/docs/standards/tokens/erc-20/index.md

@@ -147,9 +147,30 @@ print("Total Supply:", totalSupply)
 print("Addr Balance:", addr_balance)
 ```
 
+## Known issues {#erc20-issues}
+
+### ERC-20 token reception issue {#reception-issue}
+
+When ERC-20 tokens are sent to a smart contract that is not designed to handle ERC-20 tokens, those tokens can be permanently lost. This happens because the receiving contract does not have the functionality to recognize or respond to the incoming tokens, and there’s no mechanism in the ERC-20 standard to notify the receiving contract about the incoming tokens. The main ways this issue takes form is through:
+
+1.	Token transfer mechanism
+  - ERC-20 tokens are transferred using the transfer or transferFrom functions
+	-	When a user sends tokens to a contract address using these functions, the tokens are transferred regardless of whether the receiving contract is designed to handle them
+2.	Lack of notification
+	-	The receiving contract does not receive a notification or callback that tokens have been sent to it
+	-	If the receiving contract lacks a mechanism to handle tokens (e.g., a fallback function or a dedicated function to manage token reception), the tokens are effectively stuck in the contract’s address
+3.	No built-in handling
+	-	The ERC-20 standard does not include a mandatory function for receiving contracts to implement, leading to a situation where many contracts are unable to manage incoming tokens properly
+
 ## Further reading {#further-reading}
 
 - [EIP-20: ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20)
 - [OpenZeppelin - Tokens](https://docs.openzeppelin.com/contracts/3.x/tokens#ERC20)
 - [OpenZeppelin - ERC-20 Implementation](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol)
 - [Alchemy - Guide to Solidity ERC20 Tokens](https://www.alchemy.com/overviews/erc20-solidity)
+
+
+## Other fungible token standards {#fungible-token-standards}
+
+- [ERC-777](/developers/docs/standards/tokens/erc-777)
+- [ERC-4626 - Tokenized vaults](/developers/docs/standards/tokens/erc-4626)

public/content/developers/docs/standards/tokens/index.md

@@ -19,10 +19,11 @@ Many Ethereum development standards focus on token interfaces. These standards h
 Here are some of the most popular token standards on Ethereum:
 
 - [ERC-20](/developers/docs/standards/tokens/erc-20/) - A standard interface for fungible (interchangeable) tokens, like voting tokens, staking tokens or virtual currencies.
+
+### NFT standards {#nft-standards}
+
 - [ERC-721](/developers/docs/standards/tokens/erc-721/) - A standard interface for non-fungible tokens, like a deed for artwork or a song.
-- [ERC-777](/developers/docs/standards/tokens/erc-777/) - ERC-777 allows people to build extra functionality on top of tokens such as a mixer contract for improved transaction privacy or an emergency recover function to bail you out if you lose your private keys.
 - [ERC-1155](/developers/docs/standards/tokens/erc-1155/) - ERC-1155 allows for more efficient trades and bundling of transactions – thus saving costs. This token standard allows for creating both utility tokens (such as $BNB or $BAT) and Non-Fungible Tokens like CryptoPunks.
-- [ERC-4626](/developers/docs/standards/tokens/erc-4626/) - A tokenized vault standard designed to optimize and unify the technical parameters of yield-bearing vaults.
 
 The full list of [ERC](https://eips.ethereum.org/erc) proposals.
 

src/data/developer-docs-links.yaml

@@ -199,12 +199,8 @@
               to: /developers/docs/standards/tokens/erc-20/
             - id: docs-nav-erc-721
               to: /developers/docs/standards/tokens/erc-721/
-            - id: docs-nav-erc-777
-              to: /developers/docs/standards/tokens/erc-777/
             - id: docs-nav-erc-1155
               to: /developers/docs/standards/tokens/erc-1155/
-            - id: docs-nav-erc-4626
-              to: /developers/docs/standards/tokens/erc-4626/
     - id: docs-nav-mev
       to: /developers/docs/mev/
       description: docs-nav-mev-description

src/data/placeholders/content-developers-docs-standards-tokens-erc-4626-data.json

@@ -0,0 +1,6 @@
+{
+  "/content/developers/docs/standards/tokens/erc-4626/map-of-erc-4626.png": {
+    "hash": "c83c47ae",
+    "base64": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAA8AAAAQCAYAAADJViUEAAAACXBIWXMAABYlAAAWJQFJUiTwAAADbklEQVR4nFWSbUyTVxTHrwlqXJwTR6SyRBwgChHjy6iVlhZaXjZlCoKKATO3rJWmBqkvoGUVbBG1LW1V+iKl6UofoKBtUctjibMYaUPSbGRhpsbERBKXLPiBb9q4h9tj7mMc2U1Ozv1wf/n9z8lFLlew00OFYl7voymLzRf1UKGIw3Ev6hmaeDIxNqF8MTM1NRuZ/H1mMhSbmRyPPY89nZ6NPH7+bDp8BsVi8Yfz8wvw8uXfWK+nwOUKwtzcPxCLxXH8rzi1MP8qkUy+hz8e++Fubwdg/JYBAFh489qB7vrCDwigVpsZqVSNz7fqF1taNMmbt0YZ2ke75+J/vp2JhMFu6MIDFiO+P0K9J/Cz6cnbSK+n6NrDbZCZI8EFu+rgYM15tqrrWnEoMO7RyWsSMsl2UB0pAc2Jb0F9rIT5bcQEQaepD6nabbRAJIUvOAKck18L5F4qkYOg9CS+N+j3yMVbEvz1CGrz18JxLgdkomzG1XUSvMZLH+FveD/AyrW7Men7qpRQIm4CfqmMNZ87yE0Iv0LAS0dwIC8Vmr/bzvisKvAaO5fMazhCnL+znjUXl8hYmJgVFXmJykwEpRkI9qxDUL8jjXFflcOgrn0Jzt12CBNrWYWCrU+xibk8axWUZa+Gog0IZKJchnZ3L5n3Fv8My1P34DUcIewobGTNXP6P/5nLNyIo5iAgszfsTmccnSc+wlqtkyYzfp7Ox1lbD7DzkgSiMjkLn6ooSAg4CAq/RLA/dzW7MBL7fzMvW74N5+TVsJE/LYzAyqpdCUlmCggyEBwqSIMm8WZm4KoCRoyX+1BHhyNIoq5I5eL0TZVJobgJ8wQ/4SKhdPGOa5g6VZH/jsTlpaFkYSpKHilY96/1YgN4jR12FAxGabniOmR8LcHfV5+DhsZL0NbWC3VHLy7SowH3L/WChFS0GfgbEFTmfAaK8q1MlLbCbHS8j/ywvap2m7q11fRrp6bfrtU6bzS39JxtVup6B/qp04HbJrvj8pkLJpXSOWTudg7fukb5LFe6I/ddXESOxWLJslodOr9/nPL7aVM4/HSfzeZwDw2N3XB5xjQjgSdVN62D/aO+R27PcFAXeBjNYkEASCFdqzXz9HpLj9ncd8VgsBsMBrsxFIqI6w43Hu3uMtqsvf0aY4/N4HSOFpH31ZuyUz4APicGWaM0LgMAAAAASUVORK5CYII="
+  }
+}