docs: rewrite README with deployed addresses and versions#59
Conversation
Replace the stale README with one that matches the shipped contracts: - Deployments table: mainnet events/profile at 1.1.0, testnet events/profile at 1.0.0 (addresses + live version() reads) - Contract descriptions cover all four pillars and the current profile surface (reputation + earnings, lazy bootstrap) - Repo layout matches the tree (bootstrap.rs, crowdfunding.rs, profile_client.rs, scripts/admin + scripts/deploy) - Deploy sequence reflects the current constructors; upgrade section documents the timelocked propose/apply/migrate flow - Drop external spec references and stale audit/deployment notes Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughDocumentation-only update to README.md replacing contract descriptions with ChangesREADME documentation update
Estimated code review effort: 1 (Trivial) | ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
rustfmt.yml: drop the workflow_call trigger, deploy job, and secret declarations that existed only to chain into contract-deploy.yml. verify-build.yml: drop the chained rustfmt job that called rustfmt.yml as a reusable workflow (no longer reusable) with secrets it no longer declares; the standalone rustfmt workflow covers the same push branches. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
What
Rewrites the README to match the shipped contracts and live deployments.
version()reads:CCFVEGOQ…JGQZand profileCD3KH4OE…E3PC, both1.1.0CBEODVJG…VTZPand profileCCA3OAIB…Q6T3, both1.0.0bootstrap.rs,crowdfunding.rs,profile_client.rs,scripts/admin+scripts/deploy).Notes
version()reads, not copied from notes.1.0.0: it has not been upgraded since the mainnet1.1.0apply.🤖 Generated with Claude Code
Summary by CodeRabbit