Skip to main content

​
Deployment and additional resources

Forkast publishes verified Conditional Token Framework deployments on Polygon Amoy and mirrors the exact same layout on mainnet. We also reuse the canonical Gnosis contracts, so any bytecode you compile from the upstream repository matches what is already live. Use the guidance below whenever you need to inspect a contract, rebuild calldata, or audit a new release.

​
Discovering contract addresses

  • Follow the release notes in the Forkast Discord or reach out to [email protected] whenever you need the latest Amoy contract map. We publish every ConditionalTokens, FPMMDeterministicFactory, and FixedProductMarketMaker deployment there with verified ABIs.
  • When interacting via the relayer, use GET /core/get-deployed to confirm whether your Safe already exists on the current network before approving CTF calls.
  • Prefer deterministic deployments (CREATE2) for helper contracts. You can pre-compute the final address off-chain and bake it into your subgraph mappings or front-end configuration.

​
Tooling checklist

  1. Add a Polygon Amoy RPC to your wallet or backend (for example, https://rpc-amoy.polygon.technology).
  2. Install conditional-tokens-contracts or compile the contracts locally with Foundry/Hardhat.
  3. Reuse Forkast’s publicly available ABIs from our API responses or from the verified contracts on the explorer.
  4. Run smoke tests by splitting a small amount of Amoy USDC, trading the outcomes, and merging them back before hitting production.

​
Helpful references

  • Sample scripts in the Forkast engineering repo — use these as starting points for Foundry/Hardhat tasks (request access via support if you need it).
  • Polygon RPC catalog — alternative Amoy endpoints when a provider is under maintenance.
  • CTF source code — audited implementation used by Forkast.
  • Audit results — independent reviews of the contracts we rely on.
  • Position ID walkthrough — reference math for deriving ERC-1155 token IDs locally.
Need confirmations that a specific Amoy deployment matches the bytecode you compiled? Reach out to [email protected] with the contract name and commit hash—our team will supply the exact address, constructor arguments, and verification artifacts.