Skip to main content

At a glance

MainnetDevnet
Network ID (CAIP-2)solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpsolana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1
Native assetSOLSOL
Native decimals99
StablecoinUSDC SPLUSDC SPL
Stablecoin mintEPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v(devnet equivalent)
Stablecoin decimals66
Confirmation timeSub-second to 1 secondSub-second
Typical fee$0.00025Free (devnet airdrop)

Solana Pay reference binding

Solana doesn’t support arbitrary memos in the way Algorand or Hedera do. Instead, AlgoVoi uses Solana Pay’s reference mechanism: a fresh ed25519 public key generated per checkout, included as a non-signer account in the settlement transaction. For each Solana checkout:
  1. AlgoVoi generates a new ed25519 keypair. Only the public key is stored in the database.
  2. The Solana Pay URL on the checkout page includes ?reference=<pubkey> alongside amount and spl-token.
  3. The wallet builds a transaction that includes that pubkey as a non-signer account.
  4. The verifier looks up the settling tx via getSignaturesForAddress(reference) against a managed RPC.
  5. The match is cryptographic: no other transaction can satisfy this checkout, even if it sends the right amount to the right address.
This is the same mechanism Solana Actions and Blinks use to bind a Blink to a specific checkout.

Associated token accounts

Like SPL tokens generally, USDC requires an associated token account (ATA) on the recipient side. AlgoVoi auto-detects whether the payout’s ATA exists and creates it as part of the first transfer if needed (paying the small rent fee, which is reimbursed from the next confirmed payment).

Wallets

See also