cowprotocol / cowprotocol/docs
chore: improve Batch Auction Section
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
I'd add a diagram show-casing the difference between continuous order books (bid ask spread) vs. discrete order books (orders overlapping clearing at the intersection).
I think we should also add context of why batch auctions are already arguably beneficial in TradFi (we can link/summarize to Budish's talk for that) and highlight more why they make even more sense on Ethereum, namely that there is no concept of continuous time on Ethereum, all transactions within a block are already batched and executed at the same instant in time (yet people apply pseudo-continuous time priority mechanisms to this which is 🤯)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/cow-protocol/concepts/batch-auctions/why-batch-auctions.md, especially the section linked in the issue. Review the requested comparison between continuous and discrete order books and the linked Budish talk for context. Done means the page includes a clear diagram and explains why batch auctions are useful in traditional finance and especially on Ethereum.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100