Improving UX

[Autoparallel]

Dialing in Our Simulation UX

I will confess that I didn't start this discussion, but @0xJepsen did in an issue. Nonetheless, I will paste what he started here and continue the thread for the community to see.

One thing we should do in our architecture is make a a simulation outline where we can have on going constructions on a collection of protocols like portfolio, uniswap, curve, etc. These will

• Serve as an example of the power of arbiter to external contributors and projects
• Demonstrate economic risk auditing capabilities
• Give more opportunities from other core protocols to contribute

---

Question: How can we architect together a template that others can use to ingest their own config and run their own simulation?

Traits

A while back I considered adding traits for everything. For example, an Exchange trait which is also a supertrait for CFMM. You can see this in the ./lib/simulate/exchange.rs module. Also, I made an issue around this a while back: #211. What does the community think about this?

Middleware

I started issue #263 with an idea of better interfacing with EVM and following the way ethers-rs does and creates in their bindings. We should also check out Octane which seems to propose a middleware that hooks up directly with revm. Thanks @ts0yu for finding this repo 🙂