Goo Exchange · Robinhood Chain
Integrate Goo Exchange pools
Goo's CL pools use Uniswap V3-style math, events and swap callback interfaces. The key address-computation difference is that CREATE2 deployment is performed by a separate pool deployer, not the factory.
- Factory
0x221A6239E40709792b0d4bdc140fA36158CD41C7- Pool deployer
0x9eF8bfae948B012EDD9e902Beb0d55F475631396- Pool init code hash
0x361074a657704920539a5187a0873cfbb0bf83771a463c46c98e615554bf9264- Factory discovery start
- Block 73266708
Pool lookup and CREATE2
Use factory.getPool(tokenA, tokenB, fee) to locate an existing pool. For address computation, sort the tokens and use salt = keccak256(abi.encode(token0, token1, fee)), the pool deployer above as the CREATE2 parent, and the compiled pool init code hash. Using the factory as the parent produces a different address.
| Swap fee | Tick spacing |
|---|---|
| 0.05% | 10 |
| 0.25% | 50 |
| 0.3% | 60 |
| 0.9% | 180 |
| 1% | 200 |
| 10% | 1000 |
| 20% | 2000 |
Default protocol fee
A newly initialized pool obtains the factory's default protocol fee atomically, even if it was created outside the web app. Changes use the FactoryController's notice mechanism. Protocol denominators are disabled or the supported V3 denominators; they are not arbitrary basis-point values.
Quotes, decimals and supported settlement
Goo's native router handles exact input, WETH/native ETH conversion and multiple CL hops. It refuses partial fills. Tokens with transfer fees or incompatible rebasing behavior are not established as supported by merely implementing ERC-20 methods. Parse decimals explicitly and label raw stock-token amounts separately from underlying shares.
Integration JSON · Deployment manifest · Current chain facts · Full contract interfaces.
Onchain snapshot: , Robinhood Chain block 78146108. This is an observation at that block, not a continuously updated quote. Read current protocol facts.