OpenChainGraph Suite · Digital-Asset Rails

Avalanche Evergreen L1 Onboarding

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.
Reading mode (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. The permissioning, segregation-of-duties, validator, and fee-runway checks each grade a separate facet of L1 readiness and are combined into one composite walkthrough.

Evergreen permissioning-control classifier > precompile segregation-of-duties check > validator change-control receipt > L1 continuous-fee runway model: composite Evergreen L1 onboarding walkthrough for a permissioned Avalanche L1.

OpenChainGraph · 4 Steps compliance mandate Hash-Anchored §4 chain_depth:4 Client-Side · Zero PII
Chain Topology: Permissioning Classifier → SoD Matrix Check → Validator Change-Control → Fee Runway Model
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Market Rationale
Buyer: issuer/institution standing up a permissioned Avalanche Evergreen L1, and the auditor evidencing its supervisory controls
Forcing function: ACP-77 replaced the fixed 2000 AVAX stake with a continuous P-Chain fee, and Evergreen subnets ship precompile-based permissioning whose control coverage is easy to leave undocumented
Chain Stages · 4 Steps
1 ROOT node
Evergreen Permissioning-Control Classifier art-495-avax-permissioning-control-classifier
protocol-enforced, application-enforced and absent control classification (with gap register) feeds Stage 2 precompile segregation-of-duties check
↓
2 D2 node
Segregation-of-Duties Matrix Checker art-459-sod-matrix-check
clean/conflict SoD verdict over the application-enforced roles feeds Stage 3 validator change-control receipt
↓
3 D3 node
Validator Change-Control Receipt art-497-validator-change-control-receipt
authorization chain, quorum verdict and exceptions for the validator-set change feed Stage 4 L1 continuous-fee runway model
↓
4 TERMINAL node
L1 Continuous-Fee Runway Model art-496-l1-continuous-fee-runway
annual TCO, months_to_depletion and refill_amount_required complete the Evergreen L1 onboarding walkthrough
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition, no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: The treasury keeps a fixed AVAX balance for validator fees. Does the runway clear our 24 month target at the current fee curve?
Run the AINumbers MCP tool `run_chain` with {"chain":"avax-evergreen-l1-onboarding"} and read `art-496-l1-continuous-fee-runway.runway_flag`.
Re-run with `inputs` for `art-496-l1-continuous-fee-runway`, reusing the values that result echoed, with `current_balance` set to 60000. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/avax-evergreen-l1-onboarding.html