Deterministic reconstruction
Ordering, references, edits, reorgs, and invalid events.
Process logs in (blockNumber, transactionIndex, logIndex) order, starting at the bundle's declared start block. Store raw logs before deriving views.
References are evaluated once against prior valid objects. A missing or forward reference is invalid and does not become valid when a later event appears. A reply must reference an earlier message in the same main discussion. An edit must be authored by the original author. The last valid edit controls the current display, while the original event remains available for audit and reply snapshots.
On a chain reorganization, roll back affected blocks and replay from the common ancestor. Database row IDs, API arrival time, and WebSocket order are not canonical ordering signals.
An event may remain part of chain history while being semantically invalid. Compatible clients preserve it for audit but exclude it from canonical conversation state.