Contracts & sources
Start from the canonical market address, then follow its contract graph and source evidence.
Deployed Family V1 mechanicsOne factory, isolated families
The reusable CatchFamilyFactoryV1 creates a separate token, release vault, reserve vault, hook, liquidity locker, fee ledger and release controller for each family. A shared factory does not pool their reserves or make tokens interchangeable.
The canonical factory on Robinhood Chain (4663) is 0x21acBCC6227Cf5D2Fb5eB876735edd04F7B49c12. Follow each market’s Contracts & pool section for the admitted component graph. Verify both chain and address; a familiar ticker alone proves nothing.
What the evidence establishes
Launch evidence ties the mined transaction, Safe execution, runtime identities and launch state to the admitted family. Explorer source verification is a separate correspondence check. The 7 September 2026 publication evidence records exact Sourcify creation and runtime matches for 71 contracts: the shared factory and seven components for each of ten live families, including every token and hook.
The seven code depots have partial source verification on Blockscout and independently checked exact bytecode payloads. They do not have successful Sourcify matches. Blockscout badges may lag Sourcify results; the evidence does not claim an exact Blockscout badge for every address. Source correspondence is not an independent audit, safety guarantee or router approval.
The source-only catch-exchange/catch-contracts repository publishes exact Solidity sources, ABIs, compiler inputs and the deployment directory for all ten live families. Versioned releases preserve the source record. Private development history and operator material remain separate. Publishing a new documentation version does not change an immutable deployed contract.
Review and regression testing
The development programme includes AI-assisted Pashov Solidity auditor and EthSkills EVM reviews across separate Codex and Claude sessions, executable edge-case tests, stateful invariants and focused remediation reviews. These are framework-assisted project reviews, not an audit commissioned from Pashov Audit Group or an endorsement by the framework authors.
The public review history identifies candidate boundaries, design dispositions and test limitations. It includes the latest bounded regression: 40 Solidity tests, including six invariants at 256 runs and 128,000 calls each, plus 10 economic simulator tests. Public CI separately verifies exact compilation and package integrity; it does not run the private contract-test harnesses.
Hook routing is per deployment evidence
Each family has its own hook address and immutable configuration. Do not assume a third-party approval for one address covers another family. Catch’s direct canonical-pool swaps, Uniswap interface routing and 0x/Matcha routing are distinct paths.
Inspect the public record
source-v1.0.2 · source, review evidence and reproducible builds.
Browse the versioned sourcesThe shared factory and each family’s deployed component code.Source verification evidence71 exact Sourcify matches and the seven code-depot exceptions.Review and testing historyFramework runs, remediation, edge cases and evidence boundaries.Reproduce the compilationPinned inputs and checks for all eight compiler targets.Release recordWhat changed in this public source publication.Live token references
These token addresses come from the versioned public deployment directory. Source evidence is separate from current market health and transaction checks.
The live market directory shows admitted markets and their current indexed observations. Open a market for its component graph.