Start

Tova Documentation

Confidential spending, revocable agent mandates, and hardware-attested HTTP 402 settlement on Solana.

What Tova does

Tova is a confidential spending, delegated authority, and atomic HTTP 402 settlement protocol on Solana. Principals deposit SOL or SPL tokens into Shielded Ring Vaults, issue revocable Shielded Mandates with per-call and epoch limits to autonomous agents, and let those agents settle paid HTTP 402 services only when a hardware-attested provider returns a signed Execution Receipt.

On-chain observers see vault addresses, commitment roots, nullifiers, and verified proofs. Vault principals and authorized auditors decrypt exact amounts, fees, and receipts off-chain with a Viewing Key.

Core objects

ObjectOn-chain accountPurpose
Shielded Ring VaultRingVaultHolds escrowed SOL or SPL balances behind encrypted UTXO commitments and a Merkle root
Shielded MandateMandateDelegates bounded spend (per-call ceiling, epoch budget, epoch duration, expiry) to an agent signing key
Attested ProviderProviderRegistryBinds a provider's Intel TDX, AMD SEV-SNP, or localnet attestation key to its Capacity Stake
Atomic 402 EscrowSettlementEscrowLocks a shielded commitment until a signed TEE Execution Receipt claims it or the deadline slot passes
Nullifier RecordNullifierRecordRecords each spent note nullifier in a unique PDA to prevent double-spend
Protocol ConfigProtocolConfigStores protocol authority, fee_recipient, configurable fee_bps (default 25 bps), and global counters

Canonical addresses and defaults

ParameterValue
Anchor program (tova_core)C5K5LF7CGN5zKf7mxHxy5PYQHnvzHEui7dtkLZ1ytmb9
ProtocolConfig PDAFXsYi3agEshdEbiA499isr6tvU5abgEdnjNepZ2gNCTu
Fee recipient (fee_recipient)CMR92vY5iHC1o6pVCrpSpK1qrye4yQdWPkp4fukeUrbC
Default protocol fee (fee_bps)25 (0.25% on claim_settlement, rounded down)
Groth16 proof envelope192 bytes
Measured open_settlement compute38,631 CU on localnet (~155,000 CU target with full BN254 verifier)
Measured claim_settlement compute31,967 CU on localnet (~65,000 CU target)
TypeScript SDK package@tova/sdk (TovaClient, pay402, gate402)
CLI binarytova (@tova/cli)

Details on TOVA token supply, fee routing, and buyback-and-burn status live on Protocol.

Choose your path

RoleFirst stepReference
Vault principal or treasury operatorCreate a Ring Vault, then Issue an Agent MandateAnchor Program
Agent developer5-Minute Quickstart, then Pay an HTTP 402 Endpoint@tova/sdk
Inference or data providerRegister a TEE ProviderREST API
Auditor or compliance reviewerViewing Keys & Disclosuretova CLI

Quick integration

ts
import { TovaClient } from '@tova/sdk'

const tova = new TovaClient({
  apiUrl: 'http://127.0.0.1:37402',
})

const result = await tova.pay402<{ output: string; responseHash: string }>(
  'http://127.0.0.1:37402/api/demo-provider/infer',
  {
    agent: process.env.TOVA_AGENT_PUBKEY!,
    vault: process.env.TOVA_VAULT_PDA!,
    mandate: process.env.TOVA_MANDATE_PDA!,
    body: { prompt: 'Verify shielded HTTP 402 receipt' },
  },
)

console.log(result.settlementId, result.teeVerified, result.data.output)

Upcoming protocol builds

Tova's roadmap after this first build covers four areas:

  1. Cross-provider reputation and dynamic trust capacity on ProviderRegistry with trust-ranked routing in pay402.
  2. Multi-hop agent sub-delegation through bounded SubMandate accounts with single-transaction root revocation.
  3. NVIDIA confidential GPU attestation and shielded streaming compute channels for per-token inference settlement.
  4. Helius Custom Compliance Rings, organizational policy trees, and multi-auditor scoped viewing keys.

Next steps

  1. Run your first shielded HTTP 402 settlement in 5-Minute Quickstart.
  2. Read how the four cryptographic primitives fit together in Ring Vaults or on Architecture.
  3. Test the live consoles on Vaults, Settle, and Providers.