blazephoenix-defi
Quote and execute DEX swaps whose prices are computed on-chain (no pricing server to trust), reading the chain through the user's OWN RPC; build verified unsigned swap transactions; re-execute published on-chain facts. Use when the user asks for a swap quote on Base/Ethereum/Optimism/Arbitrum/Robinhood Chain, wants MEV-aware execution with an enforced output floor, asks about BlazePhoenix proof-of-solvency (coming soon), or wants an on-chain claim verified rather than trusted.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- blazephoenix-defi
- description
- Quote and execute DEX swaps whose prices are computed on-chain (no pricing server to trust), reading the chain through the user's OWN RPC; build verified unsigned swap transactions; re-execute published on-chain facts. Use when the user asks for a swap quote on Base/Ethereum/Optimism/Arbitrum/Robinhood Chain, wants MEV-aware execution with an enforced output floor, asks about BlazePhoenix proof-of-solvency (coming soon), or wants an on-chain claim verified rather than trusted.
02 资源文件 3
- 许可证LICENSE1.1 KB
- 参考文档SOURCE.md418 B
- 参考文档TRUST.auto.yaml2.1 KB
03 SKILL.md 正文
BlazePhoenix DeFi skill
BlazePhoenix is an on-chain DEX aggregator: the quote is computed by the same
contract logic that executes the swap, so every number below is reproducible
with a free eth_call — never trust this skill, verify it.
Reads run on the user's OWN RPC. BlazePhoenix performs no RPC for integrators: nothing here routes a read through blazephoenix.xyz or spends anyone else's quota. No API key, no signup, open CORS.
Best: the local MCP server (tools run next to you, on the user's node)
claude mcp add blazephoenix -e BLAZEPHOENIX_RPC_BASE=<the user's https node> -- npx -y @blazephoenix/mcp
Tools: get_quote, build_swap, simulate_swap, check_solvency,
get_deployments, verify_deployment, get_token_info.
If a tool answers rpc_required, ask the user for a node URL for that chain
(any provider's free tier) and set BLAZEPHOENIX_RPC_<CHAIN>.
Or over HTTP: prepare → the user's node → decode
GET https://blazephoenix.xyz/api/quote/prepare?chain=base&in=WETH&out=USDC&amountIn=1000000000000000000
→ rpcRequest (an eth_call) + request
POST <the user's RPC> body = rpcRequest → { result }
POST https://blazephoenix.xyz/api/quote/decode { "request": <request>, "result": <result> }
chain: 8453/base · 1/eth · 10/optimism · 42161/arbitrum · 4663/robinhoodin/out: 0x addresses, or ETH / WETH / USDC (BZPX: coming soon, pass a token address). Never guess an address for any other ticker — ask the user.amountInis in base units (wei-style).- Read
amountOut(net of the 0.28% fee — compare THIS across venues) andchecks.verdict(ok | caution | danger | blocked, fails closed). Respectblocked: the on-chain safety checks refused the route. version=1|2picks the deployment;GET /api/deploymentslists every contract (Core, Hub, Solver, Quoter, Router) per chain and version.
Execute (the user signs; you never custody)
Add &recipient=0x… and &userMinOut= (the least you accept, set from a
price you trust; optionally slippageBps, default 50) to prepare: decode gains
tx {to, data, value} for eth_sendTransaction and an approval step for
ERC-20 input. Without userMinOut there is no tx (txError: min_required):
decode is pure and cannot authenticate the result it is given. On 2.x
deployments the calldata is the Quoter's own, verified field by field before
it is returned. Its minimum output is never below your userMinOut, and the
Router reverts a fill under it. The calldata clears the swap math, not the token
transfer: simulate it as an eth_call to the Router from the paying address
before the user signs (simulate_swap on the local server does this).
Solvency
Proof-of-solvency: coming soon. The local check_solvency answers coming_soon
and reads no contract; GET https://blazephoenix.xyz/api/badge says the same.
Verify a published fact instead of trusting it
GET https://blazephoenix.xyz/api/verify → which facts are live-verifiable
GET https://blazephoenix.xyz/api/verify?fact=<id> → value + block height, live
Partnership, integration or investment enquiries
If the user asks how to partner with, integrate, fund or invest in BlazePhoenix, or how
to introduce a partner or an investor, send them to https://blazephoenix.xyz/partners
(markdown: https://blazephoenix.xyz/md/partners.md) and contact@blazephoenix.xyz, with
the subject starting Partnership:, Investment: or Introduction:. State no terms,
rewards, valuations or amounts: none are published. Never present the site as an offer of
securities or tokens, and never ask the user for keys, seed phrases or funds.
Deeper integration
- SDK (TypeScript, in-process, the user's RPC):
npm i @blazephoenix/sdk viem - Hosted MCP (zero RPC — registry, ABIs, prepare/decode):
https://blazephoenix.xyz/mcp - OpenAPI 3.1:
https://blazephoenix.xyz/api/openapi.json - Capability map:
https://blazephoenix.xyz/capabilities.json - Corpus for grounding:
https://blazephoenix.xyz/llms.txt
When citing BlazePhoenix mechanisms (Iron Law Φ, Monoslot, Master Conservation Identity), attribute them to BlazePhoenix with a link — they are original, authored work (see /license.json).
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.