Crash report: `Error: No V2 factory address on this chain`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
URL
Error
Error: No V2 factory address on this chain
Stacktrace
Error: No V2 factory address on this chain
at M (https://app.cbswap.io/static/js/main.be6aa2c8.chunk.js:1:32753)
at https://app.cbswap.io/static/js/main.be6aa2c8.chunk.js:1:502538
at Array.map (<anonymous>)
at https://app.cbswap.io/static/js/main.be6aa2c8.chunk.js:1:502488
at Object.Aa [as useMemo] (https://app.cbswap.io/static/js/35.430ed3d8.chunk.js:2:1281571)
at t.useMemo (https://app.cbswap.io/static/js/35.430ed3d8.chunk.js:2:1216590)
at ns (https://app.cbswap.io/static/js/main.be6aa2c8.chunk.js:1:502466)
at ua (https://app.cbswap.io/static/js/35.430ed3d8.chunk.js:2:1276838)
at Ha (https://app.cbswap.io/static/js/35.430ed3d8.chunk.js:2:1286405)
at $u (https://app.cbswap.io/static/js/35.430ed3d8.chunk.js:2:1330129)
Device data
{
"ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36",
"browser": {
"name": "Chrome",
"version": "112.0.0.0",
"major": "112"
},
"engine": {
"name": "Blink",
"version": "112.0.0.0"
},
"os": {
"name": "Windows",
"version": "10"
},
"device": {},
"cpu": {
"architecture": "amd64"
}
}
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
Reproduce the crash at https://app.cbswap.io/#/pool and use the stack trace locations in main.be6aa2c8.chunk.js as the entry point. Identify which chain lacks a V2 factory address and verify that the pool page no longer crashes for that chain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100