L2 ZK Rollup Creation Skill

Create end-to-end app-specific ZK rollups from STF to L1 verification.

1|1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/tokamak-network/py-ethclient --skill l2-zk-rollup-creation-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: L2 ZK Rollup Creation Skill
Source: https://github.com/tokamak-network/py-ethclient/tree/main/.claude/skills/l2-rollup
Command: npx skills add https://github.com/tokamak-network/py-ethclient --skill l2-zk-rollup-creation-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

App developers need a guided workflow to define and run App-Specific ZK Rollups—from a State Transition Function (STF) to deployment and L1 verification—without needing to wire together disparate components manually.

Core Features & Use Cases

  • Orchestrates STF definitions, PythonRuntime wrapping, and Rollup lifecycle (setup, submit, batch, prove, and L1 verification).
  • Provides pluggable interfaces for StateTransitionFunction, DAProvider, L1Backend, and ProofBackend for flexible integration.
  • Supports end-to-end workflows for building, testing, and deploying ZK rollups in Python with deterministic proving, sequencing, and state management.

Quick Start

Define STF logic, wrap it with PythonRuntime if needed, then instantiate Rollup and run setup, submit transactions, produce batches, and prove+submit to L1.

Frequently Asked Questions about L2 ZK Rollup Creation Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an app-specific ZK rollup from a state transition function?

To create an app-specific ZK rollup, define your STF logic in Python, wrap it with PythonRuntime, then use the Rollup orchestrator to run setup, submit transactions, batch, prove, and submit to L1.

What is needed to deploy a Python ZK rollup with Groth16 proving?

Deploying a Python ZK rollup requires a Python STF implementation, a Rollup orchestrator, a Groth16 prover backend, and configurable L1 and data-availability backends for automated proof submission.

Can I plug a custom data availability provider into my L2 rollup?

Yes, the rollup provides pluggable interfaces for StateTransitionFunction, DAProvider, L1Backend, and ProofBackend, allowing flexible integration of a custom data availability provider into your L2 rollup.

How does L1 verification work for an app-specific ZK rollup?

L1 verification works by the Rollup orchestrator producing batches, generating a Groth16 proof, and automatically submitting that proof to the configured L1 backend for final state verification.

What is the best way to orchestrate sequencing and proving for a ZK rollup?

The best way to orchestrate sequencing and proving is using the built-in Rollup lifecycle, which manages deterministic proving, transaction sequencing, and state management end-to-end for ZK rollups.