Endpoints
Hosts and chain ID are filled in by the partner onboarding package —
copy them once and pin in your client config. The runtime
GET /api/platform/contracts endpoint also exposes them so SDKs can
read at boot rather than hardcoding.Contract registry
Orders are signed under the domain{ name: "PredictStreet", version: "1", chainId: 36900, verifyingContract }.
Use NegRiskCtfExchange when the market’s negRiskEligible is true,
and CTFExchange (binary) otherwise. An order signed against the wrong
exchange is rejected with bad_signature.
Vault operations (withdrawals, split / merge / convert) are not signed
against any address in this table. They use your own vault’s domain
(name: "PredictStreetVault", verifyingContract = your vault address
from VaultFactory.vaultOf(yourWallet)), never the VaultFactory
address.
Verified production deployments. These are the authoritative target
for every EIP-712 verifyingContract field and the only addresses
the platform recognises.
Read-at-runtime — GET /api/platform/contracts
The address table above is the human-readable form of the canonical
contract registry. For SDK code prefer the runtime endpoint:
usdcEip712is thename/versionof the USDC contract’s EIP-712 domain. Use exactly these values when you build thePermitfor a gasless deposit; any other values recover a different signer and the relay answerspermit_signer_mismatch.ccipBridgecarries{ destChainSelector }for cross-chain withdrawals over Chainlink CCIP, ornullwhen the environment has no bridge configured (cross-chain withdrawals are then unavailable).generatedAtis the time the response was generated, not a deploy timestamp — diff the addresses to detect a redeploy.
fetch() this at boot
rather than hardcoding constants.
Production guarantees
- No
MOCK_AUTH_ACCEPT_ALL— every EIP-712 signature is verified against the on-chainCTFExchange/NegRiskCtfExchange/Vaulttypehashes. - Full compliance chain — KYC, geo / sanctions screening, and AML screening of withdrawal destinations are enforced. Withdrawals are not limited to addresses that deposited before; to restrict destinations, use the address whitelist.
- HSM-backed oracle signer — the platform oracle private key never leaves a hardware module.
- Multi-sig administrative controls —
cancel,void, and platform-kill require multiple signatures from documented officers. - No in-place redeploys — any contract change ships as a new deployment with a coexistence period and explicit migration instructions delivered via the partner channel. Addresses on this page are stable for the lifetime of the current deployment.
Onboarding
Request access
Sign the partner agreement and receive your API keys + connection
runbook.
Web app
The public retail site.