Testnet factory required for integration launches
Pons launchToken works on Robinhood Chain mainnet (4663), but the same factory / locker addresses have no bytecode on testnet (46630). Third-party launchers cannot dry-run or live-test CREATE2 prediction, factory fee, LP lock, protection (TF), or creator-fee claim without spending mainnet ETH.
This is a deployment / address-book gap, not a request to change mainnet contracts.
Confirmed live root cause
Read-only probe on 2026-09-05 against https://rpc.testnet.chain.robinhood.com:
| Check |
Result |
| Chain ID |
46630 |
Mainnet factory 0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feB on testnet |
no code |
Legacy factory 0x0c37a24F5D23A486FA692d1500881d698B1F77a4 on testnet |
no code |
Mainnet locker 0x736D76699C26D0d966744cAe304C000d471f7F35 on testnet |
no code |
Testnet WETH 0x7943e237c7F95DA44E0301572D358911207852Fa |
has code |
| Community Uni V3 (SwapRouter02 / Position Manager) |
has code |
eth_getCode on the published mainnet factory on testnet returns empty. launchEnabled() cannot be called. Independent tools therefore fall back to a custom ERC-20 + Uni V3 LP path, which is not a Pons launch (no factory, no Pons locker, no Pons fee claim).
Mainnet identity (do not replace)
- Factory:
0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feB
- Legacy factory:
0x0c37a24F5D23A486FA692d1500881d698B1F77a4
- Locker:
0x736D76699C26D0d966744cAe304C000d471f7F35
- Legacy locker:
0x31ca5E101941A93A7DD6d0497928700625CF54B5
- Chain: Robinhood Mainnet
4663
Minimal safe fix
Please deploy the current Pons launch stack on testnet or publish the official testnet addresses if they already exist elsewhere:
- Deploy factory + locker on chain
46630 with the same launchToken / CREATE2 / launchEnabled / launchFee surface as mainnet.
- Publish testnet factory, locker, WETH, and launchConfig/dex IDs in this repo (README or
deployments/testnet.json).
- Keep mainnet addresses unchanged.
- Confirm a test
launchToken with a tiny creator buy succeeds, launchEnabled() is true, and the token page (or explorer) indexes the testnet token.
No mainnet upgrade, no metadata change, and no change to existing mainnet launches.
Acceptance
Testnet factory required for integration launches
Pons
launchTokenworks on Robinhood Chain mainnet (4663), but the same factory / locker addresses have no bytecode on testnet (46630). Third-party launchers cannot dry-run or live-test CREATE2 prediction, factory fee, LP lock, protection (TF), or creator-fee claim without spending mainnet ETH.This is a deployment / address-book gap, not a request to change mainnet contracts.
Confirmed live root cause
Read-only probe on 2026-09-05 against
https://rpc.testnet.chain.robinhood.com:466300xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feBon testnet0x0c37a24F5D23A486FA692d1500881d698B1F77a4on testnet0x736D76699C26D0d966744cAe304C000d471f7F35on testnet0x7943e237c7F95DA44E0301572D358911207852Faeth_getCodeon the published mainnet factory on testnet returns empty.launchEnabled()cannot be called. Independent tools therefore fall back to a custom ERC-20 + Uni V3 LP path, which is not a Pons launch (no factory, no Pons locker, no Pons fee claim).Mainnet identity (do not replace)
0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feB0x0c37a24F5D23A486FA692d1500881d698B1F77a40x736D76699C26D0d966744cAe304C000d471f7F350x31ca5E101941A93A7DD6d0497928700625CF54B54663Minimal safe fix
Please deploy the current Pons launch stack on testnet or publish the official testnet addresses if they already exist elsewhere:
46630with the samelaunchToken/ CREATE2 /launchEnabled/launchFeesurface as mainnet.deployments/testnet.json).launchTokenwith a tiny creator buy succeeds,launchEnabled()is true, and the token page (or explorer) indexes the testnet token.No mainnet upgrade, no metadata change, and no change to existing mainnet launches.
Acceptance
eth_getCodeon the published testnet factory is non-emptylaunchEnabled()returns truelaunchTokenwith CREATE2-predicted address succeeds on 46630