Testnet only. Sei Atlantic-2, chain 1328.Not audited. Test funds only.

Concepts

The relayer

What the testnet sponsor submits, what it can see, and how it is limited.

On this page
  1. What it does
  2. What it learns, and what it can't do
  3. Limits (testnet)
  4. Gas for USDC deposits

Someone has to send each transaction and pay its gas. If you send it from your own account, your account is linked to "made a private transaction". So private transfers and claims go through a sponsor, and withdrawals through a fee-taking relayer.

What it does

Request Who pays gas Rule
Private transfer or claim (asset 0) The sponsor fee = 0, extAmount = 0, no recipient; the proof must name this relayer
Withdrawal The user, through the fee fee ≥ minimum; the proof must name this relayer
Deposit Never relayed The depositor submits it, because the depositor owns the refund

Every proof commits to the relayer's address through extDataHash. A copied proof can be submitted only by that relayer, and changing the relayer breaks the proof.

What it learns, and what it can't do

It sees your IP address, the time, the nullifiers and commitments, and for withdrawals the recipient. It can refuse or delay a request. It can't redirect funds, change outputs, or take a fee from a private transfer.

Limits (testnet)

A valid zero-value transfer can be proven from two dummy inputs, so a sponsor that pays for any valid proof can be drained. The relayer applies, in order: policy checks, a per-client rate limit (5 sponsored transfers per hour), a daily cap (200 per day and 20 SEI of gas), a check that nullifiers are unspent and the root is known, in-flight de-duplication, and an eth_call simulation so a revert never costs gas.

On Vercel these counters live in each function instance, so they are soft. The hard ceiling is the relayer account's balance, which is kept small. See the relayer API.

Gas for USDC deposits

The same account also sponsors gas for one kind of public transaction: a USDC deposit from a wallet's own Sei address when that address has no SEI. It sends just enough SEI for the approval and the deposit, once per address per day, and stops while its own balance is low. It learns that the address is about to deposit USDC, which the deposit makes public anyway.

Source: apps/web/content/docs/relayer.md