Chain Registered on Fuji · Activation Pending
KUMPLY Compliance L1
An Avalanche L1 designed so validators must hold a KUMPLY attestation (Tier 4 or higher today). Not activated yet.
Chain Registered on Fuji · Validator Activation Pending
The KUMPLY chain (ID 43210, KMP gas token) is registered on the Fuji P-Chain with its genesis committed, and the ACP-99 KumplyValidatorSetManager is deployed and verified on C-Chain with a dedicated test suite. It is not initialized and has no validators yet. Next step: ACP-77 conversion and first validator node activation. A fix that restricts registration to exactly Tier 4 is already in the code and ships with the manager's redeploy before the L1 is activated.
Validator Architecture (ACP-77 + ACP-99)
Validator registration flows through the KumplyValidatorSetManager contract, which requires a valid attestation of Tier 4 (KYB) or higher. A fix that restricts registration to exactly Tier 4 is already in the code and ships with the manager's redeploy before the L1 is activated. State changes propagate to the P-Chain via Avalanche Warp Messages.
Validator Set (ACP-77 + ACP-99)
Target: 5–21 validators · 0 active (not activated)
│ initiateValidatorRegistration(nodeID, blsPublicKey, …, weight)
▼
KumplyValidatorSetManager.sol
require: attestationStore.verify(msg.sender).tier >= 4
│ Warp Message (ACP-77 §"L1 Validator Manager")
▼
P-Chain · canonical L1 validator set sync
│ Snowman++ consensus
▼
KUMPLY L1 (Subnet-EVM, KMP gas) · 2s blocks · ICM enabled
Founding Validators
Each validator must hold a valid attestation of Tier 4 or higher when registering. If it expires or is revoked, anyone can call disableExpiredValidator() to start its removal; removal is not automatic. A still-valid downgrade can only be removed by the admin until the fix ships with the redeploy.
K
KUMPLY Protocol
Treasury validator · no node running yet
NodeID-EzGaipqomyK9UKx9DBHV6Ky3y68hoknrF
Tier 4 · KYBCommitted
I
Institutional Slot 2
Digital bank · onboarding open
Tier 4 · KYBOpen Slot
I
Institutional Slot 3
Venture fund · onboarding open
Tier 4 · KYBOpen Slot
I
Institutional Slot 4
Regional consortium · onboarding open
Tier 4 · KYBOpen Slot
I
Institutional Slot 5
Banking partner · onboarding open
Tier 4 · KYBOpen Slot
Why a Dedicated L1?
The C-Chain works for today’s reads. Here is why we are building the Compliance L1 for institutional scale.
01
Compliant by Construction
Validators must hold a KUMPLY attestation (Tier 4 or higher today) to register. Compliance is designed into the validator set, not added as a policy on top.
02
Sub-Cent Compliance Reads
Predictable, near-zero fees for compliance lookups at institutional scale. No more gas spikes blocking enterprise integrations.
03
Cross-L1 via Warp + ICM
Planned: attestations propagated to other Avalanche L1s via Warp + ICM, with no bridges or third-party oracles. Not shipped yet.
04
Permissionless Validator Purge
When a validator's attestation expires or is revoked, anyone can call disableExpiredValidator(); no admin needed. Someone has to make that call.
Deployment Artifacts
Deployment artifacts are committed and reviewed against Ava Labs' reference code (not a formal audit). Activation also needs validator nodes and the ACP-77 conversion.
Contract
KumplyValidatorSetManager.sol
Genesis
contracts/l1/genesis.json
L1 config
contracts/l1/l1-config.json
Deploy script
contracts/scripts/deploy-l1.sh
Hardhat tests
Passing in CI
Network
Fuji testnet (initial)
Avalanche Community Proposals (ACPs)
KUMPLY L1 implements the latest Avalanche standards for sovereign L1s, dynamic validator management and Warp-based cross-chain messaging.