zeekayandHanzo Dev d7837454da State a version once
A version written into a manifest is written into every manifest that wants it,
which is how eslint came to exist in a hundred and four forms across this estate
and how a package came to resolve twice at run time. The catalog moves the number
out of the manifest: a manifest names the package, the workspace names the
version.

Four are held below their latest because the newer release cannot be used, and
the reason is recorded rather than the version alone: @noble/hashes 2 renamed
every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package
that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels
3 points its types condition at the bundle.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 02:43:28 -07:00
2024-07-29 13:57:03 -04:00
2024-07-29 13:57:03 -04:00
2026-03-02 10:20:05 -05:00
2026-03-05 13:03:01 -05:00
2025-02-11 15:30:26 -05:00
2024-07-29 13:57:03 -04:00
2024-07-29 13:57:03 -04:00
2026-09-08 02:43:28 -07:00
2024-07-29 13:57:03 -04:00
2024-07-29 13:57:03 -04:00
2024-07-23 11:53:18 -04:00
2026-09-08 02:43:28 -07:00
2025-08-11 13:35:04 -04:00
2026-03-05 13:03:01 -05:00
2024-07-29 13:57:03 -04:00

Uniswap V4 Subgraph

Running Unit Tests

  1. Install Docker if you don't have it already
  2. Install postgres: brew install postgresql
  3. yarn run build:docker
  4. yarn run test

Adding New Chains

  1. Create a new subgraph config in src/utils/chains.ts. This will require adding a new <NETWORK_NAME>_NETWORK_NAME const for the corresponding network.
  2. Add a new entry in networks.json for the new chain. The network name should be derived from the CLI Name in The Graph's supported networks documenation. The factory address can be derived from Uniswap's deployments documentation (not yet available).
  3. To deploy to Alchemy, run the following command:
yarn run deploy:alchemy --
  <SUBGRAPH_NAME>
  --version-label <VERSION_LABEL>
  --deploy-key <DEPLOYMENT_KEY>
  --network <NETWORK_NAME>

Generating subgraph.yaml

The subgraph.yaml file can be automatically generated from the networks.json configuration for a specific network. This ensures that all contract addresses and start blocks are correctly synchronized.

To generate the subgraph.yaml:

  1. Make sure your networks.json is up to date with the correct contract addresses and start blocks
  2. Run:
    yarn generate-subgraph <network>
    
    For example:
    yarn generate-subgraph mainnet
    # or
    yarn generate-subgraph arbitrum-one
    

This will create a new subgraph.yaml file based on the network-specific configuration. The script will:

  • Use the contract templates defined for each contract type (PoolManager, PositionManager, etc.)
  • Generate data sources for each contract in the specified network
  • Preserve all the necessary event handlers and ABI configurations

Available networks can be found in networks.json.

S
Description
Subgraph for Uniswap V4
Readme GPL-3.0
1 MiB
Languages
TypeScript 99.7%
Dockerfile 0.3%