Skip to content

CLI fix: status command eth_getLogs exceeds RPC block range limit #662

@realproject7

Description

@realproject7

From E2E test #644 / agent-os #324

Bug

`plotlink status` queries `eth_getLogs` from the deployment block to latest — millions of blocks on mainnet. Public Base RPC limits `eth_getLogs` to ~10,000 blocks per query, causing the request to fail.

Fix

Options:

  1. Paginate — query in 10k-block chunks and aggregate results
  2. Use Supabase — fetch storyline data from the DB instead of on-chain logs (faster, no RPC limit)
  3. Narrow range — only query recent blocks (e.g., last 24h) for activity data, get storyline metadata from DB

Option 2 is recommended — the CLI already has optional Supabase config (`PLOTLINK_SUPABASE_URL`, `PLOTLINK_SUPABASE_ANON_KEY`). Use it as primary, fall back to paginated RPC if not configured.

Branch

`task/662-cli-status-pagination`

Self-Verification (T3)

  • Run `plotlink status --storyline 43` on Base mainnet — returns correct data without RPC error
  • Works with Supabase config set (primary path)
  • Works without Supabase config (RPC fallback with pagination)
  • `npm run build` passes

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/T3Assigned to T3 builder agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions