docs(skills): say which tools do not exist on Solana, and where - #98
Merged
Conversation
#97 established that the two gateways disagree and guarded the two affected tools in code, but the skills still described one catalog. An agent that ran blockrun_wallet action:"chain" chain:"solana" earlier in the session had no written way to know that two of the twenty tools stopped existing. Probed against both gateways 2026-08-07: - /v1/defillama/* is absent on sol.blockrun.ai — 404, which reads like a bad path, so the natural next move is to re-check the path rather than the chain. - /v1/modal/* is present but unconfigured there — 503 on all four sandbox actions. That reads like an outage, which invites retrying against a backend that was never going to answer. Both now say so where the tool is documented (crypto-data's defi section, the modal skill's opening) rather than only in the core skill, because that is where an agent is looking when it needs the answer. The core skill grows a short section on what action:"chain" actually changes — it repoints every paid call at a different deployment — with the coverage table and both llms.txt URLs, since each gateway's catalog quotes its own pricing convention. rules/wallet-and-payment.md carries the mechanics: why the budget gate reserves the Base figure on both chains (over-reserving on Solana is the safe direction) and that verify-prices fails the build if Solana ever becomes the dearer one.
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.
Follow-up to #97. That PR proved the two gateways disagree and guarded the two affected tools in code; the skills still described one catalog.
An agent that ran
blockrun_wallet action:"chain" chain:"solana"earlier in the session had no written way to know that two of the twenty tools had stopped existing.What is actually missing on Solana
Probed against both gateways 2026-08-07:
sol.blockrun.ai/v1/defillama/*404/v1/modal/*503on all four sandbox actionsEverything else works on both, about $0.001 cheaper on Solana.
Where it now says so
crypto-data(defi section) andmodal(opening) — at the point of use, because that is where an agent is looking when it needs the answer, not in a chain appendix.skills/blockrun— a short section on whataction:"chain"actually changes: it repoints every paid call at a different deployment. Carries the coverage table and bothllms.txtURLs, since each gateway's catalog quotes its own pricing convention.rules/wallet-and-payment.md— the mechanics: the budget gate reserves the Base figure on both chains, which over-reserves on Solana (the safe direction — it can refuse an affordable call but never let one past the cap), andverify-pricesfails the build if Solana ever becomes the dearer one.Related, not in this PR
sol.blockrun.ai/llms.txtadvertises Modal sandbox compute in two places plus its header line, with prices, while the deployment answers503for it. It correctly dropsdefillama, so the file is chain-aware — Modal is the one thing that was not pruned when it was not configured. That lives inblockrun-sol, and the fix is a product call: configure Modal there, or stop advertising it until it is. Flagged, not decided.Verification
npm run typecheck, 302/302 tests,sync-brand-numbers --checkall green.