Skip to content

fix: split testnet faucet into Asimov and Bradbury#388

Merged
MuncleUscles merged 16 commits intomainfrom
fix/faucet-testnets
Apr 7, 2026
Merged

fix: split testnet faucet into Asimov and Bradbury#388
MuncleUscles merged 16 commits intomainfrom
fix/faucet-testnets

Conversation

@MuncleUscles
Copy link
Copy Markdown
Member

@MuncleUscles MuncleUscles commented Apr 7, 2026

Split single Testnet row into Testnet Asimov and Testnet Bradbury. Added link to Networks page.

Summary by CodeRabbit

  • Documentation
    • Added "What is GenLayer" guide and new Image Processing + Features docs for Intelligent Contracts
    • Restructured homepage messaging and Get Started layout
    • Consolidated and reorganized several protocol pages into a revised navigation with redirects
    • Expanded Use Cases and reframed Challenges → Trade-offs in introductions
    • Updated Intelligent Contract feature cards and environment/faucet details (Testnet Asimov/Bradbury)

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 7, 2026

Deploy Preview for genlayer-docs ready!

Name Link
🔨 Latest commit 34df446
🔍 Latest deploy log https://app.netlify.com/projects/genlayer-docs/deploys/69d53d64489a6e0008840b31
😎 Deploy Preview https://deploy-preview-388--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
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 7, 2026

Warning

Rate limit exceeded

@MuncleUscles has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 25 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 24 minutes and 25 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 988d1d28-9f5e-41ef-bb07-c25c1e7166a4

📥 Commits

Reviewing files that changed from the base of the PR and between da51347 and 34df446.

📒 Files selected for processing (2)
  • pages/FAQ.mdx
  • pages/developers/intelligent-contracts/features/image-processing.mdx
📝 Walkthrough

Walkthrough

Reorganizes and consolidates protocol docs into a new canonical "What is GenLayer" page with redirects for deprecated pages, revises Optimistic Democracy and transaction lifecycle content, adds/updates Intelligent Contract feature pages (including image-processing and value-transfers), updates homepage messaging, and adds Testnet Bradbury to developer environment docs.

Changes

Cohort / File(s) Summary
Protocol metadata & canonical page
pages/understand-genlayer-protocol/_meta.json, pages/understand-genlayer-protocol/what-is-genlayer.mdx
Added a new canonical "What is GenLayer" page and updated navigation metadata keys/labels.
Redirected/removed legacy pages
pages/understand-genlayer-protocol/what-are-intelligent-contracts.mdx, pages/understand-genlayer-protocol/what-makes-genlayer-different.mdx, pages/understand-genlayer-protocol/who-is-genlayer-for.mdx, pages/understand-genlayer-protocol/why-we-are-building-genlayer.mdx
Replaced full content with import-backed stubs that redirect readers to the new canonical page.
Consensus & lifecycle docs
pages/understand-genlayer-protocol/optimistic-democracy-how-genlayer-works.mdx
Rewrote Optimistic Democracy page to emphasize validator consensus over diverse AI evaluations, introduced a new Transaction Lifecycle with numbered states and multi-round escalation for appeals.
Use cases & introduction framing
pages/understand-genlayer-protocol/typical-use-cases.mdx, pages/developers/intelligent-contracts/introduction.mdx
Expanded and reorganized use-case categories (focus on subjective judgment), reframed intro section from "Challenges and Mitigations" to "Trade-offs" with updated consensus/non-determinism guidance.
Features catalog & feature pages
pages/developers/intelligent-contracts/features.mdx, pages/developers/intelligent-contracts/features/_meta.json, pages/developers/intelligent-contracts/features/image-processing.mdx
Added features index page and image-processing page; updated features metadata (added image-processing), and adjusted feature card set/titles/hrefs.
Value transfers / environments
pages/developers/intelligent-contracts/features/value-transfers.mdx, pages/developers/intelligent-contracts/first-contract.mdx
Split/updated balances into value-transfers and messages links; added Testnet Bradbury row to funding accounts; clarified GenVM version-hash wording.
Homepage & discovery
pages/index.mdx
Updated homepage headline and narrative to "Trust Infrastructure for the AI Age", reworked Get Started grid/layout and community/hiring messaging.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • cristiam86
  • kp2pml30

Poem

🐰
I hopped through docs with eager paws,
Redirected pages, fixed their flaws,
A "What is GenLayer" carrot found,
Bradbury hops in, global bound,
Now features bloom across the ground.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description is minimal but directly addresses the main changes. However, it lacks detail about the broader scope of changes across multiple files (homepage, feature cards, use cases, new pages, redirects, etc.) that go well beyond the testnet faucet split. Expand the description to cover all significant changes in the PR, such as new documentation pages, homepage restructuring, feature list reorganization, use case updates, and redirect pages for better clarity.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately and specifically identifies the primary change: splitting the single testnet row into two distinct testnet environments (Asimov and Bradbury).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/faucet-testnets

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 and usage tips.

New:
- what-is-genlayer: unified page with current messaging, architecture,
  comparison table, code example
Rewritten:
- how-genlayer-works: correct transaction lifecycle (including Leader
  Revealing stage), updated non-determinism framing
Updated:
- typical-use-cases: added Autonomous Agents
- _meta.json: clean 4-entry nav
Redirected:
- what-are-intelligent-contracts → what-is-genlayer
- what-makes-genlayer-different → what-is-genlayer
- why-we-are-building-genlayer → what-is-genlayer
- who-is-genlayer-for → what-is-genlayer
Copy link
Copy Markdown
Member Author

@MuncleUscles MuncleUscles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can also handle images, I think we should try an promote this as more of a highlight

<Card title="😵‍💫 Types" href="../types" />
<Card title="🔢 Types" href="../types" />
<Card title="💾 Storage" href="storage" />
<Card title="🐛 Error Handling" href="error-handling" />
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

icon doesn't make sense

<Card title="💸 Value Transfers" href="value-transfers" />
<Card title="📨 Messages" href="messages" />
<Card title="🧠 Interacting with Intelligent Contracts" href="interacting-with-intelligent-contracts" />
<Card title="🐒 Interacting with EVM Contracts" href="interacting-with-evm-contracts" />
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

icon doesn't make sense


| Feature | Traditional Smart Contracts | Intelligent Contracts |
|---|---|---|
| **Language** | Solidity, Vyper | Python |
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

idk how popular vyper is, rust maybe for solana?


**GenLayer Chain** — an EVM-compatible L2 (zkSync Elastic Chain). Holds account balances via ghost contracts, handles standard Ethereum operations (`eth_*` methods), and anchors to Ethereum's security model.

**GenVM** — the execution environment for Intelligent Contracts. A Python runtime with native access to LLMs, web data, and non-deterministic operations.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

genmv is not just python - it's wasm, with a python interpreter, but can also run native compiled code. check repo to read more


@gl.public.write
def resolve(self) -> None:
result = gl.eq_principle.call_llm(
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not valid code, check the docs properly

…, code example

- Error Handling: 🐛→⚠️, EVM Contracts: 🐒→🔗
- Comparison table: Vyper→Rust (Solana)
- GenVM: WebAssembly-based VM (Wasmtime) with Python interpreter + native code
- Code example: replaced invalid code with WizardOfCoin from actual docs
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
pages/understand-genlayer-protocol/who-is-genlayer-for.mdx (1)

1-5: Unused Callout import.

The Callout component is imported but not used in this redirect stub. Consider either removing the import or wrapping the redirect notice in a Callout for better visual prominence.

Option 1: Remove unused import
-import { Callout } from "nextra-theme-docs";
-
 # Who Is GenLayer For?

 This page has moved to [What is GenLayer](/understand-genlayer-protocol/what-is-genlayer).
Option 2: Use Callout for better visibility
 import { Callout } from "nextra-theme-docs";

 # Who Is GenLayer For?

-This page has moved to [What is GenLayer](/understand-genlayer-protocol/what-is-genlayer).
+<Callout type="info">
+  This page has moved to [What is GenLayer](/understand-genlayer-protocol/what-is-genlayer).
+</Callout>
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@pages/understand-genlayer-protocol/who-is-genlayer-for.mdx` around lines 1 -
5, Remove the unused Callout import or use it to wrap the redirect message:
either delete the import statement "import { Callout } from
\"nextra-theme-docs\";" to eliminate the unused symbol, or replace the plain
markdown notice with a JSX Callout component (e.g., <Callout>...This page has
moved to <a href="/understand-genlayer-protocol/what-is-genlayer">What is
GenLayer</a>...</Callout>) so the imported Callout symbol is actually used.
pages/understand-genlayer-protocol/typical-use-cases.mdx (1)

17-20: Consider varying the repeated “Does …” bullet openings.

The four consecutive bullets scan a bit repetitive; light rewording would improve readability.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@pages/understand-genlayer-protocol/typical-use-cases.mdx` around lines 17 -
20, The four consecutive bullet lines starting with "Does a new prediction
market..." create repetitive openings; replace some "Does ..." leads with varied
phrasing to improve flow — e.g., reword one or two to active or descriptive
starts like "Is a new prediction market eligible for listing?", "Assess whether
a DAO proposal complies with the organization's charter", "Ensure a content
submission follows community standards", "Verify a transaction complies with
regulatory requirements" — update the bullet texts in the section containing
those four items to mix question and imperative phrasing while preserving
original meaning.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pages/index.mdx`:
- Line 20: The grid uses a fixed 3-column value in the inline style
(gridTemplateColumns: 'repeat(3, minmax(0, 1fr))'), which breaks on smaller
viewports; update the style on that div to a responsive pattern such as using
repeat(auto-fit or auto-fill) with minmax (e.g., minmax(240px, 1fr)) or replace
the inline style with responsive CSS classes/media queries so the container (the
div with gridTemplateColumns) automatically collapses to fewer columns on narrow
screens.

---

Nitpick comments:
In `@pages/understand-genlayer-protocol/typical-use-cases.mdx`:
- Around line 17-20: The four consecutive bullet lines starting with "Does a new
prediction market..." create repetitive openings; replace some "Does ..." leads
with varied phrasing to improve flow — e.g., reword one or two to active or
descriptive starts like "Is a new prediction market eligible for listing?",
"Assess whether a DAO proposal complies with the organization's charter",
"Ensure a content submission follows community standards", "Verify a transaction
complies with regulatory requirements" — update the bullet texts in the section
containing those four items to mix question and imperative phrasing while
preserving original meaning.

In `@pages/understand-genlayer-protocol/who-is-genlayer-for.mdx`:
- Around line 1-5: Remove the unused Callout import or use it to wrap the
redirect message: either delete the import statement "import { Callout } from
\"nextra-theme-docs\";" to eliminate the unused symbol, or replace the plain
markdown notice with a JSX Callout component (e.g., <Callout>...This page has
moved to <a href="/understand-genlayer-protocol/what-is-genlayer">What is
GenLayer</a>...</Callout>) so the imported Callout symbol is actually used.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c39f4509-f84b-49aa-bc22-0dae03981372

📥 Commits

Reviewing files that changed from the base of the PR and between dd7ba56 and 9fe2e1f.

📒 Files selected for processing (12)
  • pages/developers/intelligent-contracts/features/features.mdx
  • pages/developers/intelligent-contracts/features/value-transfers.mdx
  • pages/developers/intelligent-contracts/introduction.mdx
  • pages/index.mdx
  • pages/understand-genlayer-protocol/_meta.json
  • pages/understand-genlayer-protocol/optimistic-democracy-how-genlayer-works.mdx
  • pages/understand-genlayer-protocol/typical-use-cases.mdx
  • pages/understand-genlayer-protocol/what-are-intelligent-contracts.mdx
  • pages/understand-genlayer-protocol/what-is-genlayer.mdx
  • pages/understand-genlayer-protocol/what-makes-genlayer-different.mdx
  • pages/understand-genlayer-protocol/who-is-genlayer-for.mdx
  • pages/understand-genlayer-protocol/why-we-are-building-genlayer.mdx

Comment thread pages/index.mdx

<br/>
<div style={{ display: 'grid', gridTemplateColumns: 'repeat(2, minmax(0, 1fr))', gap: '1rem' }}>
<div style={{ display: 'grid', gridTemplateColumns: 'repeat(3, minmax(0, 1fr))', gap: '1rem' }}>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Make the card grid responsive instead of fixed at 3 columns.

A hardcoded 3-column layout can make cards too narrow on smaller screens.

Proposed fix
-<div style={{ display: 'grid', gridTemplateColumns: 'repeat(3, minmax(0, 1fr))', gap: '1rem' }}>
+<div style={{ display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(220px, 1fr))', gap: '1rem' }}>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<div style={{ display: 'grid', gridTemplateColumns: 'repeat(3, minmax(0, 1fr))', gap: '1rem' }}>
<div style={{ display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(220px, 1fr))', gap: '1rem' }}>
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@pages/index.mdx` at line 20, The grid uses a fixed 3-column value in the
inline style (gridTemplateColumns: 'repeat(3, minmax(0, 1fr))'), which breaks on
smaller viewports; update the style on that div to a responsive pattern such as
using repeat(auto-fit or auto-fill) with minmax (e.g., minmax(240px, 1fr)) or
replace the inline style with responsive CSS classes/media queries so the
container (the div with gridTemplateColumns) automatically collapses to fewer
columns on narrow screens.

- Move features index to sibling features.mdx so Nextra makes the
  sidebar folder title clickable (like core-concepts)
- New Image Processing page: exec_prompt with images, web screenshots,
  use cases (visual evidence, documents, web monitoring)
- Add Image Processing card to features grid
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
pages/understand-genlayer-protocol/typical-use-cases.mdx (1)

17-20: Reduce repeated sentence starts in the criteria checklist.

Line 17 to Line 20 repeat “Does …” in each bullet. Consider slight variation for smoother reading.

✍️ Optional wording refinement
-- Does a new prediction market meet listing guidelines?
-- Does a DAO proposal comply with the organization's charter?
-- Does a content submission follow community standards?
-- Does a transaction comply with regulatory requirements?
+- Whether a new prediction market meets listing guidelines
+- Whether a DAO proposal complies with the organization's charter
+- Whether a content submission follows community standards
+- Whether a transaction complies with regulatory requirements
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@pages/understand-genlayer-protocol/typical-use-cases.mdx` around lines 17 -
20, The four checklist bullets starting with "Does ..." (the items about a new
prediction market, a DAO proposal, a content submission, and a transaction)
repeat the same sentence start; update them to vary phrasing for smoother
reading by replacing some "Does ..." starts with alternatives like "Whether
...", "Assess whether ...", "Confirm that ...", or "Verify that ..." so the
content remains the same but the sentence openings differ and flow better.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@pages/understand-genlayer-protocol/typical-use-cases.mdx`:
- Around line 17-20: The four checklist bullets starting with "Does ..." (the
items about a new prediction market, a DAO proposal, a content submission, and a
transaction) repeat the same sentence start; update them to vary phrasing for
smoother reading by replacing some "Does ..." starts with alternatives like
"Whether ...", "Assess whether ...", "Confirm that ...", or "Verify that ..." so
the content remains the same but the sentence openings differ and flow better.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c279b461-2882-4e54-900e-226a748abde1

📥 Commits

Reviewing files that changed from the base of the PR and between 9fe2e1f and da51347.

📒 Files selected for processing (7)
  • pages/developers/intelligent-contracts/features.mdx
  • pages/developers/intelligent-contracts/features/_meta.json
  • pages/developers/intelligent-contracts/features/features.mdx
  • pages/developers/intelligent-contracts/features/image-processing.mdx
  • pages/developers/intelligent-contracts/first-contract.mdx
  • pages/understand-genlayer-protocol/typical-use-cases.mdx
  • pages/understand-genlayer-protocol/what-is-genlayer.mdx
✅ Files skipped from review due to trivial changes (5)
  • pages/developers/intelligent-contracts/features/_meta.json
  • pages/developers/intelligent-contracts/first-contract.mdx
  • pages/developers/intelligent-contracts/features/image-processing.mdx
  • pages/understand-genlayer-protocol/what-is-genlayer.mdx
  • pages/developers/intelligent-contracts/features.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/developers/intelligent-contracts/features/features.mdx

@MuncleUscles MuncleUscles merged commit 7977f5e into main Apr 7, 2026
8 checks passed
@MuncleUscles MuncleUscles deleted the fix/faucet-testnets branch April 7, 2026 17:29
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