Launch Timeline Adjusted — New Target of May

MetronomeDAO
3 min readMar 23, 2018

--

Hello Metronome Community:

As of today, to ensure that Metronome is the best its authors can make it for launch the guidance for the Metronome launch is May — the team has made tremendous progress to date and now have a better line of sight towards the finish line. The team wanted to provide an update on the progress they have made as they finalize the auditing and testing process and get it ready for launch.

As promised in earlier updates, the team will deliver a 10-day countdown for when Metronome’s seven-day Initial Supply Auction will begin and all of the accoutrements (such as the wallet) will be ready and available.

The team feels that it owes the (incredibly patient) Metronome community to explain the reasons for moving to May. Here’s why…

Metronome Isn’t Just Another Cryptocurrency

If it were, this would be easy.

As people who have been following this launch already know, Metronome is a set of four, interconnected, and autonomous smart contracts. What often gets lost in the discussion is that those four contracts must exist on each blockchain on which Metronome resides in the future. Developing and testing that codebase on these moving parts and rails requires extreme care and diligence. There is no precedent or guide for something like this, so the team has tried to be critical (and even skeptical) of every line of code to ensure it is as clean and secure as they can possibly make it. Thus the retention of multiple independent auditors.

Additional Protections For Initial Supply Auction Participants

One example of a recent change is that the team previously anticipate that Metronome would be immediately transferable during the Initial Supply auction. However, to mitigate the possibility of off-auction price distortion, the team has decided that purchasers will have to wait to transfer until after the Initial Supply Auction has concluded. Immediate transfer will be available during the Daily Supply Lots. While it sounds like a simple engineering change, it’s more complicated than it sounds and still needs to be tested. And, of course, any change has to be tested against unexpected impacts in other parts of the system.

Further, as Metronome’s Chief Designer Jeff Garzik mentioned in an American Banker interview, the Metronome team has spared no expense to ensure maximum protection for Metronome purchasers. This includes retaining the counsel of knowledgeable and experienced legal, compliance and cyber-security professionals. All aspects of Metronome are being reviewed and tested to ensure it is the best it can be.

Conclusion

This level of trailblazing comes with its own set of variables to address and problems to solve. Navigating these risks without an almost paranoid level of scrutiny would be dangerous for Metronome as a new cryptocurrency, and unfair to all the members of the community.

The team will not hold itself to an arbitrary date at the cost of contract, code, and system integrity, and refuses to deliver anything less than the best to the wonderful and strong community. That being said, the team has moved mountains in unchartered territory, and and are excited to be at this late stage in the journey towards launch.

In the meantime, the team continues to share the Metronome message, and has received a ton of great feedback from the growing community. From popular podcasts with Epicenter and Strategic Coin, to gatherings like the DC Blockchain Summit and TokenFest, the team has been inspired by the enthusiasm and support people have expressed for what they are building.

The team continues to make Metronome better, informed by its community, and encourages everyone to participate in the conversation on Metronome’s Telegram channel.

Thank you,

The Metronome Team

UPDATE: The Initial Supply Auction and Launch date of Metronome is set for June 18, 2018.

--

--

MetronomeDAO
MetronomeDAO

Written by MetronomeDAO

A community-drive DeFi ecosystem. Our first protocol, Synth, is now live in beta - https://app.metronome.io

Responses (1)