Skip to content

docs: epoch-zero bootstrap guide#431

Open
MuncleUscles wants to merge 1 commit into
mainfrom
docs/epoch-zero
Open

docs: epoch-zero bootstrap guide#431
MuncleUscles wants to merge 1 commit into
mainfrom
docs/epoch-zero

Conversation

@MuncleUscles

Copy link
Copy Markdown
Member

What

Adds a dedicated Epoch Zero (Bootstrap) explainer at pages/validators/epoch-zero.mdx, consolidating the special semantics of the genesis bootstrap epoch in one operator- and delegator-facing page. Motivated by the Jul 7-8 internal epoch-0 run: operators/delegators need the special rules laid out clearly, and the existing staking-guide "Genesis Epoch 0" section is Solidity-focused rather than conceptual.

New page covers

  • What epoch 0 is and why — the bootstrap window that assembles the first active validator set before consensus/economics exist.
  • Relaxed minimum stake — validators/delegators can register below the minimum (validator join guards min only if epoch > 0; delegators use a separate epoch-0 join path with no min).
  • Free restake and redelegate — epoch-0 exits pay out immediately (no unbonding); redelegate = free exit-then-join (no atomic op).
  • Conditional 0 to 2 advancement — epoch 1 is a zero-duration intermediate so epochAdvance moves 0 to 2 in effect, but only when inflation is initialized and funded through epoch 2; otherwise the network rests at epoch 1.
  • What changes at epoch 2 — active set selected by weight, only at-or-above-minimum validators carry active weight, unbonding delays apply.
  • What you'll see as an operator — below-min stake is normal in epoch 0 (not an error, mirrors the explorer fix), rest-at-1 is waiting-not-stuck, exits settle instantly, plan final stake before the jump.

Nav + cross-links

  • Registered in pages/validators/_meta.json as "Epoch Zero (Bootstrap)", placed right after Setup Guide.
  • Cross-linked from validators/setup-guide.mdx (intro Callout) and from the developers/staking-guide.mdx "Genesis Epoch 0" section header. Cross-links out to the staking-guide, setup-guide, staking concept page, and unstaking page.

Validation

  • scripts/list-docs-routes.js/validators/epoch-zero registers (routes 152 to 153).
  • scripts/generate-full-docs.js + scripts/check-llm-exports.js — both exit 0; new page flows into llms.txt / full-documentation.txt / llms-full.txt; export coverage guard passes (208 pages).
  • _meta.json validates as JSON. Matches existing page style (frontmatter description, nextra-theme-docs Callout imports, info/warning Callout usage).

All facts are contract-verified against genlayer-consensus v0.6-dev (behavior cited, no line numbers). No fabricated facts.

@netlify

netlify Bot commented Jul 2, 2026

Copy link
Copy Markdown

Deploy Preview for genlayer-docs ready!

Name Link
🔨 Latest commit 96cfc05
🔍 Latest deploy log https://app.netlify.com/projects/genlayer-docs/deploys/6a46e703e79f4800088c6fbe
😎 Deploy Preview https://deploy-preview-431--genlayer-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@MuncleUscles, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a1cddea3-9631-4fc6-a5f1-1a9c4a574bbf

📥 Commits

Reviewing files that changed from the base of the PR and between 19558ee and 96cfc05.

📒 Files selected for processing (4)
  • pages/developers/staking-guide.mdx
  • pages/validators/_meta.json
  • pages/validators/epoch-zero.mdx
  • pages/validators/setup-guide.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/epoch-zero

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant