Breadlines X-Ray now separates three questions explorers usually collapse into one: WHAT HAPPENED → execution WHAT THE NETWORK ESTABLISHED → consensus WHAT THIS OBSERVER KNEW + WHEN → provenance Tested it on a real failed Solana transaction. The SVM says LANDED_FAILED. That tells us what execution did. It does not, by itself, prove what happened to the containing block, when an observer first saw it, or independently prove finality. Those are different claims. So Breadlines now stores them as different evidence surfaces. This matters even more with alpenglow: execution stays execution while the shape of consensus evidence changes. Same transaction. Different claims. Different evidence.

Breadlines is ready for ugly transactions. Failed. Confusing. Behaved differently than you expected. The ones that made you open Solscan, logs, RPC responses and still ask: “what the hell happened here?” Send us the signature + what you were trying to understand. We’ll return: → what executed → where it failed → what committed → what never ran → what the evidence can actually prove → what still can’t be known No causality fanfic. When the evidence stops, the explanation stops. breadlinesmarkets.com

Breadlines is officially building in the Crypto World’s Fair. The mission stays simple: Make Solana execution legible. We’re pushing X-Ray beyond receipts into pre-inclusion evidence, source-aware preconfirmations and execution case files that separate what happened from what we only think happened. Four weeks. Build in public. ↓ breadlinesmarkets.com

A preconfirmation isn’t an early receipt. The useful difference is that it can be an attributable statement made before execution one you can later reconcile against the ledger. We built a Breadlines evidence model around that distinction: provider-observed ≠ validator-attested ≠ chain-proven. And if a preconfirmed tx has no matching receipt, the answer is unresolved not automatically “broken promise.” Now we want to test this against real BAM semantics.

Toly corrected how I was thinking about atomic execution across roots. Took it back into Breadlines and found a real modelling issue: execution reach ≠ state commitment. Fixed the model, UI labels and bot claim guards. Added adversarial tests too. implementation below

Firedancer documents signature linked scheduler arrival, execution timing and block inclusion. Useful groundwork for richer execution receipts. We’re exploring an offline mapping into Breadlines not announcing an integration. docs.firedancer.io/api/webso…

Solana’s execution stack is five different questions runtime, delivery, ordering, deterministic inclusion, app logic. “Why did my transaction fail?” collapses all five into one answer, usually a confident one.

We're optimizing Solana to 300ms while users still have no idea what they're competing with.