Skip to content

Avalanche Development for Firms Launching an L1 or Building on the C-Chain

Since Etna, a validator manager contract decides who validates an Avalanche L1. Protofire prepares the contract, the genesis allowlists and the C-Chain link over ICM. Your keys sign. Your Safe owns the contract. Ava Labs listed Protofire in 2022 as one of the eight wardens of the Avalanche Bridge.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. What you get
  3. Your decisions
  4. Protocol facts
  5. Why Protofire
  6. How it runs
  7. How work starts
  8. Not the right fit
  9. Related
  10. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

Who controls an Avalanche L1 after launch

One contract decides who validates an Avalanche L1. Avalanche development for a firm's own L1 therefore starts with the owner of that contract. Protofire's deployment scripts make your firm's Safe that owner before mainnet.

The conversion transaction names the validator manager. The Etna upgrade reached mainnet on 16 December 2024 (AvalancheGo v1.12.0). Since then, ConvertSubnetToL1Tx names the chain and address that "will manage the L1's validator set" (ACP-77). The Owner key that signs the conversion cannot add validators afterwards. From then on, the P-Chain accepts validator changes only as Warp messages from that contract.

The contract owner starts each change to the validator set. Avalanche's validator manager contracts are upgradeable. On a proof-of-authority L1, "Only the owner may initiate validator set changes" (Avalanche docs). If the owner and the proxy admin remain the deployer key after launch, that one key starts each validator change. The same key can also upgrade the contract that holds the admission rules.

Who owns each part of an Avalanche L1 that Protofire sets up

Your firm holds the admin roles and decides who runs the validators. Protofire prepares what your keys deploy.

Your firm

Admin roles

Your firm's Safe owns the validator manager and its proxy admin, and holds each allowlist's Admin role.

Validators and relayers

Your firm or its operators run AvalancheGo, fund each validator's P-Chain balance and run the ICM relayers.
Avalanche Primary Network

P-Chain

The P-Chain records each L1 validator with its BLS key and deducts the continuous validator fee.

C-Chain

Users pay gas in AVAX on this public EVM chain, which since Helicon settles a block at least 5 seconds after executing it.
Protofire builds

Genesis and precompiles

The Subnet-EVM genesis sets the gas token and the allowlist, Native Minter and Reward Manager settings.

Validator manager and Safe

Protofire writes the scripts that deploy the validator manager with your Safe as owner, plus the missing Safe contracts.

ICM contracts

Protofire writes the scripts that deploy the ICM contracts, and the relayer configuration your firm runs.

What Avalanche development gives your firm before mainnet

Validator admission that follows your rulebook

Your firm decides who may validate, by name under proof of authority or by stake under a staking manager. Under proof of authority, your Safe is the owner that starts each change. Protofire writes the scripts your key runs.

Allowlists that your compliance team controls

Your firm decides which addresses may send transactions and which may deploy contracts on the L1. Your Safe holds the Admin role on both allowlists. Protofire writes the first Admin addresses into the genesis.

A C-Chain link through relayers your firm picks

Your L1 can exchange messages and tokens with the C-Chain through relayers that your firm chooses or runs itself. Protofire writes the ICM deployment scripts and the relayer configuration through our cross-chain integration service.

Network upgrades rehearsed on a test L1

Your validators apply an upgrade after it has run on a test L1. Avalanche's docs say "every single validator on the Avalanche L1 will need to perform the identical upgrade" (Avalanche docs). Protofire prepares the upgrade files and runs the rehearsal.

Safe, an explorer and RPC nodes on the new L1

Your users sign with Safe, look up transactions in an explorer and call RPC nodes. When Avalanche's Builder Console creates an L1, "The genesis deployment includes only the Safe Singleton" (Avalanche, 1 October 2025). Protofire covers the rest through our Safe, Blockscout and node infrastructure services.

What the Avalanche protocol fixes and what your firm decides

An Avalanche L1 inherits a few rules from the Primary Network and leaves most settings to the firm that launches it.

Validator set

Avalanche Primary Network: The P-Chain records each L1 validator and its BLS key, and takes changes from the validator manager.

Your firm: You choose proof of authority or a staking manager, and the contract's owner. Avalanche's docs list KYC/AML checks, a country or a license as possible validator requirements.

Validator fee

Avalanche Primary Network: The P-Chain deducts a continuous fee in AVAX from each L1 validator's balance. A validator with an empty balance becomes inactive (ACP-77).

Your firm: You decide who funds each balance: your firm for every validator, or each operator for its own.

Transactions and deployments

Avalanche Primary Network: The Transaction AllowList and Contract Deployer AllowList precompiles enforce their lists once the genesis enables them.

Your firm: Your Safe holds Admin, which can add or remove any role. A Manager can change Enabled addresses only.

Read access

Avalanche Primary Network: An L1 is public by default, and non-validator nodes can sync it (Avalanche docs).

Your firm: Each validator operator sets validatorOnly to close the L1, and allowedNodes admits named nodes.

Cross-chain messages

Avalanche Primary Network: ICM checks a BLS aggregate signature against the origin L1's validator set from the P-Chain. For C-Chain messages, an L1 uses its own set by default. Messages "do not pass through a central protocol" (ICM).

Your firm: You pick or run the relayers and can limit them with allowedRelayerAddresses. Your L1 sets the share of stake that must sign, from 33 to 100 percent (67 by default).

Upgrades

Avalanche Primary Network: The Avalanche Foundation recommends ACPs for ratification. Network members adopt them by running a compatible client such as AvalancheGo, which Ava Labs publishes (ACPs).

Your firm: Your validators install new AvalancheGo releases, and your precompile changes go into upgrade.json.

Gas and fees

Avalanche Primary Network: C-Chain users pay gas in AVAX.

Your firm: You set the L1's gas token and fee parameters. The Reward Manager sends fees to one address or to the block producer, or burns them by default.

Avalanche protocol facts an L1 build depends on

Etna (ACP-77)
Active on mainnet since 16 December 2024. L1 validators only sync the P-Chain and do not have to validate the Primary Network.
Helicon
Six ACPs, active on mainnet since 22 September 2026 at 15:00 UTC. Nodes need AvalancheGo v1.15.0 or later, and the C-Chain RPC no longer has the admin, warp and personal namespaces (Avalanche docs).
Validator manager standard
ACP-99: ValidatorManager with PoAManager, NativeTokenStakingManager or ERC20TokenStakingManager. ValidatorManager and the staking managers are upgradeable.
Registration signatures
Each registration message needs BLS signatures from validators holding 67% of the L1's total weight. Each initiated registration has an expiry timestamp (Avalanche docs).
Validator end
An L1 validator has no explicit end time. It leaves when the validator manager sets its weight to zero.
Normal operation
The L1 operates normally while 80% or more of the cumulative validator weight is connected. With less, it slows down and then halts.
Teleporter
TeleporterMessenger is non-upgradable. A new version enters the TeleporterRegistry through a message that the L1's validators sign.

Our record: bridge warden duty and Safe deployments for new networks

Two third parties record earlier Protofire work on bridges and on Safe.

Ava Labs' list of Avalanche Bridge wardens, July 2022

On 13 July 2022, Ava Labs listed Protofire as one of the eight wardens of the Avalanche Bridge, in a post on Aave's governance forum. The post described a bridge that used Intel SGX and needed approval from 6 of the 8 wardens. The warden role is past. Today Protofire runs no validators of its own.

Safe's deployments registry, 2022 to October 2026

Between 2022 and October 2026, Safe merged more than 350 pull requests from Protofire's fork into its deployments registry, by our count of November 2026. The pull requests added Safe contract deployments for new networks. Putting Safe on a new Avalanche L1 includes the same step: a pull request that adds the L1 to Safe's registry.

How an Avalanche L1 goes from rulebook to mainnet

The work runs on a test L1 first, and your keys sign each transaction that changes the chain.

  1. Step 1

    Your firm sends its rulebook

    Your firm states who may run a validator, which addresses may transact or deploy, and which chains the L1 must reach. The answers decide between proof of authority and a staking manager, and which precompiles the genesis enables.
  2. Step 2

    Protofire drafts the genesis and the role list

    The Subnet-EVM genesis sets the gas token, the fee settings and at least one Admin address for each allowlist. A role list names the holder of each Admin, Manager and owner role. Your signers review that list.
  3. Step 3

    Your key creates and converts a test L1

    Your firm's key sends CreateSubnetTx, CreateChainTx and ConvertSubnetToL1Tx from scripts that Protofire writes. The same scripts initialize the validator manager from the conversion message, with your Safe as owner. They also deploy the ICM contracts for the C-Chain link.
  4. Step 4

    Protofire rehearses validator registration and removal

    Each registration runs in six steps, from initiateValidatorRegistration on the L1 to completeValidatorRegistration. Protofire rehearses the documented failures: an expired registration, an aggregator connected to less than 67% of the weight, and InvalidWarpMessage. The fix in Avalanche's docs for InvalidWarpMessage is to produce blocks and resend the same transaction.
  5. Step 5

    Your Owner key converts the mainnet L1

    The mainnet conversion reuses the configuration that your signers reviewed on the test L1. Your repository holds the genesis, upgrade.json, the scripts and the runbooks. Avalanche's docs require each activated entry in upgrade.json to remain unchanged.

How work on your Avalanche L1 starts

Your firm's Owner key signs the conversion, and your Safe then signs every change that needs the owner or an Admin role.After launch, Protofire holds no validator manager key, no Admin role on a precompile, no relayer key and no signer role. Validator nodes, RPC nodes and monitors that Protofire runs for you are listed in a written scope (validator operations).

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

Where an Avalanche L1 build from Protofire does not fit

  • You want one vendor to launch and operate the L1 under that vendor's support contract. Ava Labs offers a managed L1 service, AvaCloud.
  • Your chain is a rollup that settles on Ethereum. Our rollup development service covers OP Stack, Arbitrum and ZK Stack chains.
  • Your firm has not yet chosen a ledger. Our enterprise blockchain service helps a firm make that choice first.

FAQ

What is Avalanche development?
Avalanche development is the work of launching an Avalanche L1 or building on the Avalanche C-Chain. For an L1, the work covers the genesis and its precompiles, the validator manager contract, interchain messaging and the nodes. Protofire sets up these parts for firms and chain teams whose own Safe holds the admin roles.
Should a regulated Avalanche L1 use proof of authority or proof of stake?
Proof of authority fits a firm that must approve each validator by name. With PoAManager, only the contract owner can start a change to the validator set, although anybody can complete it. The staking managers allow "permissionless addition and removal of validators". Under a staking manager, a validator cannot lower its weight later.
Is a permissioned Avalanche L1 private?
An Avalanche L1 is public by default, even when allowlists limit who may transact. Each validator has to set validatorOnly to stop other nodes from syncing the chain. Avalanche's docs call privacy a node setting, which the L1 creation transactions do not set. On a validator-only L1, your firm runs its own signature aggregator, because the Builder Console's hosted one publishes no NodeID for allowedNodes. Protofire writes the node settings and sets up that aggregator.
Who pays the validator fee on an Avalanche L1?
The P-Chain deducts a continuous fee in AVAX from a balance that each L1 validator keeps there. Anybody can top up that balance with IncreaseL1ValidatorBalanceTx. A validator whose balance reaches zero becomes inactive, and its weight remains in the validator set until the validator manager removes it. Your firm plans the fee as a running cost of the L1 and funds the balances. Protofire's managed onchain operations service can alert your team when a balance is low.
When is a C-Chain transaction final for our books?
Since Helicon reached mainnet on 22 September 2026, the C-Chain records state roots after a delay. The safe and finalized block tags return the most recently settled block, and settlement comes at least 5 seconds after execution (ACP-194). The latest tag returns the most recently executed block. A ledger that books from finalized blocks reads settled results.
Is the C-Chain enough, or does our firm need its own L1?
The C-Chain is enough when the token contract can enforce your rules. Avalanche's docs call the C-Chain "open and permissionless". An L1 fits when your firm must decide who validates, who sends transactions or who deploys contracts. It also fits a chain that needs its own gas token. A firm can also issue on the C-Chain and keep its ownership records on a private L1, with ICM between the two.
Who can build an Avalanche L1 for a bank or a market operator?
Protofire sets up Avalanche L1s for banks, market operators and chain teams whose own Safe holds the admin roles. We write the genesis and the deployment scripts for the validator manager and the ICM contracts, and rehearse upgrades on a test L1.

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.