fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
1.0 KiB
1.0 KiB
RMN Policy for Tezos/Etherlink Flows (when using CCIP)
When high-value Tezos/Etherlink flows use CCIP, define RMN policy (blessing/veto) and test.
Scope
- RMN: Risk Management Network (5–7 nodes per CCIP_DEPLOYMENT_SPEC). Independent security layer that can bless or veto commits/execution.
- When: Only relevant if Etherlink (or Tezos via an EVM bridge) is on an official CCIP lane. Tezos L1 does not use CCIP; no RMN for Tezos L1.
Policy
- High-value threshold: Define threshold (e.g. USD or token amount) above which RMN blessing is required before Execute DON proceeds.
- Blessing/veto: RMN nodes validate payload; if approved, Execute DON can proceed; if vetoed, execution is blocked.
- Tezos/Etherlink: If Etherlink is on CCIP, apply same RMN policy as other destination chains (e.g. require blessing for transfers above X).
Tests
- Run tests that trigger high-value flow and verify RMN blessing is required and execution only proceeds after blessing (or veto blocks execution).