Build on top of DerivaDEX smart contracts
- Pick the exact DerivaDEX environment before you bind any address or ABI.
- Load the published address set from the current public contract reference.
- Bind facet ABIs to the DerivaDEX diamond proxy address rather than to facet implementation addresses.
- Separate contract-driven actions from API-driven market-data and sequencing workflows.
- Verify the result against the correct environment after every write or governance-sensitive interaction.
Start with environment targeting
- Open Smart Contract Addresses and Core Contract Reference.
- Confirm the environment label, chain ID, and contract address set match the deployment you actually intend to target.
- Do not rely on chain ID alone when multiple published environments share the same chain.
Bind the diamond correctly
- Use the DerivaDEX diamond address as the call target for protocol-facing interactions.
- Use the ABI or interface that matches the facet function you need, but bind it to the diamond address.
- Keep the interaction layer typed so selector mistakes and upgrade drift are easier to detect.
Keep the contract layer separate from market-state integration
- use contract surfaces for on-chain actions, governance-linked operations, and settlement-adjacent reads
- use REST for initial public market or account snapshots
- use realtime feeds for live updates and order/account event streams
Recheck upgrade-sensitive assumptions
- Treat selector availability as deployment-dependent rather than timeless.
- Re-verify ABI and selector assumptions after upgrades or environment changes.
- Reconfirm that a non-zero address in the published environment set still matches the surface your integration expects.