Bundle Status API

Presently, searchers on mev-share are unable to learn anything about their bundle after it is sent, other than the fact that it was received by the API. A bundle targeting a block 10 minutes in the future appears no different to the user than a bundle that gets included instantly, other than what they see on Etherscan. In situations where inclusion is prolonged (and the reason is uncertain), checking the status of your bundle is very frustrating.

The system’s UX would benefit greatly from a “status” endpoint, similar to `flashbots_getBundleStats`.

However, we cannot reveal to searchers whether their bundle reverted, because doing so would compromise the privacy of users. Any on-chain value can be leaked if we give searchers instantaneous feedback about whether their bundle reverted.

**How can we design tracking APIs that give searchers a better UX without compromising on privacy?**

Start by reviewing the issue's proposed analogy to flashbots_getBundleStats and the privacy constraint around revealing bundle reverts. Define what status information can be exposed without leaking on-chain value, and consider how the endpoint would distinguish delayed inclusion from immediate inclusion. Done means a privacy-preserving tracking API design with agreed behavior.

Written by the indexing model from the issue text.