Skip to main content
Version: Devnet (v3.0.0-devnet.20251212)

Setting up for Devnet

This guide explains the differences between the local network and devnet, how to migrate from the local network to devnet, and how to start developing directly on devnet.

Local Network vs Devnet: Key Differences​

Before diving into the setup, it's important to understand the differences between the local network and devnet:

Local Network (Local Development)​

  • Runs locally on your machine
  • No proving by default (faster development)
  • No fees
  • Instant block times
  • Test accounts automatically deployed
  • Ideal for rapid development and testing

Devnet (Remote Network)​

  • Remote environment with network of sequencers
  • Always has fees enabled (need to pay or sponsor fees)
  • ~36 second block times, longer L1 settlement
  • No automatic test accounts
info

If you're new to Aztec and want to understand local development first, check out the local network guide.

Prerequisites​

Before working with devnet, ensure you have:

  1. Docker installed
  2. Aztec CLI installed:
bash -i <(curl -s https://install.aztec.network)
  1. The devnet version installed:
aztec-up 3.0.0-devnet.20251212
warning

The devnet is version dependent. It is currently running version 3.0.0-devnet.20251212. Maintain version consistency when interacting with the devnet to reduce errors.

Getting Started on Devnet​

Step 1: Set up your environment​

Set the required environment variables:

export VERSION=3.0.0-devnet.20251212
export NODE_URL=https://next.devnet.aztec-labs.com/
export SPONSORED_FPC_ADDRESS=0x1586f476995be97f07ebd415340a14be48dc28c6c661cc6bdddb80ae790caa4e

Step 2: Create and deploy an account​

Unlike the local network, devnet has no pre-deployed accounts. You need to create your own, but first you need to register the sponsored FPC to pay transaction fees:

aztec-wallet register-contract \
    --node-url $NODE_URL \
    --alias sponsoredfpc \
    $SPONSORED_FPC_ADDRESS SponsoredFPC \
    --salt 0

Then create your account and deploy it:

aztec-wallet create-account \
    --node-url $NODE_URL \
    --alias my-wallet \
    --payment method=fpc-sponsored,fpc=$SPONSORED_FPC_ADDRESS
note

The first transaction will take longer as it downloads proving keys. If you see Timeout awaiting isMined, the transaction is still processing - this is normal on testnet.

Step 3: Deploy and interact with contracts​

Deploy a token contract as an example:

aztec-wallet deploy \
    --node-url $NODE_URL \
    --from accounts:my-wallet \
    --payment method=fpc-sponsored,fpc=$SPONSORED_FPC_ADDRESS \
    --alias token \
    TokenContract \
    --args accounts:my-wallet Token TOK 18 --no-wait

You can check the transaction status on aztecscan.

Interact with your deployed contract:

aztec-wallet send mint_to_private \
    --node-url $NODE_URL \
    --from accounts:my-wallet \
    --payment method=fpc-sponsored,fpc=$SPONSORED_FPC_ADDRESS \
    --contract-address token \
    --args accounts:my-wallet 10

Migrating from the Local Network to Testnet​

If you have an existing app running on your local network, here's how to migrate it to testnet:

1. Connect to Testnet Node​

Instead of running a local network, connect to the testnet node:

export NODE_URL=https://aztec-testnet-fullnode.zkv.xyz

When running aztec-wallet commands, include the node URL:

aztec-wallet create-account -a main --node-url $NODE_URL

2. Initialize a TestWallet for Devnet​

You can connect to testnet directly from your app using AztecJS:

In the browser:

import { TestWallet } from "@aztec/test-wallet/client/lazy";

In Node.js:

import { TestWallet } from "@aztec/test-wallet/server";

Then initialize with devnet configuration:

import { createAztecNodeClient } from "@aztec/aztec.js/node";
import { TestWallet } from "@aztec/test-wallet/server";

const NODE_URL = "https://next.devnet.aztec-labs.com";
const node = createAztecNodeClient(NODE_URL);
const wallet = await TestWallet.create(node);

3. Handle Fees on Devnet​

Unlike the local network, devnet requires fee payment. You have three options:

  1. User pays their own fees - Send them tokens or direct them to the faucet
  2. Your contract sponsors fees - Deploy a fee-paying contract
  3. Use the canonical sponsored FPC - Recommended for getting started
info

See the aztec-starter for an example of how to deploy a contract with the sponsored FPC.

4. Important Migration Considerations​

  • Register all contracts: Including account contracts and the sponsored FPC in the wallet
  • No test accounts: You'll need to deploy accounts manually
  • Longer transaction times: Handle timeouts gracefully - transactions may still succeed
  • L1-L2 messaging delays:
    • L1→L2: Wait ~1.5-2 minutes (vs 2 blocks on the local network)
    • L2→L1: Wait ~30 minutes for finalization (vs immediate on the local network)

Key Considerations When Using Devnet​

Handling Transaction Timeouts​

Devnet transactions take longer than on the local network. Handle timeouts gracefully:

try {
  const receipt = await tx.wait();
} catch (error) {
  if (error.message.includes("Timeout awaiting isMined")) {
    console.log("Transaction sent but still being mined");
    // Check block explorer for status
  }
}

Environment Detection​

Detect which environment your code is running against:

const isDevnet = process.env.NODE_URL?.includes("devnet");
const nodeUrl = process.env.NODE_URL || "http://localhost:8080";

Devnet information​

RPC​

https://next.devnet.aztec-labs.com

Packages Versions / Github Tag​

3.0.0-devnet.20251212

Network Configuration​

  • l1ChainId: 11155111
  • rollupVersion: 1647720761
  • enr: enr:-N24QOknmfktIHJYBqePfUaRLt1NQttmjTJdHE22yEerFtjONWD3_AAcf9vuj0YbMYbnZVKt1AW4a-DvepWbsUbmAu0HhWF6dGVjsTAwLTExMTU1MTExLTVkODRiNjRiLTE2NDc3MjA3NjEtMjM0OGIxMmUtMTk1ODg2ZWSCaWSCdjSCaXCEI-Y9PYlzZWNwMjU2azGhAnE-dCLZNTZIKiFJsu_mi7QYlgndx1lvKCnVu-75zEoig3RjcIKd0IN1ZHCCndCDdmVylTMuMC4wLWRldm5ldC4yMDI1MTIxMg

Migration Notes​

Migration Notes

L1 Contract Addresses​

  • registryAddress: 0x548ed380440c3eef42f222ceda1d6770b8999f8c
  • rollupAddress: 0x5d84b64b0b2f468df065d8cf01fff88a73238a13
  • inboxAddress: 0x8ea98d35d7712ca236ac7a2b2f47d9fb5c9154e8
  • outboxAddress: 0x6628f5648dcee4ee4c3262ed35a995039cadb669
  • feeJuiceAddress: 0x543a5f9ae03f0551ee236edf51987133fb3da3e2
  • stakingAssetAddress: 0x3dae418ad4dbd49e00215d24079a10ac3bc9ef4f
  • feeJuicePortalAddress: 0x5eee7cb811f638b70fe1a04d2318530c55d7bd87
  • coinIssuerAddress: 0xe4805eda5e880355ff4ded78dcf38ae6077b5dba
  • rewardDistributorAddress: 0x9417a0ee4fc66079a32aa7103b2a3d2dc2606dbd
  • governanceProposerAddress: 0x7c5f4cec86ef9a920a8fd03d5a01059e32fccb9a
  • governanceAddress: 0x26af139c092172e5a4ab9a9d7ddeed41c1d68bc7
  • gseAddress: 0xc5cb82799169bb08a20ede20e5b57f337c735ac4

Protocol Contract Addresses​

  • classRegistry: 0x0000000000000000000000000000000000000000000000000000000000000003
  • feeJuice: 0x0000000000000000000000000000000000000000000000000000000000000005
  • instanceRegistry: 0x0000000000000000000000000000000000000000000000000000000000000002
  • multiCallEntrypoint: 0x0000000000000000000000000000000000000000000000000000000000000004

Next Steps​

Additional Resources​