> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/cryptos/base.md). # Base Official Website: [base.org](https://base.org/) Base `(ETH)` is a Layer-2 network for Ethereum built by Coinbase. A Layer-2 is a separate chain that processes transactions off of Ethereum's main chain and posts them back to it, giving you much lower fees and faster confirmations while inheriting Ethereum's security. This wallet type supports the **Base** network. Do not send funds to or receive funds from other networks using this wallet. ## Addresses In Cake Wallet's Base wallet, there is only one address per wallet, which is standard for the Ethereum ecosystem. Keep in mind that this has lesser privacy compared to some other assets, where new addresses are automatically generated. Your Base address starts with `0x` followed by a series of alphanumeric characters. This is the same `0x` address format used on Ethereum and other EVM chains, so the same address can receive funds on many chains. {% hint style="warning" %} The `0x` address format is the same across EVM chains, but the network is not. Make sure the sender uses the **Base** network. A token sent on the wrong network (for example Ethereum mainnet instead of Base) will not arrive. {% endhint %} ## Seed Format Cake Wallet uses a 12-word BIP39 seed for Base wallets by default. Under `Advanced Settings` on the wallet creation screen you can choose a **24-word** BIP39 seed instead, and you can add a seed passphrase. When creating or restoring a wallet, you can use the seed phrase or the private key. The derivation path used is `m/44'/60'/0'/0`. {% hint style="info" %} Because Base shares the same seed format and derivation path as Ethereum, its seed can be shared with your other Cake Wallet currencies as part of a [wallet group](https://docs.cakewallet.com/features/managing-your-wallet/wallet-groups). {% endhint %} ## Fee Levels Transaction fees are a necessary part of sending ETH or ERC-20 tokens. ETH is consumed as a 'gas' fee when making any transaction from a Base wallet. This also applies to sending ERC-20 tokens. For example, to send USDT, you pay a network fee in ETH, not USDT. Thus, sending 10 USDT costs a small amount of ETH, and the recipient receives the full 10 USDT. Cake Wallet offers three fee levels for transactions: * **Slow**: Cheaper but may take longer to confirm. * **Medium**: Recommended for most transactions. Balanced speed and cost. * **Fast**: Expensive but confirms quickly. These fee levels are determined automatically using current network fee rates. ## MEV protection When you send a Base transaction, Cake Wallet broadcasts it privately through [Blink](https://blinklabs.xyz/) rather than the public mempool. This protects your transaction from MEV — "maximal extractable value" attacks such as front-running and sandwiching, where bots watch the public mempool and reorder or insert transactions around yours to profit at your expense. Blink protection is enabled by default. If a private broadcast ever fails, Cake Wallet automatically falls back to a normal broadcast so your transaction still goes through. You can turn it off with the `Use Blink Protection` toggle under `Connections` in settings. Base and Ethereum are the only two chains in Cake Wallet with Blink protection. ## Tokens Cake Wallet's Base wallet can store ERC-20 tokens in addition to ETH. Some common tokens such as USDC, USDe, DAI, and USDT are displayed by default. To show other ERC-20 tokens, open the `Assets` tab on your home screen, tap the `Tokens` button, and enable them. ### Adding a new token You can add a new ERC-20 token from the same `Tokens` screen: search for your desired token, then tap to enable it. If the token does not appear, you can add it by [contract address](https://docs.cakewallet.com/features/advanced/add-custom-tokens). Paste the address of the custom token you wish to add, then click the `+` button. ## Transaction history Transaction history is populated using the BaseScan API. You can enable or disable this API lookup under `BaseScan History` under `Settings` → `Connections`. --- # 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.cakewallet.com/cryptos/base.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.