Networks
GenLayer operates as two layers: the GenLayer RPC handles intelligent contract operations (gen_* methods), while the GenLayer Chain is the underlying L2—an Arbitrum Orbit chain that settles to Ethereum and uses GEN as its native gas token—that handles standard Ethereum operations (eth_* methods). The GenLayer RPC also passes through all eth_* calls to the underlying chain, so you can use either endpoint for standard wallet operations. See GenLayer Chain integration for how the chain, bridge, and settlement work.
GenLayer Chain runs on Arbitrum Orbit from consensus v0.6. Testnet Asimov and Bradbury keep the endpoints and chain ID listed below until they upgrade to v0.6; this page will list the new endpoints and contract addresses when they move.
For the full RPC reference, see GenLayer Node API.
Your wallet connects to the GenLayer RPC — it handles both intelligent contract calls and standard Ethereum methods.
Testnet Bradbury
Production-like testnet with real AI/LLM workloads.
| Setting | Value |
|---|---|
| GenLayer RPC | https://rpc-bradbury.genlayer.com |
| GenLayer Chain RPC | https://rpc.testnet-chain.genlayer.com |
| Chain ID | 4221 |
| Currency | GEN |
| Explorer | explorer-bradbury.genlayer.com (opens in a new tab) |
| Chain Explorer | explorer.testnet-chain.genlayer.com (opens in a new tab) |
| Faucet | testnet-faucet.genlayer.foundation (opens in a new tab) |
Testnet Asimov
Infrastructure and stress testing.
| Setting | Value |
|---|---|
| GenLayer RPC | https://rpc-asimov.genlayer.com |
| GenLayer Chain RPC | https://rpc.testnet-chain.genlayer.com |
| Chain ID | 4221 |
| Currency | GEN |
| Explorer | explorer-asimov.genlayer.com (opens in a new tab) |
| Chain Explorer | explorer.testnet-chain.genlayer.com (opens in a new tab) |
| Faucet | testnet-faucet.genlayer.foundation (opens in a new tab) |
Studionet
Hosted development environment — no local setup required.
| Setting | Value |
|---|---|
| GenLayer RPC | https://studio.genlayer.com/api |
| Chain ID | 61999 |
| Currency | GEN |
| Explorer | explorer-studio.genlayer.com (opens in a new tab) |
| Faucet | Built-in — use the 💧 button in the account selector |
Studio development preview
Release-candidate environment for testing the next Studio and consensus stack before it is promoted to Studionet. State and availability are not guaranteed across deployments.
| Setting | Value |
|---|---|
| Studio web app | studio-dev.genlayer.com (opens in a new tab) |
| Canonical GenLayer RPC | https://studio-dev.genlayer.com/api |
| Chain ID | 61997 |
| Currency | GEN |
| Explorer | explorer-studio-dev.genlayer.com (opens in a new tab) |
| Faucet | Built-in — use the 💧 button in the account selector |
Use the matching release-candidate SDK or CLI and its explicit studioDevnet / studio-dev network preset. Do not relabel the stable studionet preset: the environments have different chain IDs and deployments. If studio-next.genlayer.com is enabled as a browser alias for this same environment, integrations should still use the canonical studio-dev.genlayer.com/api RPC.
Localnet
Local development with full control. Requires GenLayer Studio or GLSim.
| Setting | Value |
|---|---|
| GenLayer RPC | http://localhost:4000/api |
| Chain ID | 61127 |
| Currency | GEN |
| Explorer | Bundled with Studio at http://localhost:8080 |
| Faucet | Built-in — use the 💧 button in the account selector |
GenLayer Chain (L2)
The underlying chain that GenLayer runs on. From consensus v0.6 it is an Arbitrum Orbit chain; the endpoint below is the pre-v0.6 testnet chain that Asimov and Bradbury use until they upgrade. GEN is its native currency, so balances and gas are in GEN. You typically don't need to interact with this directly — the GenLayer RPC passes through all eth_* calls. But if you need direct L2 access (e.g., token transfers, contract debugging at the EVM level), you can add this chain to your wallet.
| Setting | Value |
|---|---|
| RPC | https://rpc.testnet-chain.genlayer.com |
| Chain ID | 4221 |
| Currency | GEN |
| Explorer | explorer.testnet-chain.genlayer.com (opens in a new tab) |
Network Comparison
| Bradbury | Asimov | Studionet | Studio dev | Localnet | |
|---|---|---|---|---|---|
| Purpose | Production-like testing | Infrastructure testing | Hosted stable dev | Next-stack RC validation | Local dev |
| Setup | None | None | None | Matching RC tooling | Docker or GLSim |
| Persistence | Persistent | Persistent | Temporary | Temporary; resets expected | Local only |
| LLM execution | Real models | Real models | Real models | Real models | Configurable |
| Faucet | Available (opens in a new tab) | Available (opens in a new tab) | Built-in | Built-in | Built-in |
Recommended Flow
- Start on Studionet — zero setup, open studio.genlayer.com (opens in a new tab)
- Use Studio dev only for release-candidate validation — open studio-dev.genlayer.com (opens in a new tab) with the matching RC tooling
- Move to Localnet — when you need full control and fast iteration
- Deploy to Bradbury — when ready for production-like testing with real AI workloads