القائمة
Add message IDs to the relayer denylist. Use after investigating stuck messages with /investigate-stuck-messages, or when you have specific message IDs to denylist.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
| name | denylist-stuck-messages |
| description | Add message IDs to the relayer denylist. Use after investigating stuck messages with /investigate-stuck-messages, or when you have specific message IDs to denylist. |
Add message IDs to the relayer denylist configuration, create a PR, and deploy.
After investigation:
/investigate-stuck-messages and wants to denylist the found messagesDirect denylist request:
/denylist-stuck-messages <message_ids> [app_context=NAME] [reason=REASON]
| Parameter | Required | Default | Description |
|---|---|---|---|
message_ids | Yes | - | Space or newline separated message IDs (0x...) |
app_context | No | Inferred or "Unknown" | App context name for the comment |
reason | No | "stuck in prepare queue" | Reason for denylisting (for comment) |
environment | No | mainnet3 | Deployment environment |
Examples:
/denylist-stuck-messages 0xabc123 0xdef456 app_context=USDC/mainnet-cctp-v2-standard
/denylist-stuck-messages
0xabc123
0xdef456
0x789ghi
Extract all message IDs from the input. Valid formats:
0xabc 0xdef 0x1230xabc, 0xdef, 0x123Validate each ID:
0xUse AskUserQuestion to confirm:
Ready to denylist X messages for [APP_CONTEXT]:
| Message ID |
|------------|
| 0xabc123... |
| 0xdef456... |
Proceed?
Options:
Ask for GitHub handle if not known:
What is your GitHub handle for the branch name?
Edit typescript/infra/config/environments/mainnet3/customBlacklist.ts:
blacklistedMessageIds arrayExample addition:
// [APP_CONTEXT] [REASON] [YYYY-MM-DD]
'0xabc123...',
'0xdef456...',
Add entries near the end of the array, before the closing bracket.
# Checkout main and pull latest
git checkout main && git pull origin main
# Create branch
git checkout -b <github_handle>/denylist-<app_context>
# Stage changes
git add typescript/infra/config/environments/mainnet3/customBlacklist.ts
# Commit
git commit -m "chore: denylist <APP_CONTEXT> stuck messages
Added X message IDs to denylist for <APP_CONTEXT> route.
Reason: <REASON>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"
# Push and create PR
git push -u origin HEAD
gh pr create --title "chore: denylist <APP_CONTEXT> stuck messages" --body "$(cat <<'EOF'
## Summary
- Added X message IDs to the relayer denylist
- App context: `<APP_CONTEXT>`
- Reason: <REASON>
## Message IDs
<list of message IDs>
## Test plan
- [ ] Review message IDs are correct
- [ ] Deploy relayer with updated denylist
Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Before asking about deployment, output the Slack message:
**Slack Message (copy/paste to #relayer-alerts):**
:no_entry_sign: *Denylist PR created*
App context: `<APP_CONTEXT>`
Messages denylisted: X
Reason: <REASON>
PR: <PR_URL>
Use AskUserQuestion:
PR created. Deploy the relayer now with the updated denylist?
Options:
If user confirms, run:
pnpm --dir typescript/infra exec tsx ./scripts/agents/deploy-agents.ts -e mainnet3 --context hyperlane --role relayer
If user skips, output the command for later use.
If deployed, update the Slack message:
:no_entry_sign: *Denylist deployed*
App context: `<APP_CONTEXT>`
Messages denylisted: X
Reason: <REASON>
PR: <PR_URL>
If message IDs are for multiple destinations (from investigation output), group them in the blacklist file:
// [APP_CONTEXT] stuck messages [YYYY-MM-DD]
// dest: arbitrum
'0xabc123...',
'0xdef456...',
// dest: optimism
'0x789ghi...',
'0xjkl012...',
gh CLI authenticatedkubectl configured with mainnet cluster access