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.
LUMINARY
THE TECHNOLOGY / DESIGNED TO VERIFY
From a pinned call block to a public print, Luminary’s backend specification connects private collection, deterministic clearing and treasury settlement.
Enter the storySEALED.
CALLED.
SETTLED.


01 / PRIVATE COLLECTION
03 / PUBLIC PRINT
02 / UNIFORM CLEARINGSubmit a limit or auction-price order. At the call, eligible orders cross at one reference-bounded price. Unfilled intent rolls or cancels.
THE BACKEND ARCHITECTURE
From the Luminary product and technical documents.
Explore the complete flow in the terminal.
AuctionCalendar defines each collection window and its call block. The scheduler coordinates open, close and midnight sessions with the underlying market calendar.
The clearing engine chooses a uniform price inside the reference band. It maximizes crossed volume, respects limits and minimizes imbalance when prices tie.
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 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.
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.
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.
Tokenized treasury collateral supports the auction settlement path. RfqDesk provides a separate reference-anchored lane for private two-party blocks between calls.
The specification accounts for daylight saving changes, market holidays, corporate actions and ex-date pauses. Cancellations are not yield-gated.
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