OpenChainGraph Suite · ART-495 · Avalanche Evergreen Permissioning

Evergreen Permissioning-Control Classifier

Takes your genesis precompile configuration and validator-manager mode and classifies six supervisory controls as protocol-enforced, application-enforced, or absent — with a named gap register. This answers a different question than the segregation-of-duties matrix checker: not who holds conflicting power, but where the control lives at all, or whether it exists.

Protocol vs Application Control Gap Register
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only, e.g. opaque control identifiers.
Load a Preset

Presets fill the genesis configuration below — nothing runs until you click Classify Controls.

Record each precompile's genesis activation state exactly as the genesis declares it. An undeclared precompile is not the same as an inactive one — leaving a control undeclared surfaces as a named judgment call, never a silent guess.

Genesis Precompile Configuration
TX AllowList activated?
Contract Deployer AllowList activated?
Native Minter activated?
Fee Manager activated?
Reward Manager activated?
Validator-manager mode
Application-Level Controls (for any precompile marked inactive above)

Declare whether an off-chain or smart-contract policy substitutes for a precompile that genesis does not activate. Leave "Not declared" if you have not confirmed either way — that surfaces as a judgment call rather than a false absent.

Transaction permissioning
Contract deployment permissioning
Native asset issuance control
Fee policy control
Reward distribution control
Validator set membership control
Control Classification
Gap Register
Judgment Required
Execution Hash (SHA-256)

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

Run the AINumbers MCP tool `classify_avax_permissioning_controls`. Task: Classify six Evergreen supervisory controls -- transaction permissioning, contract deployment permissioning, native asset issuance, fee policy, reward distribution, and validator set membership -- as protocol-enforced, application-enforced, or absent, from caller-transcribed genesis precompile configuration and validator-manager mode.
Call it with arguments: {"policy_parameters":{"precompiles":{"txallowlist":{"activated":true},"deployerallowlist":{"activated":true},"nativeminter":{"activated":false},"feemanager":{"activated":false},"rewardmanager":{"activated":false}},"application_controls":{"fee_policy_control":true,"native_asset_issuance_control":false,"reward_distribution_control":false},"validator_manager_mode":"poa"}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-495-avax-permissioning-control-classifier.html#p=v1.H4sIAAAAAAAA_wFdAaL-eyJwcmVjb21waWxlcyI6eyJ0eGFsbG93bGlzdCI6eyJhY3RpdmF0ZWQiOnRydWV9LCJkZXBsb3llcmFsbG93bGlzdCI6eyJhY3RpdmF0ZWQiOnRydWV9LCJuYXRpdmVtaW50ZXIiOnsiYWN0aXZhdGVkIjpmYWxzZX0sImZlZW1hbmFnZXIiOnsiYWN0aXZhdGVkIjpmYWxzZX0sInJld2FyZG1hbmFnZXIiOnsiYWN0aXZhdGVkIjpmYWxzZX19LCJhcHBsaWNhdGlvbl9jb250cm9scyI6eyJmZWVfcG9saWN5X2NvbnRyb2wiOnRydWUsIm5hdGl2ZV9hc3NldF9pc3N1YW5jZV9jb250cm9sIjpmYWxzZSwicmV3YXJkX2Rpc3RyaWJ1dGlvbl9jb250cm9sIjpmYWxzZX0sInZhbGlkYXRvcl9tYW5hZ2VyX21vZGUiOiJwb2EifTiGWnVdAQAA