HIP-24: Hanzo Sovereign L1 Chain Architecture. Status Draft. Hanzo's own standard — read this before implementing against it.
Hanzo operates as a sovereign L1 chain on the Lux Network, meaning it maintains its own independent validator set rather than relying on primary network validation. This architecture provides Hanzo with full sovereignty over consensus parameters, validator economics, and network governance - essential for AI compute workloads requiring specialized infrastructure.
chain:
name: Hanzo
type: L1
chainId: 36963
ticker: AI
validation:
type: independent
minValidators: 5
stakingToken: AI
consensus:
engine: nova
parameters:
k: 20
alpha: 15
betaVirtuous: 15
betaRogue: 20
{
"config": {
"chainId": 36963,
"chainType": "L1",
"validatorSet": {
"type": "independent",
"minValidators": 5,
"stakingToken": "AI",
"minStake": "2000000000000000000000"
},
"consensus": {
"engine": "nova",
"parameters": {
"k": 20,
"alpha": 15,
"betaVirtuous": 15,
"betaRogue": 20
}
}
},
"timestamp": "0x0",
"gasLimit": "0xe4e1c0",
"alloc": {}
}
| Network | Chain ID | RPC Endpoint | |---------|----------|--------------| | Mainnet | 36963 | https://api.hanzo.ai/ext/bc/hanzo/rpc | | Testnet | 36962 | https://testnet.hanzo.ai/ext/bc/hanzotest/rpc |
Hanzo validators have specialized requirements beyond standard Lux validators:
validator:
hardware:
cpu: 32+ cores
ram: 128GB+
gpu: NVIDIA A100/H100 (for AI attestation)
storage: 2TB+ NVMe
software:
tee: SGX/TDX enabled
attestation: NVTrust compatible
staking:
minStake: 2000 AI
lockPeriod: 14 days
capabilities:
- AI model inference
- TEE attestation
- FHE key share management
As an L1, Hanzo transactions are validated by its own validator set:
User Transaction → Hanzo Chain → Hanzo Validators → Consensus → Finality
Benefits:
Tradeoffs:
Hanzo validators perform AI-specific operations:
// AI Mining precompile (0x0300)
type AIMiningConfig struct {
// ML-DSA signatures for quantum-safe attestation
SignatureScheme string `json:"signatureScheme"` // "ML-DSA-65"
// NVTrust verification for GPU compute
AttestationType string `json:"attestationType"` // "NVTrust"
// Reward calculation
PrivacyLevels []int `json:"privacyLevels"` // [1, 2, 3]
}
// Validator performs AI inference with attestation
func (v *Validator) ProcessAIRequest(req *AIRequest) (*AIResponse, error) {
// 1. Verify TEE attestation
if err := v.verifyTEE(req.Attestation); err != nil {
return nil, err
}
// 2. Execute AI inference in enclave
result := v.executeInEnclave(req.Model, req.Input)
// 3. Sign with ML-DSA (post-quantum)
signature := v.signMLDSA(result)
return &AIResponse{Result: result, Signature: signature}, nil
}
Hanzo uses Warp messaging for cross-chain operations:
// Send AI attestation to Zoo (L2)
IWarpMessenger(WARP_ADDRESS).sendMessage(
ZOO_CHAIN_ID,
abi.encode(modelHash, attestation)
);
// Receive compute request from C-Chain
function receiveComputeRequest(bytes calldata message) external {
require(msg.sender == WARP_ADDRESS);
// Queue AI compute job
}
Hanzo has independent staking economics:
staking:
token: AI
minValidatorStake: 2000 AI
minDelegatorStake: 25 AI
rewardRate: 8% APY (base)
aiMiningBonus: +2-5% (based on compute contribution)
slashing:
downtime: 0.1% per hour (after 4 hour grace)
doubleSigning: 5%
invalidAttestation: 10%
# Create Hanzo chain (L1 mode)
lux chain create hanzo --type l1 --validators 5 --vm evm
# Configure validator requirements
lux chain config hanzo --validator-requirements gpu,tee
# Deploy to mainnet
lux chain deploy hanzo --mainnet
# Register as Hanzo validator
lux validator join hanzo \
--stake 2000 \
--node-id NodeID-xxx \
--tee-attestation attestation.json \
--gpu-proof nvtrust.json
Hanzo follows the L1 specification defined in LP-0011:
Copyright and related rights waived via CC0.