01 ↗
Submitted.
Never confirmed.
Broadcast success does not prove chain inclusion. We trace signature status, blockhash validity, propagation and the limits of your available evidence.
RPC / CONFIRMATIONINDEPENDENT SOLANA EXECUTION FORENSICS
Your transaction
was accepted.
Your outcome wasn't.
Stop confusing a successful submission with successful execution. We trace what happened between your signal, your RPC, your bundle and the chain — and show you where the economics break.
01 Evidence over assumptions02 No wallet access03 Actionable findings
TRACE / EXECUTION PATH ILLUSTRATIVE
CASE / 001
The gap between submission and execution.
01SIGNALDETECTED
02BUILDPREPARED
03SUBMITACKNOWLEDGED
04INCLUSIONNOT VERIFIED
THE IMPORTANT QUESTIONWhat can the evidence actually prove?
Illustrative workflow. Not live customer data or a performance claim.
/ 01 THE PROBLEM
A blind spot in every execution stack
Accepted is not landed. And landed is not profitable.
Your provider can confirm a request arrived. Your telemetry can show a transaction was built. Neither alone proves inclusion, outcome or net P&L.
We reconcile pipeline events with available on-chain evidence, distinguish confirmed failures from unknown outcomes, and isolate what deserves engineering time.
WHAT WE INVESTIGATE
Four symptoms.
Different root causes.
Guesswork makes every miss look like a bidding problem. The first job is to separate failure modes.
Submitted.
02 ↗
Bundle accepted.
No landing.
A bundle ID is not a winning auction. We review submission path, status polling, slot context and whether “outbid” is actually established.
JITO / OUTCOMES03 ↗
Simulation passed.
Execution failed.
We examine instruction failures, stale state, compute budgets, account assumptions and divergence between simulation and execution.
BUILD / SIMULATION04 ↗
Transactions landed.
Economics didn't.
We reconcile fees, tips, actual token deltas and attribution. A profitable estimate is not an audited net result.
FEES / P&L/ 02 METHOD
Reconstruction before recommendations
We don't optimize what we can't explain.
The audit follows your execution path, not a generic checklist. Every conclusion is marked as verified, probable or undetermined.
Bring us a failing execution path01↗
Establish the evidence
Scope, architecture, sample events, transaction signatures and relevant logs. Read-only, redacted inputs.
02↗
Rebuild the timeline
Signal → build → simulation → submission → observed outcome. Normalize clocks and separate endpoint latency from confirmation time.
03↗
Classify the failure
Code, infrastructure, auction, state, observability or unknown. No invented explanations for missing evidence.
04↗
Prioritize the fixes
A ranked remediation plan with validation steps, measurement definitions and owners.
HOW WE THINK
A diagnosis should survive scrutiny.
Explore three common failure classes and what we can — and cannot — conclude from each.
OBSERVATION
Bundle was acknowledged. No verified landing in the observed window.
DEFENSIBLE CONCLUSION
The block engine received the submission. The evidence does not establish why the bundle failed to land.
UNKNOWN CAUSE ≠ OUTBID PROVEN
These are illustrative classifications, not client results. Trace distinguishes what was observed from what was inferred.
/ 03 THE ENGAGEMENT
A defined first step
One execution path.
One defensible diagnosis.
A scoped technical engagement for teams already shipping transactions on Solana. No retainer required to start.
FOUNDATION AUDIT / INITIAL ENGAGEMENT
Execution Forensics Audit
Choose one problematic flow or strategy. We review a bounded sample and turn your telemetry into an evidence-backed decision.
- Reconstructed execution timeline
- Failure taxonomy with confidence levels
- Fee, tip and outcome reconciliation where evidence permits
- Prioritized fixes + validation checklist
WHO IT'S FOR
Built for teams with real traffic and hard questions.
01
Trading infrastructure & automation teams
02
Solana wallets & execution integrators
03
DeFi protocols & technical operators
04
Engineering leads investigating recurring failures
—
Not a trading signal service, profit guarantee or managed custody product.
/ 04 QUESTIONS
Straight answers.
Do you need access to our wallet or infrastructure?
No wallet keys, signing permissions or production access. We start with sanitized logs, public signatures, configuration context and an architecture walkthrough. Any deeper access must be explicitly scoped.
Can you guarantee a higher landing rate?
No. Inclusion depends on the network, route, auction and competitors. We identify defects and measurable improvements; outcomes must be verified through controlled testing.
What if the failure cannot be proven?
We mark it as undetermined and state the missing evidence. An honest unknown is more useful than a confident but unsupported cause.
Is this only for MEV bots?
No. We can investigate submission and confirmation flows used by Solana apps, wallets, trading systems and protocol operations. We define scope based on your architecture.
What happens after the audit?
You receive a prioritized technical report and a review. If useful, we can separately scope remediation or ongoing execution monitoring. There is no automatic retainer.
YOUR PIPELINE / OUR NEXT CONVERSATION
Show us where
execution breaks.
One failing path is enough to start. Tell us what you're running and what you can't explain. We'll help decide whether an audit makes sense.
PREFER A DIRECT CONTACT?hola@embudo.com.ar ↗WhatsApp ↗