Skip to content

cow: rename twap-monitor to ccow-monitor and enable mainnet #657

Description

@mfw78

Final car of the convergence train. Supersedes the rename outcome of #522.

With zero TWAP logic left in the module, git mv modules/twap-monitor modules/ccow-monitor as a provably mechanical PR, then enable mainnet. This is the tracker anchor for the generic monitor that #568 already treats as committed.

Why

Rename, not new-module-plus-delete: the 1200-line keeper suite and 995-line run suite travel through every commit, so there is no coverage gap and no dual-maintenance window. TWAP survives as watch scope and vectors, not code, exactly as #138 recorded. Mainnet enablement rides here because the manifest, engine config, and ops scripts all change names in the same sweep.

Scope

  • git mv, crate name, module label "ccow".
  • module.mainnet.toml (chain 1, three event rows); engine [chains.1]; wire the existing mainnet cow-venue adapter manifest.
  • Sweep scripts/lib.sh:18, e2e-onchain.sh, baseline_latency.py:88, and the engine.*.toml rows.
  • CI rg gate: zero surviving 0xfdaF… or COMPOSABLE_COW references.

Done when

  • The rename commit is mechanical (rename-detected, no logic diff).
  • The mainnet manifest is live and the module subscribes to the three fork events on chain 1.
  • The CI grep gate is green.
  • Both test suites pass unmodified apart from path and name changes.

Blocked by: #655.

Metadata

Metadata

Assignees

No one assigned

    Labels

    component/manifestnexum.toml / nexum-engine.toml parsing + config-valuecomponent/modulesshipped guest modules (twap, ethflow, examples, fixtures)debtCode works but makes future work harder.effort/hoursFew hours. Single PR.pr-trainPart of the current stacked PR train; lands in sequence, do not merge out of order.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions