Skip to content

[indexer] Add guarded Base mainnet canary FlowPulse reader #75

@FlowmemoryAI

Description

@FlowmemoryAI

Context

The 2026-05-13 Base V0 canary deployment emitted real FlowPulse logs on chain id 8453, but the checked-in live reader intentionally accepts only Base Sepolia (84532).

Build

Add a guarded Base canary reader path that:

  • requires explicit RPC URL, addresses, and block range;
  • refuses broad/default scans;
  • persists state and checkpoint like the Base Sepolia reader;
  • labels output as canary/mainnet-observed, not production readiness;
  • tests wrong chain, empty ranges, malformed logs, duplicates, and reorg replacements.

Evidence

See docs/DEPLOYMENTS/2026-05-13-base-canary-v0.md after the deployment-report PR lands.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions