mirror of
https://github.com/luxfi/uni-v3-subgraph.git
synced 2026-07-27 03:01:58 +00:00
zeekayandHanzo Dev
991fbb3053
getSubgraphConfig() keys off dataSource.network() and only knows 'lux' (chainId 96369) — with any other value the Factory handler throws "Unsupported network" on the first PoolCreated and the deployment never indexes a single pool. The Lux config (V3 factory 0x80bBc7C4…, WLUX, LUSD/USDC/USDT stablecoins, the WLUX/LUSD price pool) has been correct in chains.ts all along; only the manifest's network label was wrong, so this subgraph could never run. Also drops a white-label brand name that must never appear in a luxfi repo. Deployed as luxfi/amm-v3 on graph-node in lux-mainnet; indexes 27 live V3 pools with $3.0M TVL. Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Uniswap V3 Subgraph
Subgraph Endpoint
Synced at: https://graph.lux.network/subgraphs/name/lux/uniswap-v3?selected=playground
Pending Changes at same URL
Running Unit Tests
- Install Docker if you don't have it already
- Install postgres:
brew install postgresql yarn run build:dockeryarn run test
Adding New Chains
- Create a new subgraph config in
src/utils/chains.ts. This will require adding a new<NETWORK_NAME>_NETWORK_NAMEconst for the corresponding network. - Add a new entry in
networks.jsonfor 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. - 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>