Secure the Metalayer message-passing network
Mailbox
dispatched messages each origin chain and publish those signatures so Metalayer relayers can aggregate and forward messages.
Topic | Hyperlane | Metalayer |
---|---|---|
Contract addresses | Public hyperlane‑registry repo | Config bundle supplied by Caldera – do not copy Hyperlane values |
Agents network | Global Hyperlane mesh | Isolated Metalayer mesh |
CLI, flags, binary | hyperlane-agent | Same binary (Abacus Works image) |
Staking / PoS | Hyperlane POS contracts | N/A – no on‑chain staking for Metalayer |
Requirement | Notes |
---|---|
Secure signing key | AWS KMS, Vault HSM, or raw hex. Same CLI flags as Hyperlane (--validator.* ). |
Available gas balance | The signer must hold enough native token to broadcast the on‑chain announce tx. The same signer MAY be reused across multiple chains. |
Public storage (checkpoint syncer) | S3 bucket (prod). |
Machine | 2 vCPU / 2 GB RAM / 4 GB disk is sufficient. |
RPC endpoints | Provide ≥ 2 per chain. Private RPCs ensure validator security. |
Max 1 chain per validator instance | Each validator instance only supports 1 chain at most. For redundancy, operators may choose to run multiple validator instances (e.g., across different availability zones) pointing to the same S3 bucket. |
metalayer-validator-sigs-<YOU>
-checkpointSyncer.type localStorage
validator.json
(replace placeholders; defaults noted):
announce()
; fund the signer with a small amount of native token first.
checkpointSyncer.folder
(S3 prefix) and -db
path.Symptom | Likely Cause | Fix |
---|---|---|
not enough gas | Signer wallet unfunded | Top‑up with native token |
No signatures in S3 | Bad bucket policy / wrong region | Check IAM & checkpointSyncer section |
High db: prune required | Disk too small | Give ≥ 5 GB or mount volume |
:9090/metrics
by default. We suggest implementing Hyperlane’s Grafana dashboard.