Explorer now reads from the indexer; 30-day RPC history merged, not applied

The public block explorer for Satsuma's chain now uses the indexer, a service that reads each block and stores it so the explorer can search history quickly. The change was merged and deployed. The live address page shows its history indexed to block 4,814,188, and contract pages show a form for verifying their source code. The indexer holds 21,257 blocks with no gaps and sits 25 blocks behind finality, within one cron run. A README sentence with doubled parentheses was tidied before the merge.

One decision came out of the deploy: the indexer does not redeploy itself. In the words of the record, "merging to main redeploys the site but not the indexer. Run pnpm indexer:deploy yourself after changing the Worker code."

A configuration change, merged with no CI run, makes the template for the chain's RPC node keep 30 days of blocks and state, has the Ethereum JSON-RPC adapter keep its transaction index on disk permanently, and gives nginx a larger response buffer for batched requests that were failing with 502 errors. The rollout steps are written up alongside the change. None of it is live: merging does not touch the node, and nothing deploys on merge. The validators still keep 256 blocks.

The work was done with Claude in Claude Code. An earlier planning session on archive history, which had stopped at its usage limit, was resumed and told that the indexer is now live, so the plan would cover backfilling earlier blocks. Two things are still open: the indexer can only backfill earlier blocks once the 30-day history is live, and unverified contract pages log one harmless 404 in the browser console.