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

A Luminaries print is a contract record, not a chart update. The backend stores the asset, call type, call block, clearing price, crossed quantity, and proof transaction for each completed auction.

What happens to an order that does not fill? Luminaries gives it two paths: roll into a later call or cancel. The auction result is final. The trader instruction does not have to disappear with it.

A stock call and a fund call share the same matching engine. The difference is the starting reference. Stocks use the configured Chainlink reference path. A fund auction is anchored to its net asset value.

The price engine has one first job: find the price that crosses the most eligible volume inside the permitted reference range. If two prices produce the same result, Luminaries chooses the one with less leftover imbalance. Soon on @RobinhoodCrypto

Call block sounds technical. It is just the point where the order window closes. Luminaries collects sealed instructions before that block. Once the block is pinned, the clearing engine works from one fixed auction book.

The main auction is for a market coming together. The RFQ lane is for two parties that already know the trade they want. Luminaries gives that block a sealed, reference anchored route between calls.

A filled instruction needs a record that it was consumed. Luminaries includes nullifiers in the completed auction data. They mark which sealed instructions were used when the call settled. Built on @RobinhoodApp

Daylight saving moves the equity clock. A chain block does not move with it. Luminaries has test cases for that gap, along with holidays and ex dates, before the scheduler publishes a call.

An issuer asks for a fund auction. The NAV watcher supplies the reference. AuctionCalendar creates the call. Then the clearing engine runs the same matching rules used for the rest of the market.

The hard part of the build is the proof circuit. Luminaries backend has a stated fallback for launch: a signed clearing digest if the full AuctionClearProof needs longer. The circuit can be upgraded after the first release. Soon on @RobinhoodApp

A stock call and an EURC/USDC fix do not share a reference source. Luminaries expansion plan keeps the auction engine and changes the market inputs: StableFX for EURC/USDC at the London and New York fixes.

The auction layer sits on an existing RWA base. Registry. Dual pricing. Raw unit notes. Corporate action calendar. Solvency. Tape. Luminaries adds scheduled collection, clearing, and a public print on top of that foundation.

What does AuctionClearProof expose? the auction ID the price state root the clearing price the matched quantity the new state root spent order markers The proof exposes the result and the state change, not the individual instructions. Built on @RobinhoodCrypto

The clearing rule has an order of operations: 1. Match the most possible volume inside the reference band. 2. If more than one price does that, choose the one with less left unmatched. That second step is how Luminaries resolves a tie.

Two order instructions. One call. A limit order has its limit respected. An at auction order fills at the price this call produces. Luminaries keeps both sealed until the engine applies the same clearing price to every fill.

The proof has its own test fixtures. Luminaries can freeze a known auction case, then check that the evidence for its result still passes when the proof layer changes. The auction rule and the evidence for that rule get tested separately. Soon on @RobinhoodApp

There is a reason Luminary names AuctionVerifier separately from AuctionPool. One contract holds the auction state. The other accepts the evidence that its result followed the rulebook. Execution and verification meet at settlement.

RfqDesk is the route for a trade that already has two sides. Party A and Party B agree to cross at the reference. Their instructions stay sealed. The desk settles the block between public auction calls.

Dual pricing sits underneath the auction. Luminaries RWA base keeps two price views before the call reaches the clearing engine. That separation matters when the system has to distinguish the market reference from the state being settled. Built on @RobinhoodCrypto

A trade fee should not be mixed into the matching engine. Luminaries keeps fee accounting in FeeVault, separate from AuctionPool and RfqDesk. The auction decides what clears. The vault records the fee flow that followed it.