> ## Documentation Index
> Fetch the complete documentation index at: https://docs.holydocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AddNetwork

Wallet onboarding button that prompts compatible wallets to add a network using built-in presets or explicit chain metadata.

**Interactive playground** For isolated previews, theme switching, and sandbox editing, open [the AddNetwork playground on holydocs.com](https://holydocs.com/components/add-network).

## When to use

Use this component when blockchain context, addresses, chains, token math, or wallet onboarding must stay precise and scannable.

## Live Examples

Every example below renders the real component directly inside HolyDocs, followed by the exact MDX you can paste into a page.

### Preset Chain

Prefer a preset key when the network is already known.



~~~mdx
<AddNetwork chain="polygon" />
~~~

### Custom Network

Pass explicit metadata when documenting a private or early-access chain.



~~~mdx
<AddNetwork chainId={84532} chainName="Base Sepolia" rpcUrl="https://sepolia.base.org" blockExplorer="https://sepolia.basescan.org" currencySymbol="ETH" />
~~~

## Props

| Prop | Type | Default | Description |
| --- | --- | --- | --- |
| `chain` | `string` | `--` | Built-in chain key for known networks like base, polygon, or arbitrum. |
| `chainId` | `number` | `--` | Explicit numeric chain ID for custom networks. |
| `chainName` | `string` | `--` | Human-readable chain name when you are not using a preset. |
| `rpcUrl` | `string` | `--` | RPC URL for a custom network request. |
| `blockExplorer` | `string` | `--` | Optional block explorer root URL. |
| `currencySymbol` | `string` | `--` | Native currency symbol used by the target network. |

## Usage

Start from this baseline shape and then tailor the copy, data, or nesting to the page you are writing.

~~~mdx
<AddNetwork chain="polygon" />
~~~

## Tips

- Assume readers are one copy action away from using the value in production. Precision matters more than flair on web3 surfaces.
- Always make the target chain explicit when a component can imply a wallet, explorer, or transaction context.
- Use testnet examples unless the page is explicitly about production contracts or addresses you expect people to reuse.

## Related Components

**[ChainBadge](/components/chain-badge)**

Compact chain indicator for network-specific instructions, examples, and warnings.
**[Address](/components/address)**

Readable wallet or contract address with truncation, copy-to-clipboard, and optional block-explorer deep link.
**[ContractCall](/components/contract-call)**

Smart contract call block for ABI-backed read or write interactions, with optional interactive execution in supported contexts.

## More

- Interactive playground: [AddNetwork on holydocs.com](https://holydocs.com/components/add-network)
- Component library index: [/components](/components)