Introduction

Since our last development update, we’ve made some exciting progress on the development of Mercury Protocol.

Key milestones

Updated GMT token contracts to allow only registered users to participate Integration of premium exposure into Android Dust Completed the premium distribution smart contract Continued development of various Ethereum services Built a unit test apparatus for Java Mercury Protocol server Configured Ethereum peers to run as a service

Video Summary

To receive video updates in the future, you can subscribe to our channel.

1. Update GMT token contracts to allow only registered users to participate

For users to participate in the upcoming token launch for Global Messaging Token (GMT), they will need to register on our website [ADD LINK]. The token smart contracts have been updated to restrict users who aren’t registered from participating in the sale.

In addition to updating the contracts, we also ran a couple simulations of a token sale using the updated contracts on the Rinkeby testnet. All tests were completed successfully.

2. Integration of “Premium Exposure” into Android Dust

As we previously mentioned in the whitepaper and blog posts, Dust will be the first application to undergo Mercury Protocol integrations. Our first milestone is to tokenize the application with GMT (Global Messaging Tokens). Users will initially have two ways to use GMT, both aimed at helping grow their networks.

Premium Exposure — users can use GMT to be listed on the front page of the Discover (new content) section for 24-hours. Premium Distribution — users can use GMT to send out a “Blast” to a number of users that don’t follow them.

The “Premium Exposure” feature is live and kicking in our Android clients! This means both the protocol’s smart contracts for the “Premium Exposure” feature and the integration of the protocol into the Android client is complete.

We’re pretty excited by our first use case, and are even more excited to have you try it out after the token launch when we release the update.

3. Completed the premium distribution smart contract

We’ve also completed the implementation of the “Premium Distribution” smart contracts. The integration of this feature into Dust will happen in the coming weeks.

4. Continued development of various Ethereum services

Along with the smart contracts, we have been actively developing various services handle the transaction processing on Ethereum. This includes:

API endpoints for processing, signing and verifying transactions. These endpoints are completed and actively being used in our test environment.

Business logic for the server to gather contract metadata (contract addresses and function names) to minimize the amount of client version updates needed as contracts are tweaked.

Transaction History being synced between Ethereum network and our Mongo Database. History now includes transaction cost, gas price, gas used, and gas limit, to match https://rinkeby.etherscan.io histories.

5. Built a unit test apparatus for Java Mercury Protocol server

The MP-Server is wired up using Spring and we have built a suite of unit tests using Spring-Test and JUnit. All business logic are run through these tests. Some of our tests include:

Create Account

Get GMT Balance

Get Ether Balance

Send GMT

Estimate Gas on Send GMT

Estimate Tx Cost on Send GMT

Pay to Be Featured

Is Featured

Get Price to be Featured

Expire Featured User

6. Configure Ethereum peers to run as a service

We configured and deployed the Java Mercury Protocol server onto our AWS development server running in Tomcat7. We also deployed an Ethereum Peer on AWS which now runs as a service and is connected to the Rinkeby test network.

Join Our Community

Mercury Protocol is an open source project where anyone can get involved. If you’re a developer and interested in getting involved with development, come say Hello on our Slack in our #dev channel.

We plan to open source the protocol in Q1 2018, and we’ll be actively building out our development team and looking for core open source contributors. We’d love to have you on board! 🙂

Connect

Learn more about the Mercury Protocol

Read the Mercury Protocol whitepaper

Join the slack community

Reddit

Twitter