feat: enable v2 routing on all deployed L2

[just-toby]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

enables v2 routes on all deployed L2

• What is the current behavior? (You can also link to an open issue here)

currenty SOR assumes v2 isn't deployed on all L2

• What is the new behavior (if this is a feature change)?

support v2 routes on all deployed L2

• Other information:

[jsy1218]

Looks like the merge conflict needs to be resolved before Github CI runs the tests.

[cgkol]

Shall we run some tests to make sure this works on optmism before we push it?

[jsy1218]

Shall we run some tests to make sure this works on optmism before we push it?

I think we want to conduct some manual testing (and maybe add into integ-test as well):

1. getting the new UR deployed address https://uniswapteam.slack.com/archives/C05MF1J6GR5/p1704913678240789
2. deploy V2 tokens on optimism ourselves (preferably FOT)
3. create FOT/WETH pool
4. add liquidity into FOT/WETH pool
5. run router to make sure it can route through

We are blocked on 1 right now.

[jsy1218]

Also I just noticed that somehow for v2 pool-provider, SOR doesn't use FACTORY_ADDRESS from v2-sdk, but rather computes the pool address directly https://github.com/Uniswap/smart-order-router/blob/main/src/providers/v2/pool-provider.ts#L261. This was probably fine previously, because UR was not deployed for v2 pools. But now with UR with different factory addresses across chains, we might need to change the v2 pool-provider logic.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@uniswap/[email protected]	environment, eval Transitive: filesystem, network, shell, unsafe	+321	150 MB	jsy1218
npm/@uniswap/[email protected]	environment Transitive: eval, filesystem, network, shell, unsafe	+339	170 MB	jsy1218
npm/@uniswap/[email protected]	None	+2	5.9 MB	alicehenshaw
npm/@uniswap/[email protected]	environment	+22	2.01 MB	jsy1218
npm/@uniswap/[email protected]	environment, eval Transitive: filesystem, network, shell, unsafe	+319	149 MB	jsy1218

🚮 Removed packages: npm/@uniswap/[email protected], npm/@uniswap/[email protected], npm/@uniswap/[email protected], npm/@uniswap/[email protected], npm/@uniswap/[email protected]

View full report↗︎

[mikeki]

Overall LGTM, assuming it works

[jsy1218]

I noticed v2-sdk FACTORY_ADDRESS_MAP is missing CELO. This explains why the CELO integ-tests are consistently failing. We will need to bump v2-sdk to include re-deployed CELO address.

[jsy1218]

Shall we run some tests to make sure this works on optmism before we push it?

Sadly we aren't able to test on any deployed L2, including Optimism. The reason is because no has added liquidity on V2 deployed L2 yet. For example, the latest UniswapV2Router02 deployed Optimism shows no one ever invoked addLiquidity/addLiquidityETH of the write contract.

I think we want to merge this first, meanwhile getting to how to add liquidity to test routing.