Luminary silver-blue illustrated world

THE TECHNOLOGY / DESIGNED TO VERIFY

The technology

A clear sequence. A verifiable outcome.

From a pinned call block to a public print, Luminary’s backend specification connects private collection, deterministic clearing and treasury settlement.

Enter the story
LUMINARY / TECHNOLOGY
02 / THE PROTOCOLLUMINARY — PROTOCOL 4663

SEALED.
CALLED.
SETTLED.

PRIVACY IN. PROOF OUT.

Many orders.
One clearing price.

Luminary silver-blue illustrated landscape01 / PRIVATE COLLECTION
Luminary illustrated world03 / PUBLIC PRINT
Luminary dragon and mountain artwork02 / UNIFORM CLEARING
LUMINARY / 02

Submit a limit or auction-price order. At the call, eligible orders cross at one reference-bounded price. Unfilled intent rolls or cancels.

PRIVATE ORDERS. PUBLIC PRICE + VOLUME.Inside the protocol

THE BACKEND ARCHITECTURE

From schedule to settlement.

From the Luminary product and technical documents.
Explore the complete flow in the terminal.

01 / LUMINARY

Pin the moment.

AuctionCalendar defines each collection window and its call block. The scheduler coordinates open, close and midnight sessions with the underlying market calendar.

02 / LUMINARY

Compute the cross.

The clearing engine chooses a uniform price inside the reference band. It maximizes crossed volume, respects limits and minimizes imbalance when prices tie.

03 / LUMINARY

Verify the result.

The proof orchestrator prepares the intended auction proof. AuctionPool and AuctionVerifier coordinate settlement; PrintRegistry publishes the resulting price and crossed volume.

A CLOSER LOOK

The systems behind the scene.

01

Private collection and state

The specified AuctionPool tracks sealed intent and settlement state. Public proof inputs include the auction identifier, reference-price root, clearing price, crossed quantity, new state root and nullifiers.

02

Proofs with a defined scope

AuctionClearProof is intended to verify reference bounds, order limits, asset conservation and the clearing volume property. A signed clearing digest may precede a full proof upgrade; this site does not generate either production assurance.

03

A coordinated worker layer

The backend separates auction scheduling, clearing, proof orchestration, print publishing, NAV watching and calendar events. Each worker has a defined role in moving a call from collection to a public result.

04

Treasury settlement and RFQ

Tokenized treasury collateral supports the auction settlement path. RfqDesk provides a separate reference-anchored lane for private two-party blocks between calls.

05

Calendar-aware operations

The specification accounts for daylight saving changes, market holidays, corporate actions and ex-date pauses. Cancellations are not yield-gated.

06

The intended stack

The technical plan uses Noir for circuits, Foundry for contracts and Bun with TypeScript for workers, targeting Robinhood Chain. These are specification choices, not a claim that this site is a deployed production protocol.

Assets and prices shown here are illustrative. See Risk & eligibility for the current boundaries.

THE STORY CONTINUES

Understand the architecture. Experience the flow.

Explore the auction terminal