Last Known BookEvidence lives on. ← Back to investigations
SOMNIA × DREAMDEX EVENT CONTRACTS · JUDGE PACKET

One product.
One evidence trail.

Last Known Book begins after an unexpected execution. It reconstructs DreamDEX venue reality, separates observed facts from inference, and allows only bounded evidence-backed containment.

JUDGE IN 60 SECONDS

See the whole argument fast.

The quickest path is intentionally behavior-first: open the case, see the venue-native reveal, verify the real Shannon proof, then inspect the source and SDK feedback only if you want the deeper audit trail.

1Open LKB-001

Start with Agent Intent ≠ Venue Reality.

2See MINT_A_PAIR

Land the reveal: “This wasn't a whale. It was a mint.”

3Inspect real proof

PostOnly rested, zero fills, exact cancel, collateral restored.

4Check the boundary

Testnet technical + behavior proof, not production evidence.

PROOF

Receipts over claims.

What the proof demonstrates.

Technical behavior and operational containment on Somnia Shannon: exact pre-write gating, a bounded PostOnly order, zero fills, `OrderPlaced → OrderRested`, exact returned-order cancellation, `OrderCancelled`, and collateral restored exactly. It does not demonstrate production reliability, ROI, MTTR improvement, incident prevalence or profitability.

MECHANISM

The incident contract.

The product does not optimize for transaction count. It reconstructs what happened, classifies what is known, and only permits an action when grounded predicates justify it.

01Capture agent intent
02Reconstruct venue reality
03Decode DreamDEX-native cause
04Gate corrective authority
05Reconcile final state
The trading agent may be AI. The layer that decides whether money moves is not.

Observed evidence can constrain automation. Inference can request more evidence. Unknown can stop the system. DreamDEX-specific semantics — marketId, rolling pool binding, MINT_A_PAIR, resting escrow, lifecycle and native order events — are the causal vocabulary rather than sponsor decoration.

JUDGE Q&A

The objections we expect.

Isn't this just analytics?DIFFERENTIATOR

No. Analytics describes a market. Last Known Book reconstructs one unexpected execution, identifies the DreamDEX-native cause, decides whether a corrective action is justified, and reconciles closure.

Why not just inspect a block explorer?PRODUCT NEED

An explorer shows transactions. It does not reconstruct Agent Intent vs Venue Reality, classify venue-specific cause, separate truth classes, apply an authority policy and close the incident as one evidence contract.

Why does this require DreamDEX?SPONSOR FIT

The mechanism depends on DreamDEX Event Contract semantics: durable marketId identity, rolling pool binding, MINT_A_PAIR, escrow behavior, lifecycle state and native order events. Removing those semantics collapses the current causal model.

What is real versus replayed?TRUTH BOUNDARY

Four casefiles are deterministic replays built from captured real Shannon incident evidence. Separately, Packet 003 is a Last Known Book-originated real Shannon testnet placement/rest/exact-cancel/reconciliation proof.

Did the real Packet 003 order trade?PROOF SCOPE

No. It was deliberately PostOnly, rested with zero fills, then the exact returned order was cancelled. That proves bounded authority and reconciliation, not profitable execution.

Is WRITE REFUSED a failure?SAFETY

No. Refusal is the correct behavior when evidence does not justify a write. A blind compensating transaction can turn one confusing incident into two.

What business outcome is proven?CLAIM DISCIPLINE

Operational containment is demonstrated on Shannon testnet. MTTR improvement, ROI, incident prevalence and production reliability are not yet proven and are not claimed.

AUDIT TRAIL

Go as deep as you want.