Donate to L2BEAT's Gitcoin grant. A new matching round has just started!

dYdX logodYdX

TVL: $982 M

+5.77% / 7 days






dYdX aims to build a powerful and professional exchange for trading crypto assets where users can truly own their trades and, eventually, the exchange itself.

Risk summary


Validity proofs ensure state correctness[Edit][Issue]

Each update to the system state must be accompanied by a ZK Proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. Once the proof is processed on the Ethereum blockchain the L2 block is instantly finalized. The system state is represented using Merkle roots.[1]

    Zero knowledge STARK cryptography is used[Edit][Issue]

    Despite their production use ZK-STARKs are still new and experimental cryptography. Cryptography has made a lot of advancements in the recent years but all cryptographic solutions rely on time to prove their security.[2]

    • Funds can be stolen if the cryptography is broken or implemented incorrectly.

    All data required for proofs is published on chain[Edit][Issue]

    All the relevant data that is used to recover the L2 balances Merkle Tree is published on-chain as calldata. This includes, in addition to the proven new state, the complete list of differences of the users' balances from the previous state.[3][4]


      The system has a centralized operator[Edit][Issue]

      The operator is the only entity that can propose blocks. A live and trustworthy operator is vital to the health of the system. Typically, the Operator is the hot wallet of the StarkEx service submitting proofs for state updates.[5]

      • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

      Users can force exit the system[Edit][Issue]

      Force exit allows the users to escape censorship by withdrawing their funds. The system allows users to force the withdrawal of funds by submitting a request directly to the contract on-chain. The request must be served within a defined time period. If this does not happen, the system will halt regular operation and permit trustless withdrawal of funds. Perpetual positions can also be force closed before withdrawing, however this requires the user to find the counterparty for the trade themselves.[6][7]

      • Users can be censored if the operator refuses to include their transactions. They can still exit the system.
      • Funds can be lost if the user is unable to find the counterparty for the force trade.


      Regular exit[Edit][Issue]

      The user initiates the withdrawal by submitting a transaction on L2. When the block containing that transaction is proven the funds become available for withdrawal on L1. Finally the user submits an L1 transaction to claim the funds. This transaction does not require a merkle proof.[8]

        Forced exit[Edit][Issue]

        If the user experiences censorship from the operator with regular exit they can submit their withdrawal requests directly on L1. The system is then obliged to service this request. Once the force operation is submitted if the request is serviced the operation follows the flow of a regular exit.[9][10][11]

          Emergency exit[Edit][Issue]

          If enough time passes and the forced exit is still ignored the user can put the system into a frozen state, disallowing further state updates. In that case everybody can withdraw by submitting a merkle proof of their funds with their L1 transaction.[9][10][11]

            Smart Contracts[Edit][Issue]

            The system consists of the following smart contracts:

            The current deployment carries some associated risks:

            • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).


            1. Enforcing Consistency on the On-Chain State - StarkEx documentation
            2. Stark Curve - StarkEx documentation
            3. ZK-Rollup - StarkEx documentation
            4. UpdatePerpetualState.sol#L82 - Etherscan source code
            5. Operator - StarkEx documentation
            6. Censorship Prevention - StarkEx documentation
            7. Forced Trade - StarkEx documentation
            8. Withdrawal - StarkEx documentation
            9. Forced Operations - StarkEx documentation
            10. Forced Withdrawal - StarkEx documentation
            11. Full Withdrawal - StarkEx documentation