Add SVS verified action example#16533
Open
CryptoZaddy-dev wants to merge 1 commit into
Open
Conversation
| }, | ||
| "dependencies": { | ||
| "@svsprotocol/solana": "^0.2.0", | ||
| "ai": "^6.0.202", |
Contributor
There was a problem hiding this comment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
@svsprotocol/solanaValidation
cd examples/svs-verified-action npm install npm run validate node ./svs-verified-action.mjsThe default run is import validation only. Live submission is opt-in with
SVS_RUN_LIVE_SUBMIT=trueand requires a prepared serialized transaction inSVS_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.