really cool design!
two more theoretical questions:
- how do you foresee governance of the language of {privacy preferences, validity conditions, hints} working? Esp. as it pertains to SUAVE
this seems like the first case where language defining predicates of EVM-level stuff needs to exist at the ‘protocol level.’ I.e. tokens_traded in privacy preferences is a quite subjective ‘application-level’ concept.
If there are differing opinions about what predicates to expose in the language between these various entities, I could imagine governance of what’s canonical/enshrined being quite contentious.
- is there a way for builders (or searchers) to re-submit privately-matched bundles for more tx addition?
slightly less thought out, but I’m wondering if there’s a way to recursively continue building private bundles.
reason being that the existence and properties of a ‘privately inserted bundle’ is information that could probably be used by builders (or even searchers) to re-bid for additional private tx insertion.
the fun, less useful exercise I’m also curious about as an extension - what would it look like to recursively build a bundle ‘from 0.’ i.e. could a capitalized enough searcher with no information about other txes recognize that there’s some value in affecting bundle formation at a specific time and act on that