Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates

- 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>

2026-02-12 15:46:57 -08:00

1.7 KiB

Raw Blame History

Multi-Chain Execution — Key Rotation

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

Scope: Hot keys (execution), warm keys (MirrorRegistry publisher), cold keys (contract admin).

Key tiers

Hot: Transaction execution per lane; high turnover; segment by chain/wallet/lane.
Warm: Commitment publishing to MirrorRegistry on public mainnets; one per chain or shared.
Cold: Contract admin (MirrorRegistry, TransactionMirror, etc.); multisig + timelock preferred.

Rotation procedure

Hot keys

Generate new key; add to wallet lane config (env or secrets manager).
Sync nonce: set next nonce for (chainId, newWallet, lane) from on-chain getTransactionCount.
Route new intents to new wallet; drain or retire old wallet once pending txs finalize.
Update EO/config to use new wallet for that lane; remove old key from config.

Warm keys (MirrorRegistry publisher)

Deploy or use existing MirrorRegistry; add new address as publisher via setPublisher(newAddress, true) (admin).
Configure Mirroring Service to use new warm key for submitCommit.
After confirming new key can submit: call setPublisher(oldAddress, false) (admin).
Rotate secret in KMS/env; restart Mirroring Service.

Cold keys (contract admin)

Use multisig/timelock to propose new admin (e.g. MirrorRegistry.setAdmin(newAdmin)).
Execute after timelock; verify new admin on-chain.
Revoke old admin if applicable (contract-dependent).

Verification

Hot: Submit a test intent and confirm execution from new wallet.
Warm: Trigger a commit and confirm CommitSubmitted event from new publisher.
Cold: Perform a single admin action (e.g. setPublisher) and confirm it succeeds.

1.7 KiB Raw Blame History