Merge pull request 0xPolygon#258 from 0xPolygon/mapping-requst-update

PoS - Token mapping

Author: hsutaiyu

docs/img/pos/token-mapping-1.png

@@ -1,6 +1,10 @@
 The mechanism to natively read Ethereum data from Polygon EVM chain is that of ‘State Sync’. In other words, this mechanism enables transfer of arbitrary data from Ethereum chain to Polygon chain. The procedure that makes it possible is: Validators on the Heimdall layer are listening for a particular event — `StateSynced` from a Sender contract, as soon as the event is picked, the `data` that was passed in the event is written on the Receiver contract. Read more [here](../../../architecture/bor/state-sync.md).
 
-The Sender and Receiver contract are required to be mapped on Ethereum — [StateSender.sol](https://github.com/maticnetwork/contracts/blob/release-betaV2/contracts/root/stateSyncer/StateSender.sol) needs to be aware of each sender and receiver. If you'd like to get the mapping done, please request a mapping [here](https://mapper.polygon.technology/).
+The Sender and Receiver contract are required to be mapped on Ethereum — [StateSender.sol](https://github.com/maticnetwork/contracts/blob/release-betaV2/contracts/root/stateSyncer/StateSender.sol) needs to be aware of each sender and receiver.
+
+!!! tip "Custom tokens"
+
+    Looking to bridge your custom token to Polygon PoS using the official bridge? Check out the guide on [how to submit a request to get your token mapped](../ethereum-polygon/submit-mapping-request.md).
 
 ---
 
@@ -109,9 +113,9 @@ Deploy  your Receiver.sol on Polygon's testnet and keep a note of the address an
 
 ### 3. Getting your Sender and Receiver mapped
 
-You can either use the already deployed addresses (mentioned above) for sender and receiver, or deploy your custom contracts and request a mapping done here: [https://mapper.polygon.technology/](https://mapper.polygon.technology/)
+You can either use the already deployed addresses (mentioned above) for sender and receiver, or deploy your custom contracts and request a mapping using [the Google form here](https://docs.google.com/forms/d/e/1FAIpQLSeq8HTef2dYpRx35_WWYhyr4C146K9dfhyYJQcoD1RuTTVABg/viewform).
 
-### 4. Sending and Receiving data
+### 4. Sending and receiving data
 
 Now that we have our contracts in place and mapping done, we'll be writing a simple node script to send arbitrary hex bytes, receive them on Polygon and interpret the data!
 

docs/img/pos/token-mapping-2.png

@@ -1,15 +1,17 @@
-Polygon brings you a trustless two-way transaction channel between Polygon PoS and Ethereum by introducing the cross-chain bridge. With this users can transfer tokens across Polygon PoS without incurring third-party risks and market liquidity limitations. 
+Polygon brings you a trustless two-way transaction channel between Polygon PoS and Ethereum by introducing the cross-chain bridge. The official bridge allows you to transfer tokens between Ethereum and Polygon PoS without incurring third-party risks and market liquidity limitations. 
 
-The PoS Bridge is available on both Mumbai Testnet as well as Polygon PoS Mainnet. You can access it and bridge assets over to Polygon PoS using the [Polygon Wallet Suite](https://wallet.polygon.technology/polygon/bridge/deposit).
+The official bridge is available on both Mumbai Testnet as well as Polygon PoS Mainnet, and provides a near-instant, low-cost, and flexible bridging option for both users and dApp developers. You can access it and bridge assets from Ethereum over to Polygon PoS using [Polygon Portal](https://portal.polygon.technology).
 
-Polygon PoS bridge provides a bridging mechanism that is near-instant, low-cost, and quite flexible.
+!!! tip "Polygon Portal"
 
-There is no change to the circulating supply of your token when it crosses the bridge;
+    To learn more about the features that Polygon Portal offers, and a series of step-by-step reference guides that help you with using the platform, check out [the doc available here](../../../../tools/wallets/portal.md).
 
-- Tokens that leave the Ethereum network are locked and the same number of tokens are minted on Polygon PoS as a pegged token (1:1).
-- To move the tokens back to the Ethereum network, tokens are burned on Polygon PoS network and unlocked on Ethereum network during the process.
+There is no change to the circulating supply of your token when it crosses the bridge. This is what goes on in the background when you bridge your tokens over to Polygon PoS from Ethereum:
 
-## Additional Resources
+- When depositing, tokens that leave the Ethereum network are locked and the same number of tokens are minted on Polygon PoS as a pegged token (1:1).
+- When withdrawing tokens back to the Ethereum network, tokens are burned on Polygon PoS and unlocked on Ethereum during the process.
+
+## Additional resources
 
 - [Introduction to Blockchain Bridges](https://ethereum.org/en/bridges/)
 - [What are Cross-Chain Bridges](https://www.alchemy.com/overviews/cross-chain-bridges)

docs/img/pos/token-mapping-3.png

@@ -1,36 +1,29 @@
-Mapping is necessary in order to transfer your assets to and from Ethereum and Polygon PoS. We offer two bridges to do the same. More details on the bridge can be understood [here](index.md).
+Token mapping is important in order to enable the transfer mechanism for the said token between Ethereum and Polygon PoS.
 
-!!!info
+!!! info
 
-    The Polygon PoS bridge is available for both Polygon Mainnet as well as Mumbai Testnet.
+    - For more information on how bridging works in the background, see [the doc available here](../index.md).
+    - Thinking about bridging another popular token? Refer to the [reference guide on Polygon Portal](../../../../tools/wallets/portal.md).
 
 ## Steps to submit a mapping request
 
-In order to map tokens between Ethereum and Polygon PoS, you may use the [Polygon Token Mapper](https://mapper.polygon.technology/). Open the link and click on the **Map New Token** button on the top right corner to initiate a new mapping request.
+1. To submit a request for mapping your token on Polygon PoS, start by navigating to [the Google form available here](https://docs.google.com/forms/d/e/1FAIpQLSeq8HTef2dYpRx35_WWYhyr4C146K9dfhyYJQcoD1RuTTVABg/viewform).
 
-![image](https://github.com/0xPolygon/wiki/assets/104004697/c530ceed-cf6a-4c5e-a3fe-b493eef1c761)
+2. Choose a "Network" option depending upon the chain on which you're looking to map your token. This would be **"Sepolia <> Polygon Amoy"** for testnet, and **"Ethereum <> Polygon PoS"** for mainnet.
 
-Click on Raise Mapping Request (a Google Form pops up).
+  ![](../../../../img/pos/token-mapping-1.png)
 
-![image](https://github.com/0xPolygon/wiki/assets/104004697/0c08656f-3ffd-43ee-819e-722786d7015d)
+3. Next, input the contract address for the token contract that you've deployed on Sepolia/Ethereum mainnet in the "Root Contract Address (L1)" field.
 
-**Step 1 &rarr;** Choose the network on which you want to map your token. You may choose **Goerli-Mumbai** for Testnet, and **Ethereum-Polygon PoS** for the Mainnet.
+  ![](../../../../img/pos/token-mapping-2.png)
 
-**Step 2 &rarr;** Select the type of token you are mapping - **ERC20**, **ERC721**, or **ERC1155**.
+4. Choose the correct "Token Type" for your token. i.e., [ERC-20](https://eips.ethereum.org/EIPS/eip-20) for a standard token, [ERC-721](https://eips.ethereum.org/EIPS/eip-721) for an NFT, or [ERC-1155](https://eips.ethereum.org/EIPS/eip-1155) for a multi token.
 
-**Step 2 &rarr;** Enter your **Ethereum/Goerli** token address in the  **Root Contract Address (L1)**  field. Make sure your token contract code has been verified on the **Ethereum/Goerli** blockchain explorers.
+  ![](../../../../img/pos/token-mapping-3.png)
 
-**Step 4 &rarr;** After adding the Select the type of token you are mapping - **ERC20**, **ERC721**, or **ERC1155**.
+5. Finally, select "Submit" to send in your request. The Polygon team will review your mapping request, and get back to you with a response. This generally takes up to 7 days.
 
-**Step 5 &rarr;** Now, click on the **Submit** button to initiate the mapping process. Our team will review the mapping request and get back to you in 7 days.
+!!! info "Token list"
 
-For a successful Mainnet mapping, you may provide your token details [here](https://github.com/maticnetwork/polygon-token-list/issues/new/choose) to be added on the [**Polygon Token List**](https://api-polygon-tokens.polygon.technology/tokenlists/polygonTokens.tokenlist.json).
-
-## Video Guide
-
-Here is a quick video tutorial on how to map tokens between **Ethereum Goerli &harr; Polygon Mumbai Testnet**:
-
-<video autoplay width="100%" height="100%" controls="true" >
-  <source type="video/mp4" src="/img/token-mapping/token-mapper.mp4"></source>
-  <p>Your browser does not support the video element.</p>
-</video>
+    - Check out the list of supported tokens available in JSON format by following this URL: https://api-polygon-tokens.polygon.technology/tokenlists/polygonTokens.tokenlist.json
+    - Once approved, your token will be added to the above list!

docs/pos/how-to/bridging/ethereum-polygon/ethereum-to-matic.md

@@ -1,14 +1,13 @@
 This document provides examples of token mappings on the Polygon PoS and Mumbai testnet.
 
-!!!tip
-    Mapping
+!!!tip "Token mapping"
 
-    If you want to get your token mapped then please send your mapping request via [<ins>mapper.polygon.technology</ins>](https://mapper.polygon.technology/).
+    Want to get a custom token mapped to Polygon PoS so it can be bridged over? Send in your mapping request via [this Google form](https://docs.google.com/forms/d/e/1FAIpQLSeq8HTef2dYpRx35_WWYhyr4C146K9dfhyYJQcoD1RuTTVABg/viewform).
 
 
 ### Mumbai
 
-| Token Name        | Bridge | Parent Chain Address: Goerli                                                                                                 | Child Chain: MUMBAI                                                                                                                          |
+| Token name        | Bridge | Parent chain address: Goerli                                                                                                 | Child chain: MUMBAI                                                                                                                          |
 | ----------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
 | PoS\-WETH         | PoS    | [0x60D4dB9b534EF9260a88b0BED6c486fe13E604Fc](https://goerli.etherscan.io/address/0x60D4dB9b534EF9260a88b0BED6c486fe13E604Fc) | [0xA6FA4fB5f76172d178d61B04b0ecd319C5d1C0aa](https://mumbai.polygonscan.com/address/0xA6FA4fB5f76172d178d61B04b0ecd319C5d1C0aa) |
 | DummyERC20Token   | PoS    | [0x655F2166b0709cd575202630952D71E2bB0d61Af](https://goerli.etherscan.io/address/0x655F2166b0709cd575202630952D71E2bB0d61Af) | [0xfe4F5145f6e09952a5ba9e956ED0C25e3Fa4c7F1](https://mumbai.polygonscan.com/address/0xfe4F5145f6e09952a5ba9e956ED0C25e3Fa4c7F1) |