Wallet

Sends without gas

Send USDC and USDT from your own Solana address, and USDC on Ethereum, Base and Arbitrum, without holding SOL or ETH. The fee comes out of the stablecoin.

A stablecoin on Solana or an EVM chain normally can't move unless its wallet also holds that chain's coin for gas. People who only want dollars end up stuck with dollars they can't send. The USD.NET wallet removes that step: USD.NET pays the gas, and you pay a small fee in the stablecoin you are sending.

Your funds stay at your own address the whole time. You sign every send on your device. USD.NET only adds its signature as the payer of the network fee.

Where it works

NetworkTokensGas paid by USD.NET inHow
SolanaUSDC, USDTSOLA separate fee payer on the transaction
EthereumUSDCETHEIP-3009 authorizations, relayed
BaseUSDCETHEIP-3009 authorizations, relayed
ArbitrumUSDCETHEIP-3009 authorizations, relayed

On the EVM chains you can still pay the fee in ETH yourself: under Pay the network fee in, choose ETH.

The fee

The fee is what the send costs USD.NET in gas, plus 30%, at least 0.01 and rounded up to the next cent. It is shown before you sign and is part of what you sign, so it can't change afterwards.

Typical fees, quoted live on 3 November 2026:

SendFee
Solana, recipient already holds the token0.01
Solana, recipient's first time holding the token0.19 (includes opening their token account, about 0.0015 SOL)
Base0.01
Arbitrum0.02
Ethereum0.03, following Ethereum's gas price at the time

If the send fails, nothing is charged.

How it works on Solana

  1. 1

    Quote

    The wallet asks for a quote. The server checks your balance, whether the recipient already has a token account, and the current blockhash. It returns the exact transaction parameters with its own signature over them.

  2. 2

    Build and check

    The wallet builds the transaction from those parameters with the same code the server uses. It refuses to continue unless the recipient, the token and the amount are exactly what you entered.

  3. 3

    Sign

    You sign as the owner of your token account. The transaction has two signers. USD.NET is the fee payer. You sign the two transfers: the amount to the recipient, and the fee to USD.NET.

  4. 4

    Co-sign and send

    The server rebuilds the transaction from the signed parameters and checks that your signature covers exactly those bytes. It adds its signature as fee payer and simulates the transaction on Solana. It broadcasts only if the simulation succeeds.

The fee payer can't move your tokens. Only the owner's signature can, and the owner's signature covers the whole transaction.

How it works on Ethereum, Base and Arbitrum

USDC supports EIP-3009 transferWithAuthorization: the owner signs a typed message authorizing a specific transfer, and anyone can submit it.

  1. 1

    Quote

    The server quotes the fee and picks two random one-time nonces, valid for 15 minutes.

  2. 2

    Sign two authorizations

    You sign two EIP-712 messages: one sending the amount to the recipient, one sending the fee to the USD.NET relayer. Each names the exact recipient and amount and can be used once.

  3. 3

    Relay

    The relayer checks both signatures and simulates the transaction. It then submits both authorizations in one Multicall3 transaction, with neither allowed to fail on its own, and pays the gas.

The relayer can only submit what you signed. Changing the amount or the recipient makes USDC reject the signature.

What you trust

  • USD.NET can't move more than you signed, send it somewhere else or reuse a signature.
  • USD.NET can decline to relay, for example while a relayer is being topped up. Your funds stay where they are, and you can always send them with your own SOL or ETH using the recovery phrase in any standard wallet.

API

The wallet calls these endpoints on usd.net. They are public, but every send needs the owner's signature.

MethodPathBody
POST/api/relay/solana/quote{ from, to, mint, amount } (amount in token units)
POST/api/relay/solana/send{ params, token, sig } (owner signature, base64)
POST/api/relay/evm/quote{ chain, from, to, amount } with chain eth, base or arb
POST/api/relay/evm/send{ params, token, sigs }
GET/api/relay/statusRelayer addresses and their gas balances