Alternatives

dYdX Alternatives — Evidence Comparison

Alternative venues are shown for evidence comparison and are not recommendations. They are included because published evidence attributes differ from dYdX — not because dYdX is “bad”, and not because of commercial relationships.

dYdX record Visit dYdX

Why these venues are included

Each candidate differs from dYdX on at least one published evidence attribute (regulation, legal-entity mapping, PoR, custody, geographic records, products, or completeness). Inclusion is deterministic from the public snapshot.

Evidence attributes

Venue	Regulation	Legal entities	PoR	Custody	Geographic scope	Products	Coverage
dYdX	0	2	0	2	9	1	4 / 7i
Crypto.com	2	3	1	3	38	2	7 / 7i
Binance	4	4	1	3	3	4	7 / 7i
Bitget	1	1	1	1	28	4	7 / 7i
Bybit	1	1	1	1	15	6	7 / 7i
Gate	1	1	1	7	35	3	7 / 7i

Crypto.com

Venue architectureRegulatory evidenceCustody modelPoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction

— Published venue boundary differs (interface vs exchange). Interface/protocol presentation is kept distinct from custodial exchange records.
— Regulatory records on file: dYdX 0 (exact IDs 0) vs Crypto.com 2 (exact IDs 2).
— Custody claim records: dYdX 2 vs Crypto.com 3.
— PoR snapshots on file: dYdX 0 vs Crypto.com 1 (PoR ≠ audit).

Explore record Visit Crypto.com

Binance

Regulatory evidenceCustody modelPoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction

— Regulatory records on file: dYdX 0 (exact IDs 0) vs Binance 4 (exact IDs 4).
— Custody claim records: dYdX 2 vs Binance 3.
— PoR snapshots on file: dYdX 0 vs Binance 1 (PoR ≠ audit).
— Fee snapshots on file: dYdX 0 vs Binance 2.

Explore record Visit Binance

Bitget

Regulatory evidenceCustody modelPoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction

— Regulatory records on file: dYdX 0 (exact IDs 0) vs Bitget 1 (exact IDs 0).
— Custody claim records: dYdX 2 vs Bitget 1.
— PoR snapshots on file: dYdX 0 vs Bitget 1 (PoR ≠ audit).
— Fee snapshots on file: dYdX 0 vs Bitget 2.

Explore record Visit Bitget

Bybit

Regulatory evidenceCustody modelPoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction

— Regulatory records on file: dYdX 0 (exact IDs 0) vs Bybit 1 (exact IDs 0).
— Custody claim records: dYdX 2 vs Bybit 1.
— PoR snapshots on file: dYdX 0 vs Bybit 1 (PoR ≠ audit).
— Fee snapshots on file: dYdX 0 vs Bybit 2.

Explore record Visit Bybit

Gate

Regulatory evidenceCustody modelPoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction

— Regulatory records on file: dYdX 0 (exact IDs 0) vs Gate 1 (exact IDs 1).
— Custody claim records: dYdX 2 vs Gate 7.
— PoR snapshots on file: dYdX 0 vs Gate 1 (PoR ≠ audit).
— Fee snapshots on file: dYdX 0 vs Gate 2.

Explore record Visit Gate

What remains unresolved

Open questions and missing domains stay unknown. An empty cell is not a safety finding.

dYdX: dYdX Operations Services Limited / dYdX Trading Inc. named; DTI states it does not operate public deployments — no licence record packaged. Re-audited 2026-09-13: keep THIN; do not invent fills.
dYdX: DEX/software — no PoR product applicable / no disclosure found
Crypto.com: HISTORICAL only: Mazars AUP as of 2022-12-07 still hosted. Re-check 2026-09-13 found no newer dated official Exchange PoR / attestation / wallet disclosure snapshot. STALE as current reserve evidence — do not present as current.
Crypto.com: Status page located; no dated material incident structured (status≠incident)
Binance: ADGM Nest trio roles mapped from official ADGM Terms; Binance FZE mapped from FZE Terms + VARA VL/24/04/001. Do not treat any single entity licence as brand-wide global authorisation. Nest Trading Limited role kept as unknown enum (broker-dealer/off-exchange per terms) pending richer role taxonomy.
Bitget: FSA Seychelles lists BTG Technology Holdings Limited on the VASP Assessment list (2026-03-09). Not a granted licence. Operator marketing licences (AUSTRAC etc.) were not confirmed on primary registers in this pass; VARA public register has no Bitget VASP licence row (2026-09-13).
Bitget: No confirmed primary incident record packaged
Bybit: SATOS partnership terms are regional/partner-scoped; not applied as global Bybit custody. Added PoR wallet-disclosure claim only.

Limitations

This is not a “best alternative” ranking. Evidence differences can change as records are re-verified. Regional records do not imply global approval.