Skip to main content
DZap routes trades through one router per chain, DZapDiamond, and zaps through its zap contract. These are the contracts users approve, so look them up at runtime when you can. The tables below are a snapshot, checked against each chain.

Look up at runtime

DZapDiamond

The router is a diamond (EIP-2535) and runs version v2 on every EVM chain. Deployed is when the contract was created on that chain; the router is upgraded in place, so later changes don’t move this date. A blank date means no public archive node could confirm it.

Testnets

Zap contract

The zap contract has the same address on every chain below: 0xCE2541ce645A1B232fF2fead53dcD9f369E86bA4. Zaps run on the chains marked in the Chain Support Matrix; elsewhere the contract is deployed but not in use yet.

Permit2

Permit2 is Uniswap’s approval contract, which DZap uses for signature-based approvals. It’s at 0x000000000022D473030F116dDEE9F6B43aC78BA3 except on these chains, where the SDK uses the address below: On Core, the router has no Permit2 set, so use a standard approval there.

Solana and Sui

On Solana and Sui, DZap adds a call to a tracking program that records the DZap transaction ID on-chain.

ABIs and source

Audit reports are on Security & Audits.
Last modified on October 14, 2026