feat: add Solana fixed-yield brief plugin#122
Draft
sheawinkler wants to merge 4 commits 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
Adds
solana-fixed-yield-brief, a T0/read-onlywasm32-wasip2tool pluginthat:
BASE_TO_PTquotes with a non-weakenable 5.50%staking hurdle and explicit cost allowance;
result;
base-token leg, and non-approval risk labels.
The plugin accepts no wallet, key, transaction, config, filesystem access, or
caller-controlled URL. Its only manifest permission is
http_client.Why
An APY headline is not an executable wallet return. Exponent's
BASE_TO_PTamount is normalized-SOL accounting notional; an LST-backed market can require
its underlying base token rather than native SOL. The plugin therefore exposes
that acquisition/redemption gap and never presents a quote as a funded trade or
execution approval.
Safety and integrity
venue lists, routes, quote fan-out, and output;
parsing, duplicate-identity rejection, and pre/post-I/O clock checks;
one-for-one atomic-scale assumption;
partial coverage fail closed or remain explicitly
UNPROVEN;action/recipient/amount/privateKeytool fields arerejected before clock or network access;
log-record; no stdout from thecomponent.
Authoritative local verification
Committed snapshot:
af5c036c32d650509832e7c76a7a5f7a9c9c4ed4The repository's strict clean-snapshot validator independently passed tests,
native Clippy, WASI Clippy, release build, source-mutation detection, and
component staging:
Real ZeroClaw host execution
A fresh release harness built against ZeroClaw commit
f0b92f1516ec86aeb89ab2d8f25b837e14885aaeloaded the final component throughthe actual
PluginHost/Wasmtime bridge. The four relevant WIT files werebyte-identical.
bf051d8265ca4011815cedba98c699bf523e362e5957ec4b0d838e31dce1e803solana-fixed-yield-brief v0.1.0withpermissions=[HttpClient];success=true, 3/3 attemptedcoherent quotes across 4 eligible markets, one best candidate, and explicit
partial-coverage warning;
o200k_basetokens, 222cl100k_basetokens;
success=falsefor the hostile fund-move/private-key argumentset.
The component transport exposes a connect timeout but not a total/read
deadline; the verified host supplies a 30-second outer cancellation boundary.
Full reproducible evidence and the exact observed output are in
DEMO.md.Human-only bounty artifact
The real Telegram/Discord, no-slide video and Superteam submission remain
human-produced artifacts. The README and demo record provide the exact
invocation and hostile-message sequence; this PR does not misrepresent the local
host execution as channel proof.