Concepts

MEV Protection

Raiku’s MEV layer blends auction-level rules, validator attestations, and execution-time heuristics to dramatically reduce sandwiching and priority gas auctions without impacting honest flow.

Threats We Mitigate

Sandwiching: malicious actors attempt to bracket user transactions within the same slot.
Time-bandit replays: transactions are replayed across RPC endpoints to infer strategy.
Blockspace sniping: priority fee spikes steal capacity from scheduled flows.
Cross-domain leakage: builders read order flow before inclusion decisions are final.

Controls

Lane Isolation

Reserved slots can opt into shielded lanes. Transactions are encrypted until the validator’s decision window to prevent cross-venue frontrunning.

Order Commitments

Builders submit merkle commitments of the order flow they plan to execute. Divergence triggers slashing or suspension from premium lanes.

Anomaly Scoring

Each slot computes a per-transaction risk score using volatility, liquidity depth, and historical behavior. High scores automatically move to shielded settlement.

Receipt Attestations

Validators append MEV attestations to reservation receipts, proving the flow was respected. Receipts feed back into analytics, insurance, and compliance reports.

Integration Pattern

mev-protection.ts

import { initMEVShield } from '@raiku/sdk'

const shield = initMEVShield({
  intentId: reservation.intentId,
  mevPolicy: 'shielded',
  allowedRelayers: ['raiku-default', 'custom-otc'],
})

await shield.register({
  commitment: bundleCommitment,
  expiry: reservation.slot + 2,
})

The SDK signs your commitment and forwards it to the Raiku coordination layer. When the slot executes, validators will only admit transactions that match the commitment hash, ensuring pre-trade privacy.