Melon Dev Update — July 2017

First things first, the first Melon Manager Competition was a great success and we wanted to thank all participants and congratulate the winners of this very first round: Goat, Passive Gains LTD and Fake Internet Money!

Now, hello from the Melon Dev Team! 👋 👩🏽‍💻👨🏼‍💻👨🏻‍💻👨‍💻👨🏻‍💻

July has been quite eventful for us!! Here is what we have been up to for the v0.2 release:

SMART CONTRACTS

  • We added a lot of tests to the protocol, along with a coverage tracker to have better visibility on our codebase coverage.
  • We added a Logging contract, in an effort to gather all relevant vault events in the same contract. This will enhance performance on the front-end by making it more convenient to listen for any vault related events.
  • We added a bunch of new ERC20 tokens in the Melon universe of assets.
  • We began using MLN as a native currency in the protocol (wow!) and modified some subscribe/redeem functionality.

OYENTE

  • OneNorth, the v0.2.0 of Oyente was released.
  • Fresh reminder for those wondering but what is Oyente? Oyente is a symbolic execution based analyser for Ethereum smart contracts. It is a tool to analyze Ethereum smart contracts directly at the EVM bytecode level and look for potential security issues. Open source. How cool is that?

DAEMON

  • We performed an important refactoring of Daemon, our beloved liquidity provider. We refined spread occurrence and width, and modified the way Daemon handles the process of replacing existing orders with new ones, in an effort to have better consistency of orders frequency.
  • We made the necessary changes for Daemon to provide liquidity for the new assets available and redesigned some processes to make it more straight-forward in the future to add new assets.

PORTAL

  • We undertook a wide (and much needed!) refactoring of the portal in an effort to improve the quality and efficiency of our codebase.
  • We started our journey from Blaze to Redux/React, which massively improved our state management practices. We also started to put into practice our new coding standards.
  • We created Melon.js, a javascript API for the Melon Protocol! It aims to make interaction with the Melon protocol as developer friendly as possible. We wrote a nice and fully-tested suite of functions to interact with our smart contracts. Our intention is to make it as easy as possible for developers out there to build their own version of the portal; Melon.js is a big step towards that direction. More details on that in an upcoming blog post… Stay tuned!
  • We addressed a number of performance issues that stemmed from our need to synchronize our database with the blockchain for sensitive information (growing number of vaults, orders and trades). We are still looking into all possible solutions to provide our users with the best experience possible.
  • We integrated the new ERC20 assets in order to make the asset management experience feel more realistic (v0.2 : 17 new assets available).

DESIGN

  • We worked on the design of the M-0 website (the very first Swiss blockchain conference for asset management, brought to you by Melonport).
  • We worked on a new design system, Blocks, a modular, flexible and beautiful UI pattern library that we can use across different places. It is basically a cool design tool for our entire team and it will make our transition to React super efficient.
  • We started working on a new design for the Melonport website (coming out soon!) and branding for Melon.network.

The organization and implementation of the first Melon Manager Competition kept us pretty busy as well, we hope participants enjoyed it (despite server downtime on the last day) and again, we thank everyone for the great engagement with what we’re building! We gathered incredibly valuable feedback from users, which will help us iterate in the right direction for the next release/competition.

If you have any feedback/suggestions for us -or just want to chat with us, please join our Gitter channel.

Melon Dev Team ❤ 🍉

Show your support

Clapping shows how much you appreciated Jenna Zenk’s story.