feat: Add Sepolia support

[fadeev]

Before merging

• Merge Add Sepolia, remove Goerli networks#32
• Release new version of networks (currently, using a pre-release version)
• Add ZETA token consumer
• Add Uniswap v2/v3 router addresses
• Update networks package version in this branch

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@types/[email protected]	None	0	6.27 kB	types
npm/@zetachain/[email protected]	environment Transitive: filesystem	+1	108 kB	lucasjanon
npm/[email protected]	None	0	8.95 kB	75lb
npm/[email protected]	environment, filesystem	+1	19.3 kB	tootallnate
npm/[email protected]	None	0	5 kB	vweevers
npm/[email protected]	None	0	68.4 kB	holgerd77
npm/[email protected]	None	0	11 kB	vweevers

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

View full report↗︎

[fadeev]

@andresaiello I need to know zetaTokenConsumerUniV2, uniswapV2Router02, uniswapV3Router for Sepolia. (these addresses cannot be fetched from chain).

[fadeev]

For Uniswap router contract address on Sepolia, I'm using the universal router from https://docs.uniswap.org/contracts/v3/reference/deployments

[fadeev]

I still don't know zeta token consumer address on Sepolia, which is needed for CCM, but I suppose we can add it later.

[fadeev]

Is this the consumer address?

https://sepolia.etherscan.io/address/0x7e792f3736751e168864106AdbAC50152641A927

[lumtis]

Addresses looks legit to me.

Wondering why do we store some addresses in duplicate in task/addresses?

[fadeev]

@lumtis addresses in the tasks are the ones that we cannot fetch from anywhere.

[fadeev]

Basically, these addresses are copied to the final JSON as is, the rest are fetched from chain/other contracts.

[lumtis]

Seems like the Uniswapv3 address fix is out of the scope of the PR title but LGTM