What’s this for?

Language glossary:

Name Description
Stylus Arbitrum’s new Rust/WASM frontend stack for the EVM.
Backdata All the transactions, and their receipts

What are some validation milestones as UX constraints?

Milestone 1

  1. Backdata collected from ZkSync’s AMM offerings, and the median gas cost collected.
    1. Controlling to avoid:
      1. Routers
      2. Multiple hops that aren’t 1 to 1 base/quote asset.
  2. ERC20 token that mints anything transferred is created. Existing code in Q that generates the delta is removed, and the Go code that executes the calldata is used against the contract.
    1. Run against the Arbitrum Stylus nitro testnode.
    2. State in the contract is snapshotted and ready to be reproduced offline.

Milestone 2

  1. Building on the position creation, ERC20 token/contract is written to fuzztest the contract with hundreds of swaps.
    1. Whether these work or not is not a big issue!
    2. Gas profile is collected for this.

Milestone 3

  1. Backdata from the following chains is collected with whatever native AMMs they have. In the same way as the other collection.
    1. Scroll
    2. Berachain
    3. Optimism
    4. Solana

What could the architecture look like?

What're some example test user stories that would be suitable for integration tests?

If there’s math, what are some inputs and outputs that would be suitable for a unit test?

What are some readings and comparable products?

  1. Past efforts, including the program that generated the data for the Go position creation:

https://www.notion.so/fluidity/Historical-data-swap-comparison-AMM-ARBITRUM-ONLY-list-0dc988d62ee745c7bb203a165cc9f11b