> For the complete documentation index, see [llms.txt](https://docs.ddrops.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ddrops.world/technology/usddop-token-evolution/ethereum-migration.md). # Ethereum Migration ## Guide to the DOP Token Transition and Bridging from Polygon to Ethereum Holders of the original DOP tokens will receive an airdrop of the updated $DOP tokens on the Polygon network on March 2, 2024. Following this airdrop, token holders will have the opportunity to bridge their tokens to the Ethereum network, utilizing the official Polygon-Ethereum bridge. This document outlines the steps required for a smooth transition and bridging process. ### Airdrop of Updated $DOP Tokens on Polygon #### Receiving Your Airdrop On March 2, 2024, all eligible holders of the original DOP tokens will automatically receive the updated $DOP tokens on the Polygon network through an airdrop. This process requires no action from your end to claim your new tokens. #### New Polygon (POS) Token Contract Address Your new $DOP tokens on Polygon will be associated with the following contract address: **0xF24A9cD051dD11E815Cbf699EDD704541a08B996**. Ensure to add this address to your wallet to view and manage your airdropped tokens. ### Bridging Your $DOP Tokens to Ethereum After receiving your airdropped $DOP tokens on the Polygon network, you have the option to bridge these tokens to the Ethereum network. This process is facilitated through the official Polygon-Ethereum bridge, ensuring a secure and efficient transition of your tokens between networks. #### Steps to Bridge Your Tokens 1. **Access the Official Polygon-Ethereum Bridge:** Visit to access the official bridging tool. 2. **Connect Your Wallet:** Select the option to connect your wallet to the bridge portal. Ensure your wallet is configured with the Polygon network and contains the airdropped $DOP tokens. 3. **Initiate the Bridging Process:** Follow the on-screen instructions to select the amount of $DOP tokens you wish to bridge to the Ethereum network. Confirm the transaction in your wallet to initiate the bridging process. 4. **Wait for Confirmation:** The bridging process may take some time to complete. You can monitor the transaction status through the bridge portal or your wallet. #### Adding Ethereum Network and $DOP Token Contract Address To view and manage your $DOP tokens on the Ethereum network after bridging, ensure your wallet is configured with the Ethereum network and add the new Ethereum $DOP token contract address: **0x2a7CAd775fd9C5c43f996A948660fFc21b4e628c**. ### Security Reminder During this process, it is crucial to ensure the security of your private keys and wallet information. Do not share your private keys with anyone and avoid clicking on links from unverified sources. By following these steps, you will successfully transition and bridge your $DOP tokens from the Polygon network to Ethereum. For further assistance, please reach out to our support team at . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ddrops.world/technology/usddop-token-evolution/ethereum-migration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.