Test bridges

Tidepool can swap between NEAR testnet and three EVM testnets (below), plus Solana devnet, Stellar testnet, Sui testnet, Bitcoin testnet4 and XRP Ledger testnet (after the table), with the same API shape as 1Click mainnet cross-chain swaps:

Solana devnet is also available as a separate, same-style bridge (SOL capped at 0.005 SOL): Solana devnet bridge. It is devnet only and custodial, and is listed in /v0/tokens only while it is live.

Stellar testnet is another separate bridge (XLM capped at 100 XLM, deposits use depositMode: "MEMO"): Stellar testnet bridge. It is testnet only, custodial and listed in /v0/tokens only while it is live.

Sui testnet is another separate bridge (SUI capped at 10 SUI, per-quote deposit addresses, no memo): Sui testnet bridge. It is testnet only, custodial and listed in /v0/tokens only while it is live.

Bitcoin testnet4 (native tBTC capped at 0.005 BTC, native segwit tb1q… per-quote deposit addresses, no memo): Bitcoin testnet4 bridge. It is native-coin only (no stablecoins), custodial, testnet only and listed in /v0/tokens only while live. The faucet never drips BTC: get tBTC from the external faucets linked in the guide.

XRP Ledger testnet (native XRP capped at 100 XRP, deposits use depositMode: "MEMO" with the numeric depositMemo as the Payment's destination tag): XRP Ledger testnet bridge. It is native-coin only (no issued tokens, like 1Click), custodial, testnet only and listed in /v0/tokens only while live. The faucet never drips XRP: use the official XRPL testnet faucet linked in the guide.

What matches 1Click (EVM chains)

• Asset ids. Bridged tokens look like 1Click's omft ids: nep141:<chain>-<erc20 address>.tp-omft.testnet. /v0/tokens lists them with blockchain and contractAddress.
• Deposit addresses. A live quote with an EVM originAsset and depositType: "ORIGIN_CHAIN" returns a unique 0x deposit address. You send the ERC-20 with a plain transfer.
• Addresses. refundTo and recipient must be 0x addresses for EVM legs, and NEAR accounts for NEAR legs.
• Status and refunds. The same lifecycle and refund reasons. EVM transactions are listed in originChainTxHashes / destinationChainTxHashes with explorer links.

How the EVM bridges work

The Solana, Stellar, Sui, Bitcoin and XRP Ledger bridges follow the same idea (relayer detects the deposit, mints the matching NEP-141 into the verifier, and pays out on the destination chain) but have their own deposit mechanics; see their route guides.

1. Deposit. Each quote's deposit address is a CREATE2 address of the chain's TidepoolVault (salt = keccak256("tidepool-deposit:" + correlationId)). Nothing is deployed there until funds arrive.
2. Sweep. The relayer calls vault.sweep(salt, token). This deploys a tiny forwarder at the deposit address that sends the tokens to the vault and self-destructs in the same transaction.
3. Credit. The relayer mints the matching NEP-141 on NEAR and credits it into the verifier with a normal ft_transfer_call, to the quote's intents account. The swap settles with execute_intents, as on NEAR-only routes.
4. Payout. For an EVM destination (or an EVM refund), the verifier ft_withdraws the bridged token to the relayer with memo WITHDRAW_TO:0x…. The relayer then calls vault.release(id, token, to, amount). id is derived from the quote, and the vault refuses to release the same id twice.

What you trust

• The relayer key. On the EVM chains, one key (0x55F2c8044D790e1b8369508c31c756c0c2Ca0E93) can sweep deposits and release any vault balance. If it is lost or misused, bridged balances are gone. There are no light clients, proofs or multisigs.
• Minting. Bridged NEP-141s are minted by the Tidepool root account. Supply on NEAR is not enforced against vault balances on-chain.
• Liveness. If the relayer is down, deposits wait in their deposit addresses and payouts wait as PROCESSING. Both resume when it restarts.
• Testnet RPCs. The relayer uses public RPCs. Congestion or reorgs can delay a swap.

Do not send mainnet assets to any of these addresses. Contracts on these chains do not accept real USDC or USDT; only the Tidepool test tokens listed in each route guide are credited.

Gas and faucets

POST /v0/faucet with {"chain":"base","address":"0x…"} mints test USDC and USDT on that chain. It does not send gas: get testnet ETH from each chain's public faucet. The same call works for sol, stellar and sui, and mode: "intents" with assets chain aliases credits the bridged tokens to a NEAR intents balance. Pick a chain in the dropdown on the Faucet page, or see its "How the faucet works" section.