W3.io Logo
Menu

C1 Option · Avalanche Subnet

Deploy W3's settlement contracts to a dedicated Avalanche Subnet with EVM execution.

TL;DR: Avalanche Subnet = your own EVM blockchain using Avalanche's validators and Snowman++ consensus. We deploy the same three smart contracts (WorkflowRegistry, ValidatorRegistry, AttestationLog) as Ethereum L1, but with cheaper gas, faster finality (~2s), and a potential partnership deal.

What Is a Subnet?

Subnet = separate blockchain that reuses Avalanche's validator network but runs its own VM (virtual machine). Think "Ethereum L1, but you pick which validators secure it and what gas token it uses."

Consensus

Snowman++ (Avalanche's PoS). Validators vote on blocks.

VM Options

Subnet-EVM (Solidity), custom Rust VM, or WASM runtime.

Gas Token

Could be AVAX, W3, or any ERC-20.

Validator Set

Subset of Avalanche validators who also validate your Subnet.

For W3: We'd launch a Subnet running Subnet-EVM (Ethereum-compatible), so we can deploy the exact same Solidity contracts as Ethereum L1. State lives on-Subnet. Validators commit attestations to these contracts instead of Ethereum mainnet.

Smart Contracts (Same as Ethereum L1)

WorkflowRegistry

  • Store workflow hash, manifest CID, quorum size.
  • Emit WorkflowActivated events.
  • Authority enforcement (multisig or DAO).

ValidatorRegistry

  • Validator staking (AVAX or W3 token).
  • BLS public keys for aggregated signatures.
  • Slashing + heartbeat tracking.

AttestationLog

  • Append-only log of trigger + step attestations.
  • Store transcript roots + aggregated BLS sigs.
  • Indexed by explorers for audit.

Key difference from Ethereum L1: Gas is ~100x cheaper, and blocks finalize in ~2s instead of ~12s (slot) + ~13 min (finality). Otherwise, implementation is identical.

Where State Lives

On-Subnet (W3 Settlement State)
Workflow Definitions
WorkflowRegistry contract (Solidity state).
Validator Set
ValidatorRegistry contract (stakes, keys, status).
Attestation History
AttestationLog contract (append-only proofs).
W3 Token (if native)
ERC-20 deployed on Subnet, or native gas token.

On Avalanche C-Chain (Optional Bridge)

W3 Token Liquidity: If W3 token is ERC-20 on C-Chain (main Avalanche), we'd bridge supply to/from Subnet for DeFi integrations.

Settlement Proofs: Could mirror AttestationLog commitments to C-Chain for public visibility (similar to Ethereum L1 posting).

Offchain (Execution Layer)

Workflow execution (E5→E1) still happens offchain in validators' runtimes. Only C2 (registries) and C3 (attestations) touch the Subnet. Same split as Ethereum L1.

Tokenomics

What AVAX Pays For

  • Validator bonding on the Primary Network (2000 AVAX minimum).
  • Subnet transaction fees if we keep Subnet-EVM denomination.
  • Security inheritance from Avalanche staking + slashing.

What W3 Token Pays For

  • Workflow execution + attestation incentives.
  • Protocol governance (parameter votes, upgrades).
  • Bridged liquidity rewards or sequencer tips.

Dual-token by default (AVAX for validator weight, W3 for protocol utility). Could migrate to single-token once W3 token is accepted as Subnet gas.

Trade-offs

What You Get

  • Battle-tested Snowman++ (fast deterministic finality).
  • Validator marketplace (existing Avalanche stakers).
  • Customizable VM + fee logic for workflows.
  • Native bridge to Avalanche ecosystem liquidity.

What It Costs

  • Need to attract validators to an additional Subnet.
  • Dual-fee UX unless W3 token becomes gas.
  • Operational burden: upgrade coordination with Avalanche tooling.
  • Regulatory/treaty work if partnership terms include rev-share.