Add YO Protocol native plugin (on-chain)#81
Open
AndonMitev wants to merge 1 commit into
Open
Conversation
Adds skills/base-mcp/plugins/yo.md and registers it in the base-mcp SKILL.md plugin table. YO Protocol is an ERC-4626 yield aggregator with ERC-7540 async redemption on Base, Ethereum, and Arbitrum. The plugin covers four operations — getVaults, yoPositions, deposit, withdraw — entirely on-chain: reads via chain_rpc_request, unsigned calldata via send_calls. No external API, no allowlist, no CLI.
Collaborator
🟡 Heimdall Review Status
|
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
2 participants
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
skills/base-mcp/plugins/yo.md— a native Base MCP plugin for YO Protocol — and registers it in thebase-mcpSKILL.mdplugin table.Submitted in response to Base's invitation to author a native plugin per the plugin spec. (Noting the current
CONTRIBUTING.mdline about core-team-only contributions — happy to adjust if the process differs.)About YO
YO Protocol is an ERC-4626 yield aggregator with ERC-7540-style async redemption, live on Base, Ethereum, and Arbitrum. Both deposit and withdraw route through the YO Gateway (
0xF1EeE0957267b1A474323Ff9CfF7719E964969FA, same address on every chain).Scope — four operations, fully on-chain
getVaultstotalAssets/totalSupplyyoPositionsbalanceOf→convertToAssets→pendingRedeemRequest, aggregated by (vault id + underlying) across chainsdepositapprove(underlying→Gateway)+Gateway.depositwithdrawapprove(shares→Gateway)+Gateway.redeemintegration: semantic-base-tool. Reads go throughchain_rpc_request; writes are unsigned calldata tosend_calls. No external service — no API host to allowlist, no CLI, no MCP dependency — so it works on every surface from day one. (APY/yield and cross-chain zaps aren't on-chain-derivable and are intentionally out of scope.)A note on
integrationsemantic-base-toolis the only "no external service" value, but it nominally describes composingswap/sendrather than building raw calldata. This plugin builds raw calldata forsend_callswith no external service in the path — I've stated that plainly in Overview/Submission. Happy to relabel if you'd prefer a different classification for a pure-on-chain, calldata-building plugin.Verification
viem.deposit/redeemsignatures + param order checked against YO's canonical ABI.0x942a1f717627f5b794f18e8f4e6c630a5877c598faa4d795c87ebeaafa05a74d) + instant redeem (0xdcda0814759eba5f6f699c68c2c1fbf07a3c99339cfbcd5c089c0f142450f4e4), both confirmed.Authoring checklist
## Submissionnamessend_callswith the exact mapping## Risks & Warnings(slippage, irreversible)SKILL.mdplugin table