feat(plugins): add Solana token risk check#127
Draft
scrumlord8 wants to merge 1 commit into
Draft
Conversation
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.
What changed
Adds
plugins/token-risk-check, a T0 read-only Solana safety preflight for ZeroClaw agents.The
token_risk_checktool accepts a mint address and returns a compact red/amber/green heuristic covering:The implementation keeps the risk parser and policy in a host-testable pure Rust module, with a thin
wasm32-wasip2WIT andwasi:httpshim.Why
Agents need an inexpensive, bounded preflight before discussing or constructing token actions. The plugin gives them a useful first-pass risk signal without adding custody, signing, transaction construction, or arbitrary URL access.
Safety
http_clientand jailedconfig_read.Validation
cargo test --locked— 10 tests passed.cargo clippy --all-targets -- -D warnings— passed.cargo build --locked --target wasm32-wasip2 --release— passed.python3 -m unittest discover -s tools/tests -p 'test_*.py'— 17 tests passed.python3 tools/build-registry.py --source-plugins plugins --check-metadata registry.json— passed.Notes
getTokenLargestAccountsreports token accounts rather than deduplicated beneficial owners, so the output explicitly labels concentration as a proxy. Indexed liquidity is optional and coverage-dependent.