ENS <> Melon
Last weekend, part of the Melon team was attending the ENS workshop and hackathon in London. We took that occasion to integrate ENS with Melon.
From now on, the latest version of our deployed contracts on the main net will point to the following ENS subdomains:
- version.melonfund.eth (Version contract)
- governance.melonfund.eth (Governance contract)
- canonicalpricefeed.melonfund.eth (Canonical Pricefeed contract)
- matchingmarketadapter.melonfund.eth (OasisDex adapter contract)
- zeroexv1adapter.melonfund.eth (Zero Ex Adapter contract)
- compliance.melonfund.eth (Compliance contract)
- ranking.melonfund.eth (Funds Ranking contract)
- riskmanagement.melonfund.eth (Risk Management contract)
- olympiad.melonfund.eth (Olympiad contract — currently Naxos)
- deployer.melonfund.eth (Deployer contract)
- authority.melonfund.eth (Authority contract)
You can now look up our main net contracts on Etherscan only using those names! With each new main net release, we will update the addresses those names resolve to.
We just launched Naxos yesterday, so the above ENS subdomains point to all the contracts used in Naxos :)
As a side note, we were quite impressed by the awesome organization of this healthy hackathon by the ENS team! Kudos to the ENS team and to all the participants!
This blog post is subject to change as the research & development phase is ongoing. Melonport will aim to update blog-posts regularly to represent our latest thinking on a best-efforts basis but there may occasionally be time-lags between latest thinking and updated documentation. With this in mind, the author of this blog assumes no responsibility or liability for any errors or omissions in the content of this blog.
