Core Concepts

Slot Quality of Service (siQoS)

siQoS quantifies how scarce blockspace is at any given moment. Each slot carries metadata about its reservation depth, latency budget, and MEV posture. Builders can bid on those qualities instead of guessing fee levels. Under the hood, siQoS is enforced by reservation receipts, validator policies, and a monitoring network that flags any deviation.

• Deterministic: reservations are cryptographically signed and timestamped.
• Composable: lanes can be combined (e.g., MEV-protected + AOT) when capacity allows.
• Auditable: every slot publishes inclusion proofs and fee breakdowns.

Execution Lanes

Raiku maintains parallel \"lanes\" for immediate vs. scheduled activity. Lanes are not consensus forks; they are coordination layers that assign priority and enforce commitments before transactions reach validators.

Receipts & Telemetry

Every reservation generates a receipt that includes the slot number, clearing price, latency budget, and MEV policy. Receipt IDs are used throughout the APIs (monitoring, cancellation, settlement) so you always have a single source of truth. Telemetry streams broadcast slot updates, congestions forecasts, and risk alerts so products can adapt automatically.