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

# Testnets

> Build against Ethereum Sepolia and Solana devnet on the production host, with test tokens you mint yourself on Sepolia or get from the Multiliquid team on devnet.

The test networks run on the production host, `https://api.multiliquid.xyz`, with the same routes, except redemptions, and the same API keys. Going live changes only the network key.

| Network | Key | Tokens |
| - | - | - |
| Ethereum Sepolia | `evm-sepolia` | Mock tokens you mint yourself |
| Solana devnet | `svm-devnet` | Mock tokens from the Multiliquid team |

List what each network offers with the same discovery calls as on mainnet:

```bash theme={null}
curl "https://api.multiliquid.xyz/v1/swap/pairs?network=evm-sepolia"
```

## Fund a Sepolia wallet

1. **Get Sepolia ETH** from a public Sepolia faucet, for network fees.

2. **Mint test tokens.** The Sepolia mock tokens, such as `MUSDC` and `MRWA`, let any wallet mint them. Call `mint(address to, uint256 amount)` on the token. This is a contract call, so the amount is in the token's on-chain base units, not the whole tokens the API takes:

   ```bash theme={null}
   cast send $MUSDC "mint(address,uint256)" $WALLET 1000000000 \
     --rpc-url $SEPOLIA_RPC_URL --private-key $PRIVATE_KEY
   ```

3. **Try an RWA with transfer rules.** `MWRWA` transfers only to a wallet that has called `setKYC(true)` on it, the way some issuers restrict holders. The API cannot read that rule before it simulates the swap, so a build into `MWRWA` reports `checks.eligibility` as `unknown`, with reason `tokenRules`, while `simulation` is `skipped`. Fund the wallet with `MUSDC` and land the approval, then build again: the swap is simulated, and before `setKYC(true)` the simulation reverts. The wallet admits itself with:

   ```bash theme={null}
   cast send $MWRWA "setKYC(bool)" true \
     --rpc-url $SEPOLIA_RPC_URL --private-key $PRIVATE_KEY
   ```

   Build once more: the simulation succeeds, and eligibility is `eligible` with reason `simulated`. This is how your app sees an RWA whose issuer applies its own transfer rules.

4. **Get test TSY.** Swap `MUSDC` for `TSY`. The Treasury capital provider of the pair, `0x06aa03964db1f7257357ef09714a5f0ca3633723df419e97015e0c7a3e83edb7`, mints TSY, and it mints only to a wallet that Multiliquid has whitelisted, so the swap reverts for any other wallet, and a build for such a wallet reports `checks.eligibility` as `ineligible`, with reason `notAllowlisted`. A quote without `capitalProvider` picks the capital provider with the best quote, so name the Treasury capital provider in `capitalProvider` to swap through it. Either [ask the Multiliquid team](https://www.multiliquid.xyz/) to whitelist your wallet, after which a swap through the Treasury capital provider also records Treasury credits for it, or name the pair's other capital provider, `0x0d29c0dffbd2c0c346869448228ca2a7abc53ed8b9bc71131711a7dc1b2e1dbf`, in `capitalProvider`: it pays TSY from its own holdings, and the wallet gets no credits.

Read each token's address from `GET /v1/swap/pairs?network=evm-sepolia`.

## Fund a devnet wallet

Get devnet SOL from the Solana devnet faucet. The devnet tokens, mock stablecoins and RWAs, some of them Token-2022 mints, are minted by Multiliquid, so [contact the Multiliquid team](https://www.multiliquid.xyz/) for a test balance. `GET /v1/swap/pairs?network=svm-devnet` lists them.

## What differs from mainnet

* **Tokens have no value.** Mock tokens record no issuer, so their `issuer` is `null`, and their prices come from fixed test price feeds. Sepolia's TSY records `Multiliquid` as its issuer.
* **Redemptions run on mainnet only.** There is no test environment for them.
* **Batch orders follow the same daily calendar** as mainnet, with no on-demand release.
* **The Data API's transactions and volume** cover `evm-sepolia` as well as `evm-mainnet`.

Everything else, from errors to rate limits, behaves as it does on mainnet.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.