Bundle + Searcher Features

During an auction a searcher is competing in, a searcher may want to know what the current winning bid is so they can send a higher paying bundle and/or do a cancel_replace. From office hours: "not knowing if you're going to win an auction or not sucks." Similar to this idea, when the bundle results message is sent for rejection due to low bid, send the winning bid and other auction details

Searchers can have the ability to add more contextual information for bundles. For instance, what slots are a bundle valid for, which bundles can be broken apart/merged, what txs in a bundle are ok to fail, and more. For bundle merging, imagine an NFT mint where several searchers submit a backrun like [nft_mint_enable, mint_nft, mint_nft, mint_nft, ...]. In this case, only the highest paying bundle would win since there's only one nft_mint_enable transaction. With bundle merging, we could break bundles apart and find better ordering, either automatically or specified by the searchers with some type of flags attached to each transaction in a bundle

To get more insight into why a bundle failed (and accelerate dev in prod flow) it would be nice to access full sim results including logs. Could be an api endpoint or a ui. Would be already super useful if data only goes one epoch back.

Filtering options similar to https://github.com/rpcpool/yellowstone-grpc would be really valuable to reduce network and system load for searchers

Details - ignore_signers is a list of Pubkeys you dont want to receive memstream messages from Purpose - Filter out other searchers spam transactions to reduce backlog (mainly for busy times). The source of MEV, in almost all cases, will be from the end user Note: I am talking from an arbitrage perspective, and can't talk to the usefulness elsewhere

System that monitors bundles sent to validators and their on-chain status (landed, what slot, dropped, drop reason, what slot simulated on, executed tip amount vs simulated, etc.)

When cross-region pending transactions go live, add the ability to limit pending transactions to a specific region.

Setup RPC service to submit transaction's through Jito's staked nodes so that it has higher priority. Comparable to Marinade's mtransaction service: https://medium.com/marinade-finance/marinade-mev-part-3-introducing-mtransaction-346f914c0750

Seteup Starrider RPC service in Tokyo. Target setup by May but TBD based on customer interest

Dashboard showing all Jito bundles as well as contents. It should show general MEV stats, tip amounts, and should be searchable with a few fields like transaction signature, signer, and more.