On July 12th, the 0x team had to upgrade their smart contracts, due to a security vulnerability disclosed by a third-party security researcher (the vulnerability was not exploited). The 0x team reacted promptly, and shut down the 0x Exchange v2.0 contracts and deployed patched contracts. As a result, the 0x v2.0 contracts cannot process trades and are unable to be used going forward.

Implication for existing Melon funds

The Melon funds that were deployed with 0x as an authorized exchange will therefore be unable to trade (make orders or take orders) on 0x going forward.

Existing funds are not able to update or add an exchange address. By design, a Melon fund configuration cannot be changed once it has been deployed. Your fund will still be able to trade on the other exchanges you authorized.

If you’d like to use Melon with 0x, you will need to redeploy a fund using the latest Melon Manager Interface.

Melon Manager Interface v1.0.2

This new release is a frontend release (protocol version remains the same). It contains the updater contract addresses for 0x, which means that next time you deploy a fund, it will be deployed with the patched 0x v2.1 contracts, and you will then be able to trade on 0x.

For this release, we decided to raise the maximum AUM per fund from 5,000 DAI to 10,000 DAI.

This release also contains some minor front-end fixes (see release notes).