feat: add read-only Solana analysis plugins - #141
Open
taharfi wants to merge 7 commits into
Open
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
1 participant
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 three read-only Solana analysis plugins:
wallet-narrate: bounded, redacted activity summaries with success/failure handling.stake-monitor: delegation and activation health reporting.token-risk-check: deterministic mint-authority, freeze-authority, holder-concentration, liquidity, and metadata risk flags.All plugins use the vendored ZeroClaw WIT contract, standalone Cargo workspaces, pure Rust cores, thin WASM shims, bounded inputs, and no custody/signing/transfer capability.
Validation
wasm32-wasip2release builds pass for all three plugins.token-risk-checkis markedregistry = falsebecause live HTTP imports are host-gated.Safety
No private keys, signing, transfers, swaps, or arbitrary RPC methods are accepted. Signatures are redacted and provider data is bounded.
Notes
Telegram live results and injection-refusal evidence were captured locally. The two registry-ready plugins are pending the generated registry/publish workflow.