feat: implement Data Chain Layer (DCL) core

[qj0r9j0vc2]

Summary

• Add core type definitions (Hash, Height, ValidatorId)
• Add BLS12-381 crypto primitives for threshold signatures
• Implement DCL Primary components (Car proposer, Attestation collector, Cut former)
• Implement DCL Worker components (Batch maker, Synchronizer)
• Add storage layer with WAL support
• Add MVP node binary for local testing

Components

crates/types

Core type definitions used across the codebase:

• Hash: 32-byte hash with hex display
• Height: Block height wrapper
• ValidatorId: 20-byte validator identifier

crates/crypto

BLS12-381 cryptographic primitives:

• BlsKeyPair, BlsPublicKey, BlsSecretKey
• BlsSignature with aggregation support
• Threshold signature verification

crates/data-chain

DCL implementation following the Sui Mysticeti/Narwhal pattern:

Primary:

• Car: Certified Acknowledgment Record (contains batch digests + attestations)
• Attestation: BLS signature on Car hash
• Cut: Consistent snapshot across all validator chains
• CutFormer: Forms cuts when 2f+1 attestations received

Worker:

• Batch: Collection of transactions
• BatchMaker: Creates batches from incoming transactions
• Synchronizer: Syncs missing batches from peers

crates/storage

Persistent storage with crash recovery:

• WAL (Write-Ahead Log) for durability
• Storage traits for Cars, Batches, Attestations

crates/node

MVP binary for testing:

• gen-config: Generate validator configs
• run: Run single node
• local-test: Run N validators locally

Test plan

• Unit tests for core types
• Unit tests for crypto primitives
• Unit tests for DCL components
• Crash recovery tests
• Local integration test with 4 validators
• Network partition tests
• Performance benchmarks