Add Definitive Flash plugin (swaps + limit/TWAP/trigger orders, 7 chains) - #151
Open
sp6pe wants to merge 1 commit into
Open
Add Definitive Flash plugin (swaps + limit/TWAP/trigger orders, 7 chains)#151sp6pe wants to merge 1 commit into
sp6pe wants to merge 1 commit into
Conversation
Adds skills/base-mcp/plugins/flash.md: swaps and advanced orders (limit, TWAP, stop, take-profit, bracket) on Definitive Flash via HTTP API -> send_calls (funding txs) + sign (EIP-712 order payloads), with gasless MEV-protected execution across 7 Base MCP chains. Also appends the net-new 'cross-chain' tag to the vocabulary list in plugin-spec.md, per Contribution Scope. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Description
Adds a Base MCP plugin for Definitive Flash (https://flash.definitive.fi/docs) — a trading API routing across 200+ liquidity sources with market, limit, TWAP, stop/stop-loss/take-profit, and bracket orders, plus cross-chain settlement.
Integration shape (
http-api, closest precedent: o1.exchange):POST /quotereturns pricing plus funding payloads (wrap tx, ERC-20 approve calldata) and EIP-712 typed data{to, value, data}viasend_callssign(eth_signTypedData_v4); cancel/update usepersonal_signover canonical messages/order; Flash handles gas, simulation, MEV protection, and onchain landing (execution is gasless for the user)The diff adds
skills/base-mcp/plugins/flash.mdand appends the net-newcross-chaintag to the vocabulary list inplugin-spec.md, per Contribution Scope.Allowlist request: please add
flash.definitive.fito theweb_requestallowlist so chat-only surfaces (Claude.ai / ChatGPT) can reach the POST endpoints. Until then the plugin is fully functional on harness surfaces (Claude Code, Cursor, Codex), and## Surface Routingstops cleanly on chat-only surfaces.Verification done while authoring (read-only, against the live API with the public dev key):
GET /search,GET /balances/{address},GET /orders— response shapes match the docPOST /quotewith and withoutfunderAddress— confirmedapproveTx/permitTypedData/orderTypedDatapayloads, and the documenteddomain.chainId-as-string quirk@definitive-fi/flash-mcp) and the OpenAPI spec (https://flash.definitive.fi/v1/openapi.json)Type of change
Affected skill(s)
base-mcp
Plugin checklist
Base MCP Plugin Submission Agreement (when applicable)
By checking the box below, I agree and represent on behalf of the protocol/entity it references that:
I am authorized to submit this plugin on behalf of the protocol/entity it references;
the plugin does not infringe or misappropriate any third party's rights;
the plugin and the underlying protocol comply with all applicable laws, and my API enforces the same geofencing and eligibility restrictions as my own user-facing app;
the plugin is in full compliance with our protocol's/entity's then-current terms and conditions, and if not, submission and use thereafter is considered a formal written exemption to such terms and conditions;
the plugin accurately describes its behavior and contains no hidden, deceptive, or malicious instructions, and my API will not return malicious or unexpected calldata;
the protocol/entity is solely responsible for the plugin and is submitting a plugin is subject to the Base Account and Base App Terms of Service as using a "Service"; and
Base may modify, decline to list, or remove the plugin at any time, for any reason.
I have read and agree to the Base MCP Plugin Submission Agreement above.
Related issues
N/A — submitted by Definitive (the protocol team behind Flash).