How Raiku Works
This page explains how Raiku delivers deterministic execution on Solana without modifying consensus or replacing validators.
Where Raiku Fits in the Stack
Raiku operates at the execution coordination layer. It sits between users and block builders, organizing how blockspace is allocated before blocks are constructed.
Importantly, Raiku does not change Solana’s consensus rules and does not replace validators.
High-Level Execution Flow
- Users submit execution requests with timing preferences
- Raiku organizes requests into explicit markets
- Blockspace is allocated via auctions
- Builders construct blocks honoring execution commitments
- Validators finalize blocks as usual
Key idea: Execution is coordinated before block construction, not guessed during it.
The Architectural Shift
Traditional Model
- • Leader-controlled block building
- • Blind transaction competition
- • Fee-based guessing
Raiku Model
- • Coordinated execution
- • Explicit commitments
- • Market-based allocation
Open Block Building
Raiku enables open block building, where multiple builders compete to construct optimal blocks under predefined execution rules.
Builders are economically incentivized to honor execution commitments, improving fairness and reducing MEV waste.
Slots as Schedulable Units
A slot represents a fixed execution window on Solana. Raiku treats slots as economic units that can be priced, reserved, and scheduled.
This turns blockspace from a best-effort resource into predictable infrastructure.
Global Accounts
Global accounts are shared coordination points that allow Raiku to enforce execution ordering and prevent conflicts.
They make deterministic scheduling possible by ensuring execution guarantees can be enforced across transactions.
Why This Architecture Works
Raiku’s architecture succeeds because it separates concerns: consensus remains untouched while execution becomes predictable.
This preserves Solana’s performance advantages while enabling a new class of reliable applications.