> For the complete documentation index, see [llms.txt](https://svpchain.gitbook.io/svpchain-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://svpchain.gitbook.io/svpchain-docs/ecosystem/bridges.md).

# Bridges

***

### description: Move assets between Ethereum and SVPChain.

## Bridges

SVPChain ships with a **native bridge** between EVM L1 networks and SVPChain, integrated into the protocol via the bridge daemon that every full node runs. On testnet, supported L1 counterparts are **Ethereum Sepolia** and **Arbitrum Sepolia**. The bridge contracts on the L1 side are a fork of the [Hyperliquid](https://hyperliquid.xyz) bridge contracts.

{% hint style="warning" %}
**Bridges are the highest-risk integration point in any chain.** Always verify URLs and contract addresses against this page before signing. Make a small test transfer first on any new path, even one you've used before.
{% endhint %}

#### Official bridge

| Direction | Source chain                        | Destination               | Status                 |
| --------- | ----------------------------------- | ------------------------- | ---------------------- |
| Deposit   | Ethereum **Sepolia**                | SVPChain Testnet (`2517`) | Live                   |
| Withdraw  | SVPChain Testnet                    | Ethereum Sepolia          | Live                   |
| Deposit   | **Arbitrum Sepolia**                | SVPChain Testnet (`2517`) | Live                   |
| Withdraw  | SVPChain Testnet                    | Arbitrum Sepolia          | Live                   |
| Mainnet   | Ethereum Mainnet ↔ SVPChain Mainnet | TBD                       | Pending mainnet launch |

**Bridge UI:** <https://bridge.svpstars.com>

**Contract addresses:**

| Network                       | Contract                   | Address                                      | Deployed   |
| ----------------------------- | -------------------------- | -------------------------------------------- | ---------- |
| SVPChain Testnet (`2517`)     | SVPBridge proxy            | `0xC2C7f43735C4bEC84eABbcce32bDA269c2c75f20` | 2026-07-28 |
| SVPChain Testnet (`2517`)     | SVPBridgeV2 implementation | `0xeDad69Ecd39936c4C24478494aEf24793715182e` | 2026-08-04 |
| Ethereum Sepolia (`11155111`) | SVPBridge proxy            | `0x889DBfC7F0349e8648C8b71D104d8d3c4f59bCa4` | 2026-07-28 |
| Ethereum Sepolia (`11155111`) | SVPBridgeV2 implementation | `0x9142312a9F171Faf10E17d6fcCC5675910057038` | 2026-08-04 |
| Arbitrum Sepolia (`421614`)   | SVPBridge proxy            | `0x865328a6Cdf6a3017C16b9a682d823031613F52B` | 2026-07-28 |
| Arbitrum Sepolia (`421614`)   | SVPBridgeV2 implementation | `0x889DBfC7F0349e8648C8b71D104d8d3c4f59bCa4` | 2026-08-04 |
| Mainnet                       | SVPBridge                  | TODO (pending mainnet)                       | —          |

USDV proxy address (use for ERC-20 integrations): `0x013a61E622e6ABFCaB64F52D274C3Fc0aA37f951`. Full token and role details: [Testnet contracts § USDV](/svpchain-docs/reference/testnet-contracts.md#usdv-stablecoin).

**Testnet networks (for wallet / RPC setup):**

**Ethereum Sepolia**

| Field           | Value                                                                                 |
| --------------- | ------------------------------------------------------------------------------------- |
| Chain ID        | `11155111`                                                                            |
| RPC             | `https://ethereum-sepolia-rpc.publicnode.com`                                         |
| Block explorer  | <https://sepolia.etherscan.io>                                                        |
| Native currency | ETH (SepoliaETH)                                                                      |
| Test ETH faucet | <https://www.alchemy.com/faucets/ethereum-sepolia> (and other public Sepolia faucets) |

**Arbitrum Sepolia**

| Field           | Value                                    |
| --------------- | ---------------------------------------- |
| Chain ID        | `421614`                                 |
| RPC             | `https://sepolia-rollup.arbitrum.io/rpc` |
| Block explorer  | <https://sepolia.arbiscan.io>            |
| Native currency | ETH (SepoliaETH)                         |

**SVPChain Testnet**

Endpoints, chain IDs, RPC, WebSocket, explorer, and faucet: [Networks](/svpchain-docs/chain/networks.md).

#### How it works

1. **Deposit.** A user sends supported assets to the bridge contract on the source L1 (Ethereum Sepolia or Arbitrum Sepolia).
2. **Detection.** The bridge daemon embedded in `svpchaind` polls the configured L1 RPC (`--bridge-daemon-eth-rpc-endpoint`, default Ethereum Sepolia public RPC) for deposit events.
3. **Mint.** Once the deposit is finalized on the L1, validators credit the equivalent balance on SVPChain.
4. **Withdraw.** The user submits a withdrawal on SVPChain; the bridge contract releases funds on the destination L1.

Because the bridge daemon is part of the validator stack, message-passing is in-protocol — there is no third-party bridge operator.

#### Safety checklist

* **Verify the bridge URL** against this page (and against an out-of-band source like the official Twitter `@SvpChain`) before connecting a wallet.
* **Verify the contract address** in MetaMask before signing — phishing sites use look-alike addresses.
* **Make a small test transfer first.** Always.
* **Wait for finality before re-using funds.** On the SVPChain side this is one block (1s). On the L1 side, wait the standard finality window (Ethereum mainnet 12.8 min; Sepolia 6.4 min in the worst case; Arbitrum Sepolia inherits Ethereum Sepolia finality plus the L2 challenge window — allow extra time before re-using withdrawn funds).
* **Save the tx hashes on both sides** for support requests.

#### Third-party bridges

None officially supported at this time. If a third-party bridge advertises support for SVPChain, treat it as untrusted until it's listed here.

#### Next steps

| Related                      | Link                                                              |
| ---------------------------- | ----------------------------------------------------------------- |
| Endpoints and chain IDs      | [networks.md](/svpchain-docs/chain/networks.md)                   |
| Get test funds via faucet    | [faucet-testnet.md](/svpchain-docs/get-started/faucet-testnet.md) |
| Architecture (bridge daemon) | [architecture.md](/svpchain-docs/chain/architecture.md)           |


---

# 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://svpchain.gitbook.io/svpchain-docs/ecosystem/bridges.md?ask=<question>&goal=<endgoal>
```

`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.