Development is well underway of the DEx and some very exciting advancements lead this week’s development update. Maran announced this week that his team has created the first database layer for Mastercoind. It’s a LevelDB layer that now has two uses.
DEx Status
Spec Update
Masterchest
Omniwallet
MyMastercoins Wallet
Development is well underway of the DEx and some very exciting advancements lead this week’s development update. Maran announced this week that his team has created the first database layer for Mastercoind. It’s a LevelDB layer that now has two uses.
We are now saving the raw Bitcoin transactions that have references to Exodus which get from our full validating node and save those in raw format by encoding them to binary streams. This feature was added so that flags may be given to mastercoind in order to playback this raw data and reparse all transactions without needing to resync the whole blockchain.
Additionally a second database was created this week in order to use as a fast balance lookup. The way the initial version will work is that there is lightweight balance ledger that holds all addresses as keys and their matching balances as values in the form of a hashmap: {1: 39, 2: 393}. In the future more currency IDs can be easily added.
Further, support to decode Simple Sends, next to the support we already had for Fundraiser decoding balance is correctly calculated for both Fundraiser and Simple Send transactions.An alpha release is targeted around the 21st of February, with focus purely on a Simple Send read-only balance.
Spec Update
During a very productive conference call between J.R., Craig, Marv, and Peter, several spec changes (affecting future features) are being made. Marv made a lot of updates to the spec – formatting, transaction descriptions, versioning. These will be broken into separate posts.
Masterchest
Zathras has been continuing testing and bug hunting in preparation for the wallet’s release. The consensus system received some stability fixes while the transactions API has been added to Masterchest.info. Zathras has also authored Spec Appendix E – Understanding the cost of Master Protocol messages.
The draft of the Masterchest User Documentation is now available at (https://masterchest.info/files/Masterchest_Wallet_User_Doco_Initial_Draft.pdf)
Omniwallet
The Omniwallet team (Curtis, Faiz, Patrick, and Yuval) has made significant advancements this week. Stage 1 features are now complete and can be seen at (https://github.com/mastercoin-MSC/omniwallet/tree/master/design#stage-1-features)
The team is pulling together a VM for testing at several exchanges.
The Stage 2 deadline is set for the 15th of February. Details of these stage 2 features cna be found at: (https://github.com/mastercoin-MSC/omniwallet/tree/master/design#stage-2-features)
A new demo server is now running at https://omniwallet.labs.engine.co.
POST endpoints are also now being documented: https://github.com/curtislacy/omniwallet/blob/Document-API/README.md#api
Yuval is working on a robust UI and incoming updates are soon to follow.
Technical links regarding the Omniwallet:
VM script: https://github.com/curtislacy/msc-exchange-scripts/pull/2
VM script: https://github.com/curtislacy/msc-exchange-scripts/pull/1
Offers endpoint: https://github.com/curtislacy/mastercoin-tools/pull/4
API refactor: https://github.com/mastercoin-MSC/omniwallet/pull/29
MyMastercoins Wallet
Bitoy has been working on mymastercoins wallet v 2.
Using bitcoind.exe -daemon the wallet now allows users to import private keys.
For more information on the MyMastercoins Wallet, please visit (http://mymastercoins.com/MyMSCWallet.aspx).
Omni 