Skip to content

Architecture

  • Zero Layer (Transport & Clearing): the omnichain messaging bus. It handles atomic delivery, clearing, and checkpoint creation. (Primitive: Zero Layer)

  • Oracle Network (Data Plane): the source of fresh data — prices, policy signals, randomness, fair ordering. (Primitive: defined across Data sub-primitives)

  • Programmable Settlement (Execution Plane): a visual IDE that compiles into safe, object-based transactions. (Primitive: Settlement Instructions)

Object-Centric Model & Finality Guarantees

Section titled "Object-Centric Model & Finality Guarantees"
  • Owned objects: scoped to a single user or app, like balances, positions, accounts, or operator bonds.

  • Shared objects: coordination points touched by many actors, like channels, vaults, feeds, or registries.

  • Immutable objects: carved-in-stone templates, node definitions, and verified artifacts.

Each primitive maintains its own ledger of updates and emits a Primitive Checkpoint (PCkpt) containing object roots, ordered transactions, and a threshold signature. The Master Chain re-validates these PCkpts and rolls them into the Global Checkpoint (GCkpt) stream — the single auditable ledger of record.

Cross-primitive flows bundle multiple PCkpts together. A bundle only finalizes when every referenced root exists and all signatures verify.

Concurrency splits into two paths:

  • Fast path: updates that only touch independent owned objects — no global bottlenecks.

  • Consensus path: updates that modify shared objects — ordered by a committee to keep everyone honest.