Integrate once. Prove every action.

Bot quickstart

1. Install the SDK with npm install @svs/solana.
2. Scaffold a new agent with npm create svs-agent my-agent.
3. Run preflight, doctor, and certified submit through the generated project.
4. Ask the operator for the current handoff, registry profile, and production proof status.

Protocol gate

Protocols should accept an agent only when the hosted registry verifies, the trust manifest hash matches, the agent profile is current, and the action proof shows signed bot request, human approval, broadcast, custom registry write, and action-record verification.

import { requireHostedVerifiedAgentRegistry } from "@svs/solana/protocol";

await requireHostedVerifiedAgentRegistry({
  registryUrl,
  expectedRegistryHash,
  botId,
  requireHighTrustScore: true
});

Verified Agent Standard

The public standard gives the market common language for verified Solana agents. A valid SVS proof requires current approval-domain evidence, request signing, nonce protection, policy outcome, human wallet approval, on-chain registry proof, and portable auditor evidence.

Verifier workflow

An auditor imports a signed verification set, then independently checks signer trust, release readiness, action-record proof, receipt registry submission, browser export evidence, and cache-busted verifier evidence.

Security posture

SVS treats copied badges, stale proofs, unsigned bot requests, replayed nonces, missing registry anchors, and mismatched approval domains as failure states. Public docs should show these warnings before broad launch.

Publish boundary

The public layer is packages, docs, registry pages, verifier demos, and protocol examples. The private operator dashboard, admin controls, release tooling, evidence directories, and secret material stay private.