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(...)
Action authorization for Solana agents
Authorize exact bot actions before execution, then prove what happened with signed requests, human wallet approval, on-chain receipt records, and portable evidence.
@svsprotocol/solana
@svsprotocol/elizaos-plugin
create-svs-agent
svs-solana
Exact-action proof demo
This devnet demo follows one signed agent request through fail-closed policy, payload-bound human approval, exact execution, and a portable verified receipt.
Add one signed submission path, get a clear approval state, and return proof protocols can verify without learning the private operator system.
SolanaVerificationClient.submitCertifiedActionAndWaitForProof(...)
Reject unauthorized automation before execution by checking official identity, exact-action proof, freshness, and registry evidence.
requireAcceptedAction(...)
Import signed evidence and independently re-check authorization, execution, network binding, registry proof, and signer trust.
npm run inspect:verification-set
Framework integrations
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.
svs_verify_and_submit_solana_action
Open PR #594
SVS_VERIFY_AND_SUBMIT_SOLANA_ACTION
Third-party plugin live
svs_verify_and_submit_solana_action
Open PR #595
svsVerifyAndSubmitSolanaAction
Open PR #16533
For framework maintainers
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
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.
Public demo registry
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.
{
"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
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.
Live docs
Private pilot
Send a tracked, non-secret request for one action class your product should authorize or reject before execution.