Heindel/mathematical economics of hierarchical operator pools

[heindel]

This is the present state of affairs of the 'mempool blog post', now titled Operator Pool Trees: filling order flow ASAP—at least in theory.

The relevant files are in the directory mempool, namely

• mempool-blog-post.md: the main markdown file
• MempoolHierarchiesInAnSVG.svg: the figure
• hierarchy-pools.pdf: the PDF output produced by running the Makefile
• Makefile: run the make command to generate the PDF (requires pandoc and xelatex)

Note

There are of course still many open points. Some of these are indicated by boldface in the prose.

• sometimes boldface is used to mark parts that are "obvious" passages that need improvement or placeholders for missing/unfinished content
• some "annotations" are given in [boldface], adding square brackets to make clear that this is a comment actually (and not even a placeholder)

TL;DR

While the general structure of the argument for why "this" is an interesting topic is about right, many details need checking and or corroborating via experimentation, by providing good examples. All feedback is welcome, literally ‼

[heindel]

@0xapriori ☝️

[tg-x]

Github-rendered post

[0xapriori]

My comments on first pass of reading are:

• probably want to introduce the concept of a mempool start with a basic example, maybe CometBFT or Ethereum, explain how it works before diving into this new concept
• the post assumes a lot of context in terms of order flow, intents, subnets, etc. Not all readers will be immediately familiar with these terms or have slightly different definitions. I think it would be helpful to briefly define some of these things
• Its not clear to me what the outcome of the post is other than exploring this concept of hierarchical mempools (which is fine). but I think you need to be explicit about that
• In the beginning you mentioned how this relates to Anoma being an intnet machine for Ethereum. The post never really discussed that. There are inferences about the topic sure, but most readers won't be able to make that inference.

Critiques aside, I like the tone of the post and the direction of the topic. More diagrams would help as well, which it seemed you were asking for an interactive one?

Thank you for the submission. Let's discuss more next week.

[heindel]

My comments on first pass of reading are:

• probably want to introduce the concept of a mempool start with a basic example, maybe CometBFT or Ethereum, explain how it works before diving into this new concept

yes

• the post assumes a lot of context in terms of order flow, intents, subnets, etc. Not all readers will be immediately familiar with these terms or have slightly different definitions. I think it would be helpful to briefly define some of these things

yes, and to be introduced with the above; so far, the background just gave the bare minimum to be able to formulate the point, which ...

• Its not clear to me what the outcome of the post is other than exploring this concept of hierarchical mempools (which is fine). but I think you need to be explicit about that

... is the following: For some some kind of order flow and if we have a frictionless collaboration of operators, we get a welfare advantage.

• In the beginning you mentioned how this relates to Anoma being an intnet machine for Ethereum. The post never really discussed that. There are inferences about the topic sure, but most readers won't be able to make that inference.

right, that also needs to be made explicit, incorporating some of the insights of our last chat. In fact, I had put aside the whole relation to settlement controllers

Critiques aside, I like the tone of the post and the direction of the topic. More diagrams would help as well, which it seemed you were asking for an interactive one?

Yes, inspired by quarto's description of reveal.js, there is a lot of fun stuff we could do, like "dynamic" plots that let's the reader play with parameters. I have submitted a feature request. #11

Thank you for the submission. Let's discuss more next week.

Thanks for the review, which in particular makes explicit the todo list of things to fix.