404 from uniswap backend when using UI to add liquidity
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Our V4 pool on Base works for the pool page but fails when adding liquidity with "Pool is missing tickSpacing" (404 from your backend).
Pool ID:
0x4965830819a7f6d799cd57917441052403219031ce8b67f292741015c54834bc
Hook:
0xf13f646e4b246f8089d45fa22f51317121e60180 (verified on Blockscout).
Tokens:
EURC/USDC, fee 3000, tickSpacing 60. Pool is initialized on-chain and the Envio indexer has it. A previous pool with identical permissions and tokens works
fine (pool 0x6474c309551b8c70f939e7042bddb5a742910f0d90e017c41b976764ce5ca88e). The request payload sends poolReference correctly but the response returns 404 with "Pool is missing tickSpacing".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the UI add-liquidity flow and its request carrying poolReference, then compare the failing Base pool's backend or indexer metadata with the known-working pool. Done means the failing pool's tickSpacing is returned and liquidity can be added without the 404 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100