The execution model shapes the product. We map the application's state changes and external inputs first, then develop the kernel, integration layer and operational tooling as one delivery. The result should be understandable to the people maintaining it, not only the people who wrote it.
How does information enter?
Identify accepted inputs, validation rules and the handling of missing or malformed messages.
Who responds to a fault?
Document node responsibilities, monitoring ownership and the escalation process for disputed state.
Where it fits
Practical Use Cases
01
Custom execution logic
Explore a kernel tailored to application rules that need a distinct execution environment.
02
Message-driven applications
Build a product around validated inputs, traceable processing and clear output status.
03
Operational tooling
Give rollup operators focused visibility into processing, commitments and application health.
Describe application state, messages and expected outcomes.
02
Architecture
Select the kernel approach and define the input and output contracts.
03
Implementation
Implement a testable kernel with application APIs and operator views.
04
Verification
Check deterministic behaviour, message rejection and recovery scenarios.
05
Launch & Support
Document deployment, monitoring and the maintenance handover.
Selected for your scope
Technology & Delivery Toolkit
We choose the implementation tools after confirming the architecture and integrations.
Tezos / Octez tooling
Kernel test harness
Application APIs
Node monitoring
Before you build
Tezos Smart Rollup Development FAQs
What is a Smart Rollup kernel?+
It is the program that processes the rollup's inputs and updates its state. Tezos Smart Rollups use deterministic execution so nodes can reproduce and check the same result.
Can an application ignore settlement state?+
No. A useful interface distinguishes processing from the completion of the relevant output lifecycle. We design those states into the API and customer-facing experience.
Turn your Tezos application rules into a tested kernel
Tell us what you want to build. We’ll help define the next practical step.
