Network Configuration

The GenLayer CLI stores a network alias, then resolves the current RPC, chain ID, explorer, and consensus contract addresses from the matching network definition. Keeping the alias explicit prevents a transaction intended for a release-candidate deployment from being signed for the stable Studio chain.

For the complete endpoint and wallet table, see Networks.

Built-in networks

genlayer network list
genlayer network set localnet
genlayer network info

The stable built-in aliases are:

The v0.123 / Consensus v0.6 release-candidate tooling adds studio-dev, backed by the JavaScript SDK's studioDevnet chain definition:

genlayer network set studio-dev
genlayer network info

It resolves to https://studio-dev.genlayer.com/api, chain ID 61997.

Localnet

Initialize and start the local stack:

genlayer init
genlayer up
genlayer network set localnet

Localnet defaults to http://localhost:4000/api and chain ID 61127. It is the right choice for validator configuration, database resets, custom providers, and fast repeatable development.

Hosted Studio environments

Use studionet for the stable hosted experience and studio-dev only when validating the next release candidate.

# Stable hosted Studio
genlayer network set studionet
genlayer deploy --contract contracts/my_contract.py
 
# v0.123 / v0.6 release-candidate preview
genlayer network set studio-dev
genlayer deploy --contract contracts/my_contract.py

Both have browser faucets. Studio-dev is temporary: expect resets and do not depend on its state for durable deployments. If studio-next.genlayer.com points at the same preview, treat it as a web alias and keep the canonical SDK/RPC target on Studio-dev.

Public testnets

Use Bradbury for production-like contract testing and Asimov for infrastructure-oriented testing:

genlayer network set testnet-bradbury
genlayer deploy --contract contracts/my_contract.py

Get test GEN from the testnet faucet (opens in a new tab).

Custom deployment profiles

For a deployment that is not bundled with the CLI, create a named profile from a built-in base and override its deployment data. The base supplies the compatible client behavior; explicit overrides identify the actual chain.

genlayer network add my-preview \
  --base studionet \
  --rpc https://example.net/api \
  --chain-id 62001 \
  --deployment ./deployments.json \
  --explorer https://explorer.example.net
 
genlayer network set my-preview
genlayer network info

The CLI also accepts explicit consensus-address overrides. Run genlayer network info before funding or signing to verify the effective RPC, chain ID, explorer, and contract addresses.

Recommended workflow

1. Develop and profile contract behavior on Localnet.
2. Use stable Studionet for quick hosted collaboration.
3. Use Studio-dev only when the application must validate the release-candidate stack.
4. Deploy to Bradbury for persistent, production-like testnet validation.

Next steps

• CLI Deployment
• Deploy Scripts
• GenLayer Studio
• Fee Profiling and Estimation