Skip to content

Add SVS verified action example#16533

Open
CryptoZaddy-dev wants to merge 1 commit into
vercel:mainfrom
CryptoZaddy-dev:svs-verified-action-example
Open

Add SVS verified action example#16533
CryptoZaddy-dev wants to merge 1 commit into
vercel:mainfrom
CryptoZaddy-dev:svs-verified-action-example

Conversation

@CryptoZaddy-dev

Copy link
Copy Markdown

Summary

Adds a small SVS verified-action example for Vercel AI SDK under examples/svs-verified-action/.

The example shows how an agent can route a prepared Solana action through SVS before the action is trusted. SVS checks signed bot identity, production readiness, human wallet approval, registry proof, and portable verification.

The example covers:

  • installing @svsprotocol/solana
  • creating one Vercel AI SDK compatible SVS verification/submission tool
  • checking SVS production readiness before submitting an action
  • requiring a hosted SVS registry gate so protocols or wallets can reject unverified automation
  • linking public SVS docs, registry, verifier, and Verified Agent Standard

Validation

cd examples/svs-verified-action
npm install
npm run validate
node ./svs-verified-action.mjs

The default run is import validation only. Live submission is opt-in with SVS_RUN_LIVE_SUBMIT=true and requires a prepared serialized transaction in SVS_SERIALIZED_TRANSACTION_BASE64.

Public References

Safety Boundary

This example uses only public dependencies and placeholder environment values. It intentionally excludes API keys, request-signing secrets, wallet keypairs, local evidence, private dashboard source, admin endpoints, and private operator artifacts.

},
"dependencies": {
"@svsprotocol/solana": "^0.2.0",
"ai": "^6.0.202",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The examples/svs-verified-action package declares "ai": "^6.0.202" (and "zod": "^4.4.3") as registry dependencies, so pnpm resolves ai@6 from npm instead of linking the in-repo workspace SDK (v7.0.9), meaning the example never exercises the SDK in this monorepo and pins an outdated major.

Fix on Vercel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant