> For the complete documentation index, see [llms.txt](https://docs.degate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.degate.com/security-and-self-custody/wallet-address-and-networks.md). # Wallet Addresses & Networks One DeGate wallet gives you addresses across supported chains. How those addresses come to exist depends on which type of wallet you use; this page explains each type and what it means for recovery. ## Your addresses across chains When you receive assets, use your DeGate address for the network the sender is on: tap **Receive** in the app, pick the chain, and copy the address or share the QR code. Your DeGate address is the same across all EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB and so on): these chains share a single underlying key, rather than being independently generated per chain. Solana, Aptos, and Bitcoin use their own address formats. Incoming deposits are detected automatically, and everything you receive shows up in your unified balance. Since only your private keys can authorize transactions from these addresses, DeGate cannot unilaterally move your funds. ## How your wallet is created ### Mnemonic wallets (created or imported) **Create Wallet** generates a random 12-word BIP39 recovery phrase locally on your device; **Import Wallet** accepts an existing 12-word phrase. Per-chain private keys are derived from the phrase using BIP44, the standard framework for hierarchical deterministic wallets. To restore the same addresses in another wallet application, it must support the recovery phrase, network, derivation path, and account settings used for that address. BIP39/BIP44 support alone does not guarantee that an application will display the same account. Check the restored address before receiving or sending assets. ### Hardware wallets Your private key never leaves the hardware device; DeGate reads your addresses over standard derivation paths. The mobile app supports Bluetooth-capable OneKey and Ledger models for receiving, sending, trading, cross-chain transfers, and Turbo Range. Check the connection screen for supported models and networks, and confirm signatures on the hardware device. Hardware wallet accounts pay network gas from their own address in the chain's native token, not from your DeGate balance. Keep a small balance there (for example, ETH on Base or SOL on Solana) for sends and Turbo Range operations, including closing a position. ### Email, external-wallet, and web-sync wallets These wallet types don't start from a phrase you write down. Instead, DeGate derives an operating wallet from your existing login (your email-linked embedded wallet, or the external wallet you signed in with), through a signature-based process managed entirely by the DeGate app. For an external-wallet or web-sync account, the derived DeGate addresses are separate from your original external-wallet address. Restoring that external wallet in another application does not by itself restore the derived DeGate balances. Reconnect the same external wallet in the DeGate app to restore the derived addresses. For an email wallet, use the original email address and DeGate password in the DeGate app. ## Supported networks The current list of supported networks appears in [What is DeGate](/about-degate/readme.md#supported-networks), with per-network fee tiers on the [Fees](/fees/fees.md) page. Addresses for newly-supported chains are generated the first time you enable that chain, not automatically ahead of time. Hardware-wallet accounts cover a subset of networks; check the app for current coverage. ## What this means for recovery * **Mnemonic wallet:** back up its 12-word recovery phrase. Restore in DeGate, or in wallet software with the same network, derivation path, and account settings, then verify the address. If you created several wallets, back up each phrase separately. * **Hardware wallet:** keep the device and the recovery backup created during its setup. Reconnect it to DeGate, or use wallet software that supports the same device, network, and derivation path. Check that the address matches. A pool position may require an interface that supports the underlying protocol. * **Email wallet:** use the original email address and DeGate password in the DeGate app. This recovery method depends on the email-linked wallet infrastructure and DeGate's sign-in flow. * **External-wallet / web-sync:** preserve access to the original external wallet, then reconnect it in the DeGate app. Assets at derived DeGate addresses will not appear merely because you restore the original external-wallet address elsewhere. Restoring email and external-wallet / web-sync wallets outside the DeGate app is not currently supported. These methods have different recovery dependencies from a recovery phrase or hardware wallet. ### If you lose access to your email An email wallet depends on access to its linked email address. If you permanently lose access to that email, you may be unable to recover the wallet. Your DeGate password is separate from your email provider's password. We do not recommend keeping large balances in an email wallet; for funds you need to recover independently of email sign-in, consider a recovery phrase wallet or a supported hardware wallet and keep its backup securely. ## FAQ **Can I send any token to my DeGate address?** Send tokens on their matching network to your address for that network. Everything on supported networks lands in your unified balance. **Why is my address the same on Ethereum and Base?** All EVM chains share a single underlying key in your DeGate wallet, so they share one address. That makes receiving simpler: any EVM network's deposit goes to the same address, and you pick the network when sharing it. Solana, Aptos, and Bitcoin use their own address formats. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.degate.com/security-and-self-custody/wallet-address-and-networks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.