Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of tx preconfirmation functionality to API #587

Open
konradstrachan opened this issue Feb 23, 2024 · 1 comment
Open

Addition of tx preconfirmation functionality to API #587

konradstrachan opened this issue Feb 23, 2024 · 1 comment
Labels

Comments

@konradstrachan
Copy link

It would be desirable to be able to access limited preconfirmation data from Relays to support research we are doing on intent based architectures and hopefully level the playing field for as many fillers to compete in a risk managed manner leading to greater intent execution decentralisation.

Since all intent based protocols utilise FCFS auctions, fillers race to submit a filling bid earlier than others. Presently they this is done through a combination of protocol run execution insights (i.e. the protocol known an order has been signed because of API calls and thus can speculatively fill using this knowledge even before the tx reaches a mempool) or non-protocol aligned actors tailing public / private mempools directly prior to onchain confirmations.

We propose adding a new read-only API to the Relay (shown in green in the diagram below) that will accept a filter (e.g. a contract address possibly with a function selector) and return all the transactions currently in the best candidate block that meet these filter requirements.

relayer_proposal

This creates a mechanism that allows for a degree of limited probabilistic insight into future block composition without weakening in any way the proposer builder separation mechanisms.

Besides the previously noted advantage of decentralisation, if this functionality results in commercialisable datastreams consumed by Fillers (or other actors) it could be the foundation of an economic incentivisation mechanism for running Relays.

Along with this issue we are submitting an illustrative changeset that shows how we’d approach making this change at a high level. main...AneraLabs:mev-boost-relay:tx-inclusion-info-api

@konradstrachan
Copy link
Author

Update : thanks to external discussions we realise that additional thought needs to go in to this. For now please disregard and I'll publish an update soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant