gistfile1.md

• akhil's walkthrough
  • RDD
    • separate fork from CCIP (reference-data-directory-ccip)
    • plugs into CLO
    • ccip-owner contract (MCM, timelock)
      • not much detail in the signer set, stored separately so all the chains have one config -> toplevel ccip-owner -> mcmConfigs
      • signers (metadata)
    • CLF?
    • "guide to operate CCIP and MCM" has latest detail "
  • first thing engops does: add new chain folder
    • always defining owner contracts first
    • define configurations for arm, armproxy, priceregistry, tokens
    • no routes yet
    • generate chain config next ->
    • file placed into feeds manager
      • new chain, target network etc
      • token pools/funding token pools
    • now CLF deploys all chain contracts
    • CLF responsible for ownership transfer (timelock)
    • ./ccip-generate-onchain to generate onchain equivalent
    • then generates proposal
    • changes aren't batched in proposal since we need to acknowledge for block size
    • separate RDD because security didn't want engops to push to our repo and didn'twant to disclose changes
    • proposals are either 0 (no proposals) or 1-2 -> usually two for both source and dest
      • and are a diff in changes on both chains
    • adding to allowlist is manual for example
      • need to do scoping on improvements
    • proposals = schedule/bypass/cancel (bypass skips the timelock)
    • deploying through CLO
    • CLO for deployments, gauntlet only for config
    • gauntlet only used for signing the proposal, nothing else really since this rdd tool does the proposal generation
    • signatures added
    • pending branch merged -> github action schedules these transactions with timelock
    • how does MS1 fit here?
    • rddtool/types/cross_chain OnRamp for example

• MCM took over gnosis, we don't use gnosis at all anymore

  • TODO: setup VPN
• biggest work
  • gauntlet++
  • defining schema
  • and upgrade path to new tooling and docs
  • thinking how to scale to more chains and lanes