From 7d8e2c5bf653edc56949f2c336253ef4a6532cb6 Mon Sep 17 00:00:00 2001 From: saucepoint <98790946+saucepoint@users.noreply.github.com> Date: Fri, 11 Oct 2024 12:28:55 -0400 Subject: [PATCH] note on v4 and uniswap x (#795) Co-authored-by: Alex Karys Co-authored-by: Alice <34962750+hensha256@users.noreply.github.com> --- .../v4/concepts/08-integrated-routing-uniswap-x.mdx | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx diff --git a/docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx b/docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx new file mode 100644 index 000000000..4bad9e4f5 --- /dev/null +++ b/docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx @@ -0,0 +1,13 @@ +--- +title: Integrated Routing with UniswapX +--- + +The [Uniswap Interface](https://app.uniswap.org) will be ramping up support for hooks in it's standard routing system progressively over time. Hook builders looking to get immediate access to flow from the interface can do so by running a UniswapX filler for their hooked pools. + +At a high level, hook builders' filler implementations will need to do the following: + +1. (On Mainnet) Subscribe to the UniswapX RFQ system and submit fillable bids from orders they receive +2. Listen to the public feed for orders they won or that are open to be filled publicly +3. Execute those orders against pools that use their hooks + +Developers should check [UniswapX Documentation](/contracts/uniswapx/overview) to get started.