Certainty Desk Raiku contribution ops
Learn lane

Glossary / ELI5

Terms you can teach in chat without copy-pasting the whitepaper. Official source of truth stays on docs.raiku.com.

Community plain-language pack Official docs ↗
Corecertainty

Certainty

Plain: Knowing a transaction will land as planned — not “maybe if the network feels kind.”

Why it matters: Markets, apps, and institutions need outcomes they can operationalize.

Corelanding

Deterministic landing

Plain: Inclusion/execution behaves like a guaranteed outcome path, not a dice roll under load.

Teach it: Fast roads still jam. A reserved gate is different from hoping for a gap.

ModeAOT

Ahead-of-Time (AOT) reservation

Plain: Book compute/blockspace capacity before the critical moment.

Teach it: Like reserving a gate before peak hour so your flight isn’t improvising on the tarmac.

ModeJIT

Just-in-Time (JIT) execution

Plain: Execute in a tight, coordinated window when capacity is available now.

Teach it: Not everything is pre-booked months out — some flow is high-performance “right now,” still coordinated.

UnitCU

Compute Units (CU)

Plain: The work budget a transaction needs on-chain.

Teach it: If blockspace is the airport, CU is how much runway/handling your plane requires.

Marketblockspace

Blockspace market

Plain: A two-sided market where demand for reliable execution meets supply from validators/builders offering it.

Teach it: Blockspace stops being pure chaos commodity and becomes something you can price, reserve, and plan around.

Actorsvalidators

Validators (in Raiku context)

Plain: Operators who can offer guaranteed inclusion / AOT-style services on top of securing the network.

Teach it: New revenue lane: sell certainty without throwing away existing roles.

Actorsusers

Builders · Traders · Institutions

Builders: fewer infra workarounds, more product.
Traders: execution they can model.
Institutions: operational control at scale.

Compatbundles

Bundles / existing execution services

Plain: Raiku is described as compatible with existing transaction bundling patterns — coordination layer, not “burn the tools you have.”

Teach it: Upgrade the reliability layer; don’t demand everyone invent a new religion overnight.

NarrativeICM

Internet Capital Markets

Plain: Serious on-chain financial activity that needs infrastructure SLAs, not weekend-demo reliability.

Teach it: If markets move on-chain, the rails must behave like infrastructure, not a lottery.

30-second pitch

Raiku brings enterprise-grade certainty to Solana.
Not just speed — deterministic landing and reserved compute,
so builders, traders, and institutions can operate under load
without treating every send like a coin flip.

Reply-guy myth busters

  • “Isn’t Solana already fast?” → Fast ≠ certain under stress.
  • “Is this just MEV stuff?” → Focus is reliable landing + reservation market design.
  • “Why validators care?” → Certainty services = extra revenue lane.
  • “Why community content?” → Markets need teachers, not only whitepapers.

Know it cold, then teach it warm.

Use Armory shells once the terms are automatic.