cdk-erigon
RPC and sequencing software for supported zkEVM rollup deployments, with execution, compatibility, proving, data-availability, performance, and operations assumptions validated for each configuration.
- What it is
- Rollup execution software
- Current posture
- Available for supported deployments
- What varies
- Architecture, providers, operating scope, and commitments
Fast execution is useful only when its assumptions remain operable.
A rollup execution client sits inside a wider topology of sequencers, provers, data availability, settlement, RPC, upgrades, storage, recovery, and monitoring. cdk-erigon gives Gateway a software foundation that can be integrated and operated as part of that system.
Keep the core authoritative.
- Rollup workload
- EVM applications
- Operating requirements
Change the capability at a controlled boundary.
cdk-erigon changes the boundary, not the institution’s authority.
One execution foundation
Use a supported execution and sequencing client within a documented rollup topology.
Measured compatibility
Validate application, RPC, proof, storage, data-availability, and upgrade behaviour for the selected version.
Operational ownership
Define monitoring, change, recovery, incident, support, and upstream-software responsibilities.
What cdk-erigon contributes. What still needs a decision.
EVM execution
Run supported EVM workloads according to the selected client version and compatibility profile.
Sequencing
Configure transaction ordering, block production, limits, and administrator controls for the target topology.
RPC services
Expose supported methods and capacity through the deployment’s access, routing, and security model.
Proof integration
Connect supported execution-proof workflows and document verification and fallback assumptions.
Storage and sync
Validate archival, state, sync, recovery, and storage behaviour against the workload.
Operations
Define versioning, observability, changes, incidents, recovery, support, and upstream dependency handling.
Continue from cdk-erigon into the operating model.
Bring the requirement. Define the cdk-erigon boundary.
A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.