Introducing Luminary. We are the first to pursue scheduled sealed auctions for tokenized stocks. At the open, close, and midnight UTC, orders meet privately and clear at one fair, reference-anchored price. No one gets picked off. @robinhoodapp

The clearing specification is published for third parties to recompute. Reference band. Order limits. Maximum crossed volume. Tie break. Luminaries writes those decisions into the rulebook before the call.

AuctionPool extends RwaDarkPool. That inheritance matters because the auction begins with the existing privacy core and RWA base, then adds a scheduled collection period, call block, clearing result, and print.

Bun and TypeScript run the scheduler and clearing engine. Foundry covers contracts and fixtures. Noir is reserved for the AuctionClearProof circuit. Luminaries splits ordinary deterministic work from the circuit work that needs its own layer. built on @RobinhoodApp

OPEN CLOSE MIDNIGHT NAV Luminaries stores the call type with every completed auction. The result can show whether it came from an equity session event, the global midnight call, or an issuer requested NAV auction.

The auction is not the first check in Luminaries. The base is RWA only and jurisdiction gated. Matching begins after the asset and participant have passed that layer. A sealed call is still a securities market workflow.

A thin auction lane does not require a new engine. Luminaries expansion plan says to reduce the schedule to close only if crossed volume stays below its threshold for 30 days. Cadence changes. The matching system remains. soon on @RobinhoodCrypto

State update, in one proof: pricesRoot → clearing result → newRoot Luminaries includes the nullifiers for orders consumed by the call. The proof describes what changed without publishing the orders themselves.

The full AuctionClearProof is the target. The backend plan also names the practical fallback: a signed clearing digest for the first release if the circuit needs more time. The proof circuit follows as an upgrade.

Stock reference: Chainlink × configured multiplier, inside a cap. Fund reference: net asset value. Future EURC/USDC reference: StableFX at the London and New York fixes. Same auction engine. Different reference paths. built on @RobinhoodApp

Order choice at the call: limit order fill only if the clearing price respects my limit at auction order fill at the price the call produces Luminaries supports both. Both remain sealed until the call block.

A reference band is not a suggested price. Luminaries clearing rule only considers prices inside the permitted range. The engine then looks for the one that crosses the most eligible volume.

The contract map tells you how Luminaries separates the market: AuctionPool extends RwaDarkPool. AuctionVerifier verifies the result. PrintRegistry records the print. RfqDesk crosses a block between calls. built on @RobinhoodCrypto

The scheduler is not only checking the time. It has to account for the equity calendar, holidays, daylight saving, and ex dates before it creates a call block. That work happens before the clearing engine runs.

Fund auction, from request to call: issuer request → NAV watcher → sealed collection → clearing engine → public print Luminaries changes the reference source for a fund. The call still follows the same auction flow.

A Luminaries print is intentionally small: price crossed volume The rest of the auction stays private. Individual orders and identities do not go into the public result. View keys handle the cases where a closer look is permitted.

The first build is deliberately constrained. daily calls for top stocks settlement solvency The next phase adds sealed RFQ blocks and NAV anchored fund auctions. The core market comes first. soon on @RobinhoodApp

Maximum matched volume should be something an outsider can check. Luminaries design allows that property to be proven in the circuit or verified through a published, order independent check after the call.

Two separate questions sit underneath one market: Did this auction follow its clearing rules? Is the market backed? AuctionClearProof covers the call. Solvency proofs cover backing. Luminaries keeps those checks distinct.

Before the call: a price state root. After settlement: a new root. Luminaries proof carries both records, plus the markers for orders already consumed. It is the onchain before and after of one completed auction.

The book stops changing at the call block. Luminaries collects sealed orders first, then pins that block on @RobinhoodCrypto. The clearing engine works from that fixed set of instructions. That boundary is what makes a scheduled auction an auction.