Action authorization for Solana agents

SVS: Solana Verification System

Authorize exact bot actions before execution, then prove what happened with signed requests, human wallet approval, on-chain receipt records, and portable evidence.

Public packages live @svsprotocol/solana @svsprotocol/elizaos-plugin create-svs-agent svs-solana
HMAC signed bot request Wallet human approval PDA receipt registry proof
SVS proof flow showing bot request, human approval, on-chain receipt, and auditor proof package

Exact-action proof demo

See SVS authorize the exact action before execution

This devnet demo follows one signed agent request through fail-closed policy, payload-bound human approval, exact execution, and a portable verified receipt.

Signed request Fail-closed policy Payload-bound approval Verified receipt
01

For bot builders

Add one signed submission path, get a clear approval state, and return proof protocols can verify without learning the private operator system.

SolanaVerificationClient.submitCertifiedActionAndWaitForProof(...)
02

For protocols

Reject unauthorized automation before execution by checking official identity, exact-action proof, freshness, and registry evidence.

requireAcceptedAction(...)
03

For auditors

Import signed evidence and independently re-check authorization, execution, network binding, registry proof, and signer trust.

npm run inspect:verification-set

Framework integrations

Four adapter surfaces for agent teams

SVS has public packages, copyable examples, and host-app validation for the ecosystems where Solana agent builders already start. Three upstream example PRs are open, and ElizaOS is moving through an SVS-owned third-party plugin path after maintainer fit feedback.

Solana Agent Kit @svsprotocol/solana/solana-agent-kit svs_verify_and_submit_solana_action Open PR #594
GOAT @svsprotocol/solana/goat svs_verify_and_submit_solana_action Open PR #595
Vercel AI SDK @svsprotocol/solana/vercel-ai svsVerifyAndSubmitSolanaAction Open PR #16533

For framework maintainers

Small reviewable examples, not core rewrites

Each package uses public dependencies, placeholder env values, copied-file hashes, and a maintainer handoff. Open PRs are examples only and avoid private operator internals.

Public standard

Verified Agent Standard for action authorization

SVS gives agent teams and protocols shared acceptance rules for who proposed an action, what was authorized, who approved it, what executed, and which evidence is fresh.

Signed request freshness Nonce replay protection Human approval payload binding Custom receipt registry confirmation Portable verification set Fake-badge and stale-proof warnings

Public demo registry

Four proof-backed demo agents people can inspect and protocols can pin

The public registry exposes sanitized demo/devnet profiles, badge states, a trust manifest, and verification APIs while keeping private operator controls and internal source IDs out of the public surface.

4 verified demo agents 100/100 high-trust score each 0 credential cleanup debt 5 host validations per agent devnet demo network f037...1d08 registry hash 4 official devnet identities

SVS Demo Devnet Agent

Bot ID
svs-demo-devnet-agent
Status
SVS Demo Verified
Network
devnet demo
Profile hash
d2bb...caf0
Credential lifecycle current Host validation: 5 targets

SVS Trading Agent Demo

Bot ID
svs-trading-devnet-agent
Status
SVS Demo Verified
Network
devnet demo
Profile hash
b887...7757
Credential lifecycle current Host validation: 5 targets

SVS Payment Agent Demo

Bot ID
svs-payment-devnet-agent
Status
SVS Demo Verified
Network
devnet demo
Profile hash
a991...a5f2
Credential lifecycle current Host validation: 5 targets

SVS Treasury Agent Demo

Bot ID
svs-treasury-devnet-agent
Status
SVS Demo Verified
Network
devnet demo
Profile hash
cd2e...abb1
Credential lifecycle current Host validation: 5 targets
{
  "registryUrl": "https://registry.svsprotocol.com/registry.json",
  "trustManifest": "/trust-manifest.json",
  "agentCount": 4,
  "verify": "/api/v1/agents/{botId}/verify",
  "badge": "/agents/{botId}/badge.svg",
  "network": "devnet"
}

Verifier demo

Paste a proof summary and run local checks

This lightweight public demo mirrors the auditor workflow: it checks the presence of a verification set, registry hash, action proof status, and signer trust summary. The full standalone verifier remains the production proof tool.

Verifier docs

    Live docs

    Start where your role needs proof

    Private pilot

    Bring SVS to a protocol, marketplace, wallet, or bot platform

    Send a tracked, non-secret request for one action class your product should authorize or reject before execution.

    Stored privately in SVS intake. Page analytics are anonymous and receive no form fields.