Skip to main content

​
At a glance

​
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

​
xChain — pay from MetaMask, settle on Solana

Tenants on solana_mainnet automatically get the xChain tab on every hosted checkout. A customer holding USDC on any of seven EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB, Avalanche) can pay the Solana checkout from MetaMask without installing Phantom or any other Solana wallet. Default routing: Circle CCTP V2 Fast Transfer. End-to-end ~50-90s (~30s source-tx confirmation + ~30s Iris attestation + ~5-10s relayer claim). Zero pool slippage — the customer pays the bridge amount and the merchant receives it minus only Circle’s small Fast Transfer fee (capped at 14 bps), absorbed by AlgoVoi’s slippage tolerance. Allbridge Core is available as a fallback for any source chain CCTP doesn’t support (e.g. BNB Chain) — ~90-120s, ~0.3% combined pool fee. The merchant sees a normal Solana payment land at their payout wallet; the AlgoVoi facilitator’s standard SolanaVerifier confirms the destination transaction the same way it confirms direct Solana Pay payments. No extra integration work for the merchant. See xChain payments for the full flow + bridge-source list.

​
Agent-to-agent settlement on Solana

Solana confirms in well under a second, so an agent-to-agent payment and its proof land almost immediately. The mesh writes its execution_ref into a memo on the settlement transaction. AlgoVoi Mesh settles a payment directly between two autonomous agents on Solana. Each agent verifies the other offline with a Falcon-1024 credential, the pair negotiates Solana as the settlement chain, and the authorized decision is anchored in a memo as one content-addressed execution_ref. There is no facilitator, no per-transaction fee, and no AlgoVoi service in the trust path at settlement time. Proven on-chain. A mutually verified Falcon-1024 pair negotiated Solana and settled once: Open it and read the memo. It carries algovoi-mesh:sha256:000e1936..., the exact execution reference that run’s handshake produced. Recompute it yourself from the raw fields with a stock RFC 8785 (JCS) implementation and SHA-256; no AlgoVoi software is involved in checking it. The chain never verifies Falcon. It only carries the anchor, which is why the same agent trust works on Solana and on every other chain the pair could have chosen. See AlgoVoi Mesh for the mutual handshake, the signed chain-offer negotiation, and the full eight-chain proof.

​
See also