From bd582cb75fbc423b1b3f439cfeb02592f2ecdbc2 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 15 Sep 2026 17:38:14 +0000 Subject: [PATCH 1/2] Fix broken Allowlisted Hooks link on the v4 hook routing page The "Allowlisted Hooks" link on content/protocols/v4/concepts/hook-routing.mdx pointed at support.uniswap.org/hc/en-us/articles/41305283155597-Allowlisted-Hooks, which returns HTTP 404 for a logged-out reader (the Zendesk article id no longer exists: the help-center API answers RecordNotFound for 41305283155597). Point it at the allowlist source of truth instead: https://github.com/Uniswap/uniroute-public/blob/main/src/lib/poolCaching/util/hooksAddressesAllowlist.ts Uniswap/uniroute-public is a public repository and the file resolves with HTTP 200 unauthenticated on the default branch. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016NBfmXuBzyQ5arpLrLpJ3g --- content/protocols/v4/concepts/hook-routing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/protocols/v4/concepts/hook-routing.mdx b/content/protocols/v4/concepts/hook-routing.mdx index 4aa8e9cef..d5c91884d 100644 --- a/content/protocols/v4/concepts/hook-routing.mdx +++ b/content/protocols/v4/concepts/hook-routing.mdx @@ -19,5 +19,5 @@ For implementation details, check [UniswapX Documentation](/docs/liquidity/unisw If you have built a hook that you would like to have allowlisted, fill out the [hook allowlisting form](https://www.notion.so/uniswaplabs/1aec52b2548b80f78dbef8d2f0d7183e). -You can review current allowlisted hooks in [Allowlisted Hooks](https://support.uniswap.org/hc/en-us/articles/41305283155597-Allowlisted-Hooks). +You can review current allowlisted hooks in [Allowlisted Hooks](https://github.com/Uniswap/uniroute-public/blob/main/src/lib/poolCaching/util/hooksAddressesAllowlist.ts). From 720b512a5f56b080b66f96e66436368db5730c2f Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 15 Sep 2026 17:55:44 +0000 Subject: [PATCH 2/2] Point hook builders to the allowlisting criteria The Hook Allowlisting section linked the submission form and the current allowlist, but nothing told builders what a hook has to look like to be allowlisted. Add a sentence linking the "Routing for hooked pools" support article, which documents both when a hook needs manual allowlisting and the criteria that improve its chances. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016NBfmXuBzyQ5arpLrLpJ3g --- content/protocols/v4/concepts/hook-routing.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/protocols/v4/concepts/hook-routing.mdx b/content/protocols/v4/concepts/hook-routing.mdx index d5c91884d..f71a6da3c 100644 --- a/content/protocols/v4/concepts/hook-routing.mdx +++ b/content/protocols/v4/concepts/hook-routing.mdx @@ -19,5 +19,7 @@ For implementation details, check [UniswapX Documentation](/docs/liquidity/unisw If you have built a hook that you would like to have allowlisted, fill out the [hook allowlisting form](https://www.notion.so/uniswaplabs/1aec52b2548b80f78dbef8d2f0d7183e). +You can look up the current allowlisting criteria in [Routing for hooked pools](https://support.uniswap.org/hc/en-us/articles/48291859140621-Routing-for-hooked-pools). + You can review current allowlisted hooks in [Allowlisted Hooks](https://github.com/Uniswap/uniroute-public/blob/main/src/lib/poolCaching/util/hooksAddressesAllowlist.ts).