Deploy-Ready · Not Yet Live
KUMPLY Compliance L1
The first Avalanche L1 where only KYB-verified institutions can validate. Every block is signed by a licensed entity — compliance baked into consensus.
All architecture, contracts, genesis and tests are complete
The L1 is deploy-ready: the KumplyValidatorSetManager contract is written and tested (27 tests passing), genesis is configured, and the deployment script is one command. We are coordinating with founding institutional validators (Bankaool, Arkangeles) before going live on Fuji.
Chain Identity
- NameKUMPLY Compliance L1
- Chain ID
43210 - Gas Token
KMP - VM
Subnet-EVM v0.7.0 - Block Time
2s - Consensus
Snowman (k=20, β=15)
Endpoints & Contracts
- RPC (planned)
https://kumply-l1.rpc.kumply.io/ext/bc/{blockchainID}/rpc - Block Explorer
https://kumply-l1.subnets.avax.network - AttestationStore
0x9Bbb0797EA92277c268fe7E45BdB16b70E787d76 - Validator Set ManagerDeploy-Ready (.sol)
- Warp / ICMEnabled at genesis
- ICTTPlanned · Phase 2
Validator Architecture (ACP-77 + ACP-99)
Validator registration flows through the KumplyValidatorSetManager contract, which enforces a Tier 4 (KYB) attestation as a prerequisite. State changes propagate to the P-Chain via Avalanche Warp Messages.
Validator Set (ACP-77 + ACP-99)
KYB-verified institutions only · 5–21 active validators
│ initializeValidatorRegistration(nodeID, 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 Tier 4 (Business / KYB) attestation in the KUMPLY AttestationStore. If the attestation expires, the validator is automatically removed by the contract — anyone can trigger the purge.
B
Bankaool
Digital bank · CNBV regulated
Tier 4 · KYBCommitted
A
Arkangeles
Venture capital · LatAm
Tier 4 · KYBCommitted
K
KUMPLY Protocol
Treasury validator
Tier 4 · KYBCommitted
L
LatAm DeFi Alliance
Regional consortium
Tier 4 · KYBInvited
I
Institutional TBD #5
Banking partner
Tier 4 · KYBIn Talks
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
Only KYB-verified institutions validate. Every block is signed by a licensed entity — the network itself becomes a regulatory artifact.
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
Attestations propagate to every Avalanche L1 natively. No bridges, no oracles, no third-party trust assumptions.
04
Self-Healing Validator Set
When a validator's KYB expires, anyone can call disableExpiredValidator(). The network removes non-compliant validators without admin intervention.
Deployment Artifacts
Everything required for deployment is committed and audited. One command spins the L1 up on Fuji.
Contract
KumplyValidatorSetManager.sol
Genesis
contracts/l1/genesis.json
L1 config
contracts/l1/l1-config.json
Deploy script
contracts/scripts/deploy-l1.sh
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.