examples: publish to the production bucket instead of the development one

[easeev]

Summary

The three ingest examples targeted the chainplot-test bucket behind an r2.dev origin, which is the bucket publish was developed against. They now target the chainplot bucket behind chainplot.chainstacklabs.com.

All three were republished there and regenerated with the current viewer, so the live pages carry the aligned amount columns, level KPI cards and the corrected footer rather than the layout they were built with months ago.

The README now lists usdc-supply alongside the other two, since it is published as well, and explains what the pointer links are.

Live now

Example	Pointer	Contents
transfer-traffic	https://chainplot.chainstacklabs.com/transfer-traffic/latest.json	92 transfers, blocks 18,600,000–18,600,010
protocol-flows	https://chainplot.chainstacklabs.com/protocol-flows/latest.json	258 deposit/withdrawal events over the same range
usdc-supply	https://chainplot.chainstacklabs.com/usdc-supply/latest.json	~6.8M mints and burns over roughly a year

Verification

• transfer-traffic and protocol-flows were re-ingested from scratch against an Ethereum archive endpoint and reproduced their documented figures exactly: 92 transfers and 258 events, coverage complete_with_rows over the pinned range in both cases.
• usdc-supply was rebuilt from its existing snapshots, whose coverage spans blocks 23,400,000–25,987,000 across nine segments per source, all complete.
• All four published projects, including the Arc demo already in this bucket, now serve the same viewer bundle; each pointer resolves and each release directory returns HTTP 200.
• Full offline suite: 321 passed, 3 skipped. Each retargeted example validates offline.

Dated plan documents under docs/plans/ keep the bucket name they were written with.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Added a year-long USDC supply changes example to the README, covering approximately 6.8 million mints and burns.
  • Updated example links to use stable public publish roots and the current public domain.

• Configuration

  • Updated publishing for protocol flows, transfer traffic, and USDC supply examples to use the production bucket and public URL.
  • Existing publication prefixes remain unchanged.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 7e592218-3892-4945-bd8a-f43fe01851d1

📥 Commits

Reviewing files that changed from the base of the PR and between 701e0a0 and 2ba89c5.

📒 Files selected for processing (1)

• README.md

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR updates all three example publish targets to the production chainplot bucket and public domain. The README adds the USDC supply example and updates the example links.

Changes

Live example publishing

Layer / File(s)	Summary
Publish targets and documentation examples/*/chainplot.yaml, README.md	The three r2 targets now use the chainplot bucket and https://chainplot.chainstacklabs.com. The README documents the three examples and updates their publish-root links.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 2ba89

The examples now use the production publishing domain and the README documents all three live examples. No concrete current-head risk remains identified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: updating examples to publish to the production bucket instead of the development bucket.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}