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.

Solana Transaction v1 gives you 4,096 bytes. We tried spending them on post-quantum authorization. ML-DSA-44: 2,928 bytes ✅ ML-DSA-65: 3,817 bytes ✅ SLH-DSA-128s: 8,364 bytes ❌ Smallest tested 2-signature construction: 6,252 bytes ❌ So larger transactions unlock individual PQ authorization payloads. They do not automatically unlock inline PQ multisig. And we haven’t even reached the compute question yet. New envelope. New bottleneck.

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.

What changed: -reach and commitment are now separate. -failed-tx frames show returned success · rolled back. -per-root commitment stays unknown unless actually decoded lateness / partial-commitment claims are blocked. -UI + bot both have regression tests Markets diff:
github.com/Dolaporr/BreadLin……0196d28 Bot diff:
github.com/Dolaporr/Breadlin……3663d45

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…

Breadlines biggest limitation rn isn’t features. it’s visibility. onchain data tells us what landed, but not the full execution journey before inclusion. closing that gap is what we are working on now. less guessing. better execution evidence.

We preregistered a controlled Solana delivery-path study, then stopped it before sending anything. The access check found three blockers: no documented public Axiom sender surface we could find, a mandatory Nozomi tip that changes transaction shape, and on a BAM-connected leader both RPC and direct-TPU flow routing through BAM, so there’s no clean non-BAM control.

v0.1 of our note on where the evidence for each one actually stops, with a worked receipt on a real failed signature. breadlinesmarkets.com/resear…

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.

First research note is up Did the 350ms→300ms transition change landed execution on Solana? The ledger doesn’t say. The before/after answer swings from +0.22pp to −10.65pp on window width alone the preboundary hours weren’t stable. Rules fixed before looking. Nothing passed

Solana voted to issue less SOL. But the more interesting vote failed: burning more SOL based on network resource usage. One changes supply. The other changes how Solana captures the value of blockspace. That fight isn’t over.

Swap failed? Your coin accounts didn't just trip, they staged a whole MCP traffic jam while ghost programs bailed like June bugs. Breadlines receipts bring the receipts—brutal slot-time scars with no fluff or fairy tales. breadlinesmarkets.com

If your swap failed and you’re blaming slippage, check your writable coin accounts first. Slow CA crawl and MCP vultures flipping tables in slot time don’t forgive. Breadlines prints every bruise so you know where the pain really lives.

Failed swap? It’s not just sludge—it’s the coin accounts playing dead, MCP vultures circling, and ghost programs ditching faster than your trade thought. Breadlines receipts ink the bloody timeline—no myths, just slot scars. breadlinesmarkets.com

Sluggish coin accounts in FCFS queues are the silent killers. Breadlines receipts catch every jitter, every MCP shove—your swap isn’t slow, it’s getting mugged in slot time.

MCP vultures circling your coin accounts like it’s an all-you-can-eat buffet? Breadlines prints the receipts— every slow writable, program ghost, and brutal elbow in slot time. No fairy tales, just blockchain carnage.