菜单
Update standing fee quotes for the CROSS/moonpay warp route. Use when asked to set, update, or change fees/bps for specific chains, tokens, or directions in the MoonPay route. Also use when asked to show or read current standing quotes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Encode and decode raw Hyperlane messages to/from packed hex bytes using the CLI. Use when you need to construct a message for testing, inspect a raw message from logs or a transaction, or decode a warp transfer body.
Helper skill for using Hyperlane CLI address conversion utilities (addressToBytes32 and bytes32ToAddress) for cross-chain message formatting
A skill that allows a user to validate that a warp route deployment will be in the expected state after applying some configuration
Simulate pending Safe (multisig) governance txs for a warp route by replaying the literal calldata onto anvil forks, self-relaying any ICA messages, then running warp check against the desired registry config. Use to verify that a not-yet-signed Safe batch produces the intended warp route config before signing.
Add a new chain to an existing warp route owned by a customer. Reads a Linear ticket, adds the new chain to the deploy.yaml, builds a customer-specific strategy file for existing chains, runs warp apply, and outputs transaction files for the customer to sign via their multisig.
Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
| name | set-moonpay-standing-quotes |
| description | Update standing fee quotes for the CROSS/moonpay warp route. Use when asked to set, update, or change fees/bps for specific chains, tokens, or directions in the MoonPay route. Also use when asked to show or read current standing quotes. |
print-quotes.ts (see below)CROSS/moonpay — EVM origin chains and source token labels:
| Chain | Source tokens |
|---|---|
| arbitrum | USDC, USDT |
| base | USDC, USDT |
| bsc | USDC, USDT |
| citrea | ctUSD |
| ethereum | USDC, USDT |
| katana | USDC, USDT |
| polygon | USDC, USDT |
Destinations include all the above chains plus solanamainnet.
Targets — destination router slot labels:
DEFAULT — fallback slot covering any router with no specific overrideUSDC — per-router slot for the USDC router on the destinationUSDT — per-router slot for the USDT router on the destinationctUSD — per-router slot for the citrea routerXO — per-router slot for the solanamainnet router| Concept in request | Flag | Value |
|---|---|---|
| origin chain(s) | --origins | comma-separated names or all |
| source token(s) on origin | --source-tokens | USDC, USDT, ctUSD, or all |
| destination chain(s) | --destinations | comma-separated names or all |
| destination router target(s) | --targets | DEFAULT, USDC, USDT, or all |
| fee amount | --bps | number (e.g. 3, 5, 0.5) |
| quote lifetime | --ttl | duration with unit suffix (24h, 2d, 86400s) |
Heuristics:
--origins X--source-tokens--destinations X--targets USDT/USDC--targets DEFAULTall--ttl 24hExamples:
"update all fees from arbitrum usdc to all usdt destinations to 5bps"
→ --origins arbitrum --source-tokens USDC --destinations all --targets USDT --bps 5 --ttl 24h
"set katana to arbitrum default fee to 3bps"
→ --origins katana --source-tokens all --destinations arbitrum --targets DEFAULT --bps 3 --ttl 24h
"update all moonpay fees to 3bps"
→ --origins all --source-tokens all --destinations all --targets all --bps 3 --ttl 24h
"set ethereum USDT → base and polygon DEFAULT to 4.5bps with 7d TTL"
→ --origins ethereum --source-tokens USDT --destinations base,polygon --targets DEFAULT --bps 4.5 --ttl 7d
Ask ONE clarifying question before proceeding if any dimension is unclear:
DEFAULT only or all per-router slots tooStep 1 — Derive flags from the request.
Step 2 — Preview with --dry-run to confirm the exact lanes and current→new bps against live on-chain state (no signer/submitter keys are needed for this):
cd <monorepo-root> && pnpm tsx typescript/infra/scripts/moonpay/set-quotes.ts \
-r http://localhost:3333 \
--origins <origins> \
--source-tokens <source-tokens> \
--destinations <destinations> \
--targets <targets> \
--bps <bps> \
--ttl <duration, e.g. 24h> \
--dry-run
Find the monorepo root with git rev-parse --show-toplevel if needed. The HTTP registry (-r http://localhost:3333) provides private RPC URL overrides — start it first with /start-http-registry if it isn't running.
Step 3 — Run it for real, immediately and without asking for approval: re-run the same command with --dry-run swapped for --yes (GCP defaults are used automatically for signer/submitter keys):
cd <monorepo-root> && pnpm tsx typescript/infra/scripts/moonpay/set-quotes.ts \
-r http://localhost:3333 \
--origins <origins> \
--source-tokens <source-tokens> \
--destinations <destinations> \
--targets <targets> \
--bps <bps> \
--ttl <duration, e.g. 24h> \
--yes
Step 4 — Summarize the result in plain language, grouped by lane, before showing raw output. For each lane report old→new bps, or (unchanged, was already correct) when the current value already matched the target — plus the TTL used:
Done. Katana↔katana quotes now:
- USDC→USDC: 3bps (unchanged, was already correct)
- USDT→USDT: 3bps (unchanged, was already correct)
- USDC→USDT: 3→30bps, 7-day TTL
- USDT→USDC: 18→30bps, 7-day TTL
Then show the script's raw output below the summary so the user can verify the actual submissions. Surface any errors clearly without retrying silently.
When the user asks to see current fees or standing quotes (e.g. "show me the current moonpay fees", "what bps are we charging?"), run print-quotes.ts instead:
cd <monorepo-root> && pnpm tsx typescript/infra/scripts/moonpay/print-quotes.ts \
-r http://localhost:3333
Show the output directly. No confirmation needed — this is read-only.