The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
These are the raw probes for determining what an owner address IS on chain. A caller runs the relevant probe, interprets the result per the tables below, then applies its OWN policy (reject EOA, ask-the-user for non-Safe, existence-only sanity check, controller classification, etc.). This skill supplies the primitives and their interpretation only — it does not decide policy.
cast code <address> --rpc-url <rpc> (or the multiProvider equivalent):
| Result | Meaning |
|---|---|
0x (no code) | Plain EOA. |
0xef0100<20-byte-delegate> — 46 chars, matches ^0xef0100[0-9a-fA-F]{40}$ | EIP-7702-delegated EOA. Still has a private key behind it; treat as an EOA for ownership purposes. |
| any other bytecode | Contract (Safe / ICA / timelock / custom multisig / …) — probe further. |
cast call <address> "VERSION()(string)" --rpc-url <rpc>:
| Result | Meaning |
|---|---|
a version string (e.g. "1.3.0") | Gnosis Safe — record the version. |
| reverts / no return | Not a Safe — some other contract; probe further or ask the user. |
Derive the deterministic ICA address for (origin, controlling-owner) read-only — view calls only, no transaction — with get-owner-ica.ts and NO --deploy:
pnpm --silent tsx typescript/infra/scripts/keys/get-owner-ica.ts \
--environment mainnet3 --ownerChain <origin> --owner <controlling-owner> --chains <chain>
⚠️ Never use
hyperlane ica deployfor this probe. That CLI command has no read-only mode: it deploys the ICA (spends gas, creates a contract) whenever the derived account is absent. Probing a non-ICA owner therefore mints an unrelated ICA — the exact failure a read-only classifier must avoid.get-owner-ica.tswithout--deployonly callsInterchainAccount.getAccount(a view) and prints the address.
Compare the derived address to the on-chain owner:
| Result | Meaning |
|---|---|
| derived address == the on-chain owner | The owner is an ICA controlled by <controlling-owner> on <origin>. Classify the controller by re-running the code + Safe probes on it. |
| derived address != the owner | Not an ICA from that origin/controller — try another origin/controller, or ask the user. |
getAccountInfo(<pubkey>) via the SVM SDK provider:
| Result | Meaning |
|---|---|
| null | Address has never had state on this chain (transferring ownership here would brick the route). |
| non-null | Account exists (may be executable / PDA / plain wallet). |
Contract-but-not-a-Safe is NOT automatically an ICA. These probes cover only the cheap cases (EOA via code, Safe via VERSION(), ICA via a known origin/controller derivation). Everything else — Squads multisig PDA, Turnkey, Privy, MPC, custom multisig, timelock — the caller must resolve with the user; never guess.
/warp-deploy-validate-owners (per-chain classify + reject-EOA policy), /warp-update-resolve-artifacts (per-artifact classify + governance-map shortcut + open-set + controller classification), /warp-deploy-update-owners (target-owner existence sanity check).
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Write a changeset file in the `hyperlane-registry` repo for a PR that adds, updates, or modifies warp route config / chain metadata / addresses. Canonical pattern — never run the interactive `pnpm changeset` CLI; write the file directly. Referenced by any skill that opens a registry PR.
日本語の概要は準備中です。原文の説明を表示しています。
Trigger Docker image builds for Hyperlane agent, monorepo, or node service images. Use when the user wants to build new Docker images for a branch, commit, or tag.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
日本語の概要は準備中です。原文の説明を表示しています。
Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or other processing problems.
日本語の概要は準備中です。原文の説明を表示しています。
Debug RPC provider health issues for a chain. Use when alerts mention RPC failures, high latency, stale blocks, or provider errors. Diagnoses the issue and recommends fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.
日本語の概要は準備中です。原文の説明を表示しています。