MIDNIGHT BUILDATHON / WAVE 2
AegisBid Private offers. A public settlement receipt. A sealed-tender prototype built on Midnight Preprod github.com/dinitheth/AegisBid
·
October 2026
PROBLEM AND MIDNIGHT FIT
Tender decisions need privacy and proof THE TENSION
AEGISBID ON MIDNIGHT
On-chain offers can expose sensitive prices.
Bidders commit to offers without publishing their values. After closing, the Compact circuit checks supplied witnesses against commitments and applies the price rule. V2 does not ensure every committed bid is represented.
Off-chain tenders keep prices private, but participants must trust the evaluator.
Midnight’s selective disclosure lets the receipt reveal the winning value while leaving losing prices off the public receipt. AEGISBID / MIDNIGHT BUILDATHON / WAVE 2
02
PRODUCT FLOW
One tender, four stages 01 PUBLISH
02 COMMIT
03 EVALUATE
Issuer deploys policy, deadline, reserve or ceiling, and evaluator capability.
Bidder proves an offer commitment. The ledger records a commitment and scoped nullifier.
After ledger time reaches closing, the evaluator supplies the committed bid witnesses.
04 SETTLE
V2 checks supplied bids against commitments and compares their values. It does not yet prove that every committed bid appears exactly once, so global optimality is unproven.
The receipt reveals the selected value. V2 does not yet prove that it is the true optimum.
AEGISBID / MIDNIGHT BUILDATHON / WAVE 2
03
MIDNIGHT ARCHITECTURE
Public state and private witnesses PUBLIC LEDGER
PRIVATE WITNESSES
Tender terms and phase Offer commitments and nullifiers Evaluator commitment Winning commitment and value Comparison root
Offer amount and salt at bid time Bidder key Candidate amounts, salts, and keys at settlement Evaluator capability
The evaluator must obtain witnesses after closing. The current app supports encrypted file handoff; recovery is not automatic.
AEGISBID / MIDNIGHT BUILDATHON / WAVE 2
04
ENGINEERING
A deployed Compact V2 path Compact V2 on Midnight Preprod 1AM wallet integration / Ledger 8 / generated contract bindings
The contract uses ledger block time for closing and evaluation. It checks the evaluator capability, bid commitments, and the reserve or ceiling. It compares supplied candidate amounts, but does not require distinct witnesses. A repeated bid can mask an omitted one, so V2 does not prove complete-set optimality. Settlement is bounded to eight bids.
Preprod contract: 21b2efc6…e9bdc957 · full address and proof-asset details in README
AEGISBID / MIDNIGHT BUILDATHON / WAVE 2
05
QUALITY AND LIMITS
Evidence and known limits REPRODUCIBLE CHECKS
npm test npm run compact:v2:check npm run build
KNOWN LIMITS
Eight bids per tender. Supplied keys do not prove real identity. V2 does not require distinct settlement witnesses, so it cannot prove the full set was evaluated or the true optimum selected. Witness handoff needs a trusted channel. 1AM proof preparation can take minutes. No audit or payment transfer.
Run a fresh full Compact compile on a compatible builder for judging evidence. The static gate alone does not compile the contract.
AEGISBID / MIDNIGHT BUILDATHON / WAVE 2
06
PRODUCT PATH
A focused path to a real procurement pilot FIRST USERS
Public agencies and organizations that need confidential offers with a verifiable selection rule.
PILOT PATH
Work with one willing issuer on a low-risk, non-binding tender. Validate bidder onboarding and witness handoff first. Test closing and settlement end to end. Add payment or award integrations only after issuer workflow, security, and compliance review. AegisBid records a settlement result. The issuer handles award and payment. AEGISBID / MIDNIGHT BUILDATHON / WAVE 2
07