Omni State of the Layer, End of Year 2019

Lots of news to share in this year-end update!  This update includes the following sections:

• Omni Core 0.7.0 Release
• Omniwallet User Experience Refresh
• OmniBOLT development updates
• OmniLAB Syllabus 
• Omniwallet-Mobile from OmniLAB
• Electrum Plug-in
• Specification Cleanup
• OmniJ and related work
• Decentralized Exchange Upgrade
• Omniwallet.org Regional and Functional Restrictions

Omni Core 0.7.0 Release

Thanks to the sponsorship from Tether, Omni Core maintainer dexX7 (https://github.com/dexX7) and Peter Bushnell (https://github.com/Bushstar), the creator of Feathercoin, have completed and released Omni Core 0.7.0.  Among other features this release rebases all Bitcoin Core 0.18.1 improvements into Omni Core.

Major updates are much faster indexing of transactions and the update to the decentralized exchange as described later.

Release notes for this major upgrade can be found on GitHub:

https://github.com/OmniLayer/omnicore/releases/tag/v0.7.0

Omniwallet User Experience Refresh

The talented team at Rana Dev (https://ranadev.io) has been engaged to create a new, updated version of omniwallet.org.  The Omni team asked them to focus on usability and streamlining the most used aspects of the wallet, and to make the wallet work on mobile web.  Initial prototypes are looking amazing and the team is pleased to share some examples of the new interface below:

OmniBOLT development updates

OmniBOLT is an in-progress specification, based on the fundamental theory of Lightning Network, describing how to enable Omni Layer assets to be transferred via Lightning Network channels, and how Omni Layer assets will benefit from instant payment on Lightning channels. We propose this Omni Layer-capable extended protocol to expand the horizons of basic Lightning Network, to support Omni Layer assets. 

The OmniBOLT Daemon (OBD) is a golang implementation of the specification. It runs as an independent process connecting to a full node of Omni Core (version 0.7.0), which provides the on-chain services for Omni transactions on the Bitcoin network. The current OBD implementation is tightly-bound to Omni Core. Also currently being released is an API that enables light clients to communicate with OBD network. It is an easy way for our community to develop Lightning applications. 

Development summary：

1. Applied the HD (Hierarchical Deterministic) mechanism for generating/managing OBD users’ address/keys/mnemonic words.
2. Finished HTL Contract for single node version of OBD. Tested on a user base of hundreds. 
3. New OBD test procedures and documentation are updated.
4. Update the OBD API online document (https://api.omnilab.online/), completed the HTLC related API descriptions.
5. Update the READ.ME file of the OBD repository(https://github.com/LightningOnOmnilayer/LightningOnOmni). This document is a step by step instruction for a brand-new user of OBD.
6. Released one OBD demonstration video.
7. The OBD query interfaces have been developed and improved, and an interface for querying user-related information has been added.

The following tasks are in our working pipeline :

1. Work in parallel with Omni Core team, who are developing new interfaces supporting SegWit in Omni transactions. We currently use some tricks to circumvent this part of work, in order to prove the concept. It works but is not secure enough. After the new features of Omni Core are ready, we will change our code base to the new Omni Core.
2. Larger scale tests of HTLC.
3. Try to connect OBD to the LND network. At least we hope we can connect to the existing onion network.
4. Or develop own network module, to enable OBD nodes to talk to each other.
5. Complete path discovery/finding algorithms and transfers among multiple OBD nodes and any number of clients.

Online API documents for our community: https://api.omnilab.online/

For details of Update: https://omnilab.online/news/

Please visit https://omnilab.online/omnibolt/ for more information.

OmniLAB Syllabus 

There is one aim for this syllabus: to instruct relatively unsophisticated programmers / audiences to understand the background, basic theory, and application of blockchain technology, grasp fundamental concepts, technical processes, specifications and their applicable scenarios. After passing this examination, audiences shall become a specialist with ability to develop blockchain products and applications. We are looking for the cooperative institutions globally to spread our certification standards and the technical culture of Omni. 

Strategic Partners till this moment: Odaily  Blockbeats  Ccvalue  BTCU 

Please find more details here: https://github.com/LightningOnOmnilayer/Omni-Academy 

Email: contact@omnilab.online for cooperation. 

Omniwallet-Mobile from OmniLAB

We have also begun working on mobile versions of OmniWallet, testing binaries are available in our repo. OmniWallet-mobile is a native wallet for Omni Layer assets, released on both Android and iOS. It currently supports Bitcoin and all Omni Layer tokens, providing Bitcoin & Omni Layer users with an ease-of-use and unrivaled blend of security. The wallet is completely open source, which includes a set of standard backend services, written in java/golang, and a mobile side app written in Dart (Flutter framework by Google).

OmniWallet Mobile: https://github.com/LightningOnOmnilayer/OmniWalletMobile_V2

Electrum Plug-in

A team of developers has created an electrum wallet plugin which supports Omni Layer assets.  This will allow any electrum-based wallets to begin using Omni Layer assets such as USD₮ directly.  These haven’t yet been put into the official electrum client but are available for testing here: https://github.com/engenegr/electrum/tree/3.3.4-omniplugin 

Specification Cleanup and Documentation Efforts

We have recently started a project to update the Omni Protocol Specification and related technical documentation. This work has already begun and will ultimately include:

• Converting the document from basic Github markdown to the more full-featured AsciiDoc markdown format.
• Removing obsolete and historic sections of the Specification to focus on the details of the Protocol itself.
• Updating the specification to include details on Class C transactions and other new features.

We also have created the Omni Layer Documentation Project repository. The README for this repository includes links to important existing documents. (If something is missing please let us know by submitting a Pull Request.) This repository also has a directory containing our first steps towards implementing Omni Layer Enhancement Proposals (OLEs) that will be the Omni equivalent of Bitcoin Improvement Proposals (BIPs).

OmniJ and related work

The OmniJ lead developer, Sean Gilligan (https://github.com/msgilligan), has been hard at work on improvements in bitcoinj and OpenJDK-based wallet framework technology that will allow us to build a bitcoinj-based Omni Layer wallet that can ultimately be deployed on mobile, desktop, or server.  Since bitcoinj provides lightweight serverless blockchain access (SPV mode) this architecture provides nice decentralization at the Bitcoin layer and only relies on Omni Core API servers for Omni token balances. The initial focus is on a desktop wallet, which should be appearing in alpha-test versions. OmniJ will also be updated to finally support Class C transactions.

Decentralized Exchange Upgrade

As some know – but few use – the Omni Layer provides a fully-decentralized exchange mechanism on the Bitcoin blockchain: one feature allows you to swap between BTC and OMNI tokens, and another allows for the exchange between any Omni Layer tokens (e.g. USD₮ <-> MaidSafe).  The team calls these the DEx and the MetaDEx. With the 0.7.0 update Omni Core and the forthcoming Omniwallet interface update, the team would finally like to open up the primary decentralized exchange to work between BTC and any Omni Layer token directly on the Bitcoin blockchain. The team is working on the functional interfaces within Omniwallet and the proper RPC calls within Omni Core, at which point the Feature Activation transaction necessary to make the feature live will be broadcast to the blockchain.

Omniwallet.org Regional and Functional Restrictions

Finally, the team has decided that due to laws and regulations prohibiting the export of services and technologies to certain countries and jurisdictions, Omniwallet.org is now blocking all connections from the following countries:

• Cuba
• Iran
• North Korea
• Sudan
• Syria

Also, in the forthcoming version of Omniwallet.org, users in the United States will no longer be able to use Omniwallet.org to interact with the on-chain Distributed Exchanges available on the Omni Layer protocol on the Bitcoin blockchain. Other wallet functions will be unaffected, and read-only information about offers, trades and prices from the DEx will remain available on Omniwallet and Omniexplorer. While this was a difficult decision, it protects the ability of the Omni developers to continue innovating cutting edge decentralized technologies for the benefit of all users. 

Looking forward to 2020!

I’d like to start this update with the reminder that the Omni Layer is an asset issuance and smart contract protocol that runs on top of the Bitcoin network.  Some people have asked if Omni is a fork of Bitcoin, or its own network – and I wanted to reiterate that the Omni Layer is a meta-layer on top of Bitcoin. Omni uses the available space in the Bitcoin OP_RETURN mechanism to create an Omni Protocol ledger for tokens and smart contracts as a meta-layer on the Bitcoin ledger. In this way, Omni leverages the on-chain hashing power and security of Bitcoin’s Proof of Work system.

Tether itself is a tenant on top of the Bitcoin network.  When Tether was architected, I had in mind not only a token that would hold parity with a dollar, but something that would demonstrate the extra-special capabilities of a decentralized ledger, and what applications on such a technology could achieve.

Using the Omni Layer, tethers are issued as a meta-token on top of the Bitcoin network, using the messages that Bitcoin transactions commit to this decentralized ledger.  Instead of just moving a bitcoin, you were also saying “I’m moving a dollar from here to there.” In doing so, users would have a bearer-asset, just like BTC, with the same security and assurances provided to bitcoins on the Bitcoin network.

While tens of billions of dollars of tethers are traded daily on multiple exchanges off-chain, there are hundreds of millions worth of transactions daily on the Omni Layer, on-chain, directly on Bitcoin, moving those funds between wallets and exchanges.  This demonstrates an amazing capability that I believe is being overlooked. The Bitcoin network is exceptional for securely passing value, no matter which token, BTC, USD₮, or otherwise.

The community has focused so much upon the bitcoins themselves and not on the fact that what we have is an immortal state machine that no one can turn off and no one can censor.  Bitcoin’s built-in messages and capabilities can be extended with technologies like Omni that rely upon the immutability of Bitcoin ledger records kept within.  

While Tether has begun issuing USD₮ on other blockchains such as the ERC-20 variant on Ethereum, I wanted to remind everyone that no network has the massive hash-power and security that the Bitcoin network provides, especially with the coming switch to PoS on the Ethereum network.  If you care about immutability and security, or are a Bitcoin maximalist, we’ve built the Omni Layer for you!

 

Tether Sponsorship

We are excited to announce that Tether has provided sponsorship for additional developers to bring Omni Core up to par with Bitcoin Core 0.18 and to create further innovations on the protocol.  The new release is currently being tested and should be available soon. The new release brings tremendous performance improvements, as well as cost savings due to much better fee estimation for transactions.

Peter Bushnell (https://github.com/Bushstar), the creator of Feathercoin is working with Omni Core maintainer dexX7 (https://github.com/dexX7) and Adam (https://github.com/achamely) to get this release finalized.  

Additional functionality will be added to the protocol soon, to support native Segregated Witness transactions and features like send-to-many, enhancements that can lower the cost of individual transactions and keep cost low and integration needs easier for exchanges and integrators.  We are also speaking with the Lightning and RGB community developer teams to determine how we can best integrate with them for off-chain asset movement.

Any individuals, exchanges or integrators who would like to submit recommendations and feature requests can do so by submitting a new issue on the Github Spec (https://github.com/OmniLayer/spec/issues), emailing support@omni.foundation or join the telegram chat (https://t.me/OmniLayer).  We’d like to compile a list of all integrators so that we can timely publish news and keep in communication with updates and recommendations.

 

Omni Layer Protocol Specification Updates

We are in the process of updating the Omni Layer protocol specification. This should help integrators better understand the data format used in Omni-encoded transactions. In addition, we are looking at ways to improve or optimize the protocol to allow for additional functionality.

We are looking into new ways that developers can encode instructions in OP_RETURN messages, to further enhance the capabilities of the protocol.  Beyond decentralized exchange functionality, we are considering a number of options that would allow for different types of conditional sends of assets, in a more generic smart-contract language.  We solicit any ideas and recommendations on what functionality is possible.

 

Upcoming Updates

In the coming weeks, we have updates to share on a number of exciting developments:

 

Omniwallet-Mobile from LunarX (https://lunarx.co)

Omniwallet.org redesign

Electrum Wallet Plug-in

OmniJ and related work

Omni Layer on Feathercoin

Decentralized Exchange Updates

 

Invitation to developers

Anyone who has looked into the Omni Layer and realized what it actually can provide on the Bitcoin network gets really excited about the future possibilities.  We invite curious developers and innovators to examine the capabilities of meta-layer transactions on top of the Bitcoin blockchain and to contribute ideas to accelerate the development of new features on this time-tested platform.

 

This has been a busy few months, with the team’s efforts dedicated to enhancements to the platform and assisting in Omni integrations with partners and other interesting projects.

The most recent release of Omni Wallet Desktop for Windows capped off a strong development cycle, adding Send-to-Owners capability and a QT user interface (for 64-bit Windows and Linux. Mac OS X build forthcoming).

Our forward looking roadmap, as discussed and agreed upon with the team during our most recent all-hands, is as follows:

1. Continue top priority of stability/reliability above all else.
2. The move to Class C (80-Byte OP_RETURN) for most transactions.
3. Bitcoin Core 0.10 headers-first blockchain compatibility
4. Technical debt (multi-packet transactions, useful RPC commands not yet implemented, etc.)
5. Decentralized Exchange phase II RPC (trade between Omni assets and MSC)
6. Decentralized Exchange phase II UI
7. Omniwallet.org redesign launch
8. Address anchoring for metadata
9. Futures market DEx extension
10. Spec and Documentation improvements

Leveraging Sean’s automated testing suites, the 0.0.9.1 release was the most thoroughly tested yet. The team believes strongly that stability and reliability should remain our highest priority.

Zathras has completed a good portion of the Class C transaction work, and is currently refactoring the Class B code for the few cases where Class B transactions will be required (as they won’t fit into 80 bytes).

DexX has made substantial progress on a Bitcoin Core 0.10-based branch of Omni Core.

Technical debt includes the ability for Omni Core to broadcast multi-packet transactions, output raw transactions, include RPC commands for supported and active features such as dynamic asset issuance and the decentralized exchange, high-decimal precision improvements, etc.

Michael’s work on phase II of the decentralized exchange is mostly complete, and Marv and Sean are preparing the test plans as the matching engine logic is finalized.

Thanks to Adam, Tomás and Warren, Omniwallet.org will be getting its new skin (currently at staging.omniwallet.org), dramatically improving user experience.

Working with Paul Snow, the Omni Layer will gain an “address anchoring” method, used by Factom, for ensuring the validity of eligible “publishers” of data on the blockchain.

Patrick and Dave have been working on an innovative futures market extension to the decentralized exchange, allowing advanced market features for Omni assets.

Through all of this, the team is assisting with around two integrations per week, and meeting with 8-12 additional projects, each at various stages, all coordinated by Judith.

We invite the community to provide feedback, to contribute to the development of new features, and to keep innovating on the Omni Layer. The team continues to move the platform forward, with the assistance of some amazing integration partners helping to create the future of finance.

It keeps getting better, and I’m still humbled by the capacity and talent of this team.  Keep up the great work!

Craig

After months of development and testing, the Omni development team is proud to announce the first official release of Omni Wallet Desktop for Windows, based off of Omni Core build 0.0.9.1 (which is in turn based off of Bitcoin Core 0.9.3).

https://github.com/mastercoin-MSC/mastercore/releases

As a first release, this is for more technical users (you need to edit a conf file) who wish to manage their Omni assets locally and provide feedback to the developers. Please report bugs using the issue tracker at GitHub: https://github.com/mastercoin-MSC/mastercore/issues

The software also contains several utility panes, allowing the user to look up the assets on an address, or get detailed information about an asset on the Omni Layer.

This release comes after substantial progress on new protocol features, such as Send-to-Owners (proportional distribution) and the new Decentralized Exchange (so that users can exchange their Omni assets against one another without an intermediary).  Send-to-Owners was released as part of 0.0.9, and DEx Phase II will be released as part of Omni Core 0.0.10.

The Mac OS X build of Omni Wallet Desktop will be available soon.

More and more projects are deploying their projects and assets on the Bitcoin Omni Layer, and this release of Omni Wallet Desktop for Windows opens the platform to users who wish to transact locally with their MSC, MaidSafeCoin, API Networks coin, CryptoNext Coin, La’Zooz, Synereo, HOPE Gold Coin, Tethers, and more.

Keep watching this space, as more and more integrations, assets and innovations are coming, and they are coming at an increasingly rapid pace. I would like to thank the Omni development team for their outstanding progress and efforts – it is a pleasure working with such a talented and driven group of innovators.

Craig Sellars
Technologist, Omni

Mastercoin Upgrades Premier Bitcoin Asset Layer, Relaunches as Omni
Original Bitcoin 2.0 Protocol Powers MaidSafe, Tether, Factom, La’Zooz and
35 More Cryptocurrency Tokens, Passes Counterparty in Market Cap of Assets

Core Developers Ready New Version of Omni Layer Asset Creation Platform, Omni Wallet Multi-Cryptocurrency Online Wallet, and Omni Exchange Decentralized Exchange, All to Launch in Q1 2015

(North American Bitcoin Conference, Miami – January 18, 2015) – Mastercoin (www.mastercoin.org), which created the Bitcoin 2.0 movement through the creation of the first overlay to the Bitcoin blockchain following the industry’s first crowdsale in August, 2013, announced today that it has substantially completed the development of the Omni Core engine behind the Omni Layer (formerly Master Protocol) and will rebrand all aspects of the Mastercoin ecosystem as Omni.

“This relaunch reflects both a change in the cryptocurrency asset landscape, with MaidSafe becoming a top 10 cryptocurrency overall, and the desire of the decentralized developer community that has grown up around these assets and protocols to become a unifying presence in the ongoing development of the blockchain for business,” said Craig Sellars, a technologist of the Omni Layer.

The Omni Layer is a protocol that sits on top of the Bitcoin blockchain, allowing the creation of assets that combine the unmatched network security and adoption rate of Bitcoin with enabling capabilities built into the Omni Layer which allow new assets like MaidSafe, Factom and Tether to create specific new uses cases like decentralized web services, data and records documentation, and a digitized traditional currency, respectively.

The Omni Layer is a decentralized community that was funded by the Mastercoin Foundation, which gathered support from the community totaling 4,700 bitcoins in August, 2013, and used these funds (including during times when bitcoin was valued at 4-5x today’s pricing) to fund hackathons and developer bounties. Two of the Foundation’s key projects, the Omni Wallet (the original use of the Omni brand by the Mastercoin community) and the decentralized exchange, will be completed by a new Omni Foundation, whose board members will be elected by the membership of the new Foundation.

Today the market values of token assets issued on the Omni Layer (including MaidSafe) exceed that of all Counterparty and other Bitcoin blockchain-issued assets combined.

About Omni
Omni (www.omnilayer.org) is the latest iteration of the Master Protocol, created in August, 2013, as the first bitcoin asset layer. As the original Bitcoin 2.0 entity, Omni has 18 months of development and its ecosystem includes a multi-currency wallet (Omni Wallet), which connects to a decentralized exchange (Omni Exchange). Omni is a global community of developers and entrepreneurs building the premium asset layer of Bitcoin as open-source software.

To be the leader in Bitcoin-based financial platforms, you need adoption, and to get adoption, you need utility, features and ease of use. While we have a number of innovative projects being launched using the Master Protocol as it has been developed over the past year, we still need enhanced features, additional flexibility and robust security to the users.

A proposal for distributing application-level metadata in a global format has been proposed,
which if implemented would reduce the amount of metadata storage required for Smart Properties on the Bitcoin blockchain (and slimmer is better for the whole ecosystem). Please read this and provide comments.

Asset issuers have been asking for more control over the assets they create. Not only the ability to create assets on demand, but also the means to manage those assets, and transfer ownership of those assets. The learning curve on decentralized financial assets is pretty steep, we’re finding that people are now starting to “get it” – and the foundations that have been built are exactly what issuers need to build upon and make the next killer app.

The MetaDEx is getting closer to release, taking oodles of input from experts and making it beautifully simple to execute.

The Over-under

Prepping a new software release brings the contributors together to determine the best fit for new changes, discussion surrounding caveats and edge cases, and what the changes will impact going forward.

Next week we will release the next tagged release of Master Core for integrators, version 0.0.7.

This will be the last tagged release before we build and distribute the next beta of Master Core that will include the front-end user interface for the downloadable wallet (and, of course, multiple platform support). This tagged release is to provide integrators with the most up-to-date protocol enhancements and to make sure they will be ready for the users using the forthcoming beta.

The deep

In preparation for next week’s new tagged release of Master Core, this week the team has been busy merging in the remaining code and running unit tests and black box testing against the critical functions.

So far, we’ve tested and approved p2sh multi-sig and manual issuances after thorough testing on Bitcoin testnet. Re-org protection was merged yesterday and today (and throughout the weekend), we’ll be making sure that the daemon remains stable and accurate (as it has been up to now). The re-org protection allows Master Core to recover better from a blockchain re-org, whereas the prior builds provided a warning to the user, but did not automatically reparse.

A side-refactoring of the file structure of the code was also made yesterday to allow for smoother merges of new features in the future.

The skinny

Omniwallet got some major updates this week, and over the weekend will be getting even more, related to Master Core integration, the new database backend, and front-end UI updates. Part of getting the new builds of Master Core out have been to assist in getting the old underpinnings of Omniwallet removed and replaced with the reference client. The same is happening for masterchest.info, which by next week will also be running against Master Core. All of this in preparation for new asset types, faster and more responsive services and more detailed data to be presented to the end-user.

Next week integrators get a lot. Shortly thereafter, the UI will be ready, and everyone will be able to see it.

See areas of improvement? Have any questions? The more masterminds the better! Join the project. Ask me anything!

Craig Sellars

CTO, MSC Foundation

craig (at) mastercoin.org

It’s been another frenetic and massively productive week in the Mastermind world, with new features flying in to the codebase faster than we’ve seen before.

This week we’ve pulled in more RPC updates, interface updates, manual (unlocked) issuance of assets (grant, revoke), p2sh multi-sig, and additional re-org protection – and that’s just in Master Core. No less than four third-party integrators (exchanges and wallets) have begun tying Master Core into their backend systems this week, and next week is going to be a frenzy of testing, building, testing, packaging and testing.

Two of the groups who are white-labeling Omniwallet have also provided some exceptional feedback and contributions in terms of scalability, security and interface, and the community that is growing around the Master Protocol is finally beginning to see the capabilities that are about to be unleashed.

On the testing front, we’ve updated our spock engine to allow for more automated tests on commit and builds, working through “cumulative hashes” that allow all clients to know that the balances they are using are the same as all other clients.

For Omniwallet, we’re soliciting feedback from users in our “What’s in Our Wallet” survey (which, if you haven’t yet, submit your thoughts – it will guide the future direction of Omni), populated the OmniEngine backend database, added logic processing from DEx payments, and begin integrating the new front-end API.

QA and testing were hot on the plate this week, as we welcome a new team member who will be focused on test plans and quality assurance.

Exciting new ideas are being pumped into the spec on an almost daily basis: smart property administration, futures contracts, ways to decrease transaction fees, and minimizing the blockchain storage requirements of Master Protocol transactions.

The Master Core UI is getting closer to release, as well; below can be seen the Balances tab:

All in all, the team has been working around the clock, continuing to knock the socks off anyone in the general vicinity. As an old colleague once told me, when referring to working non-stop: “you can sleep when you’re dead.”  Our next release will be coming soon, and with it the results of months of non-stop effort will be shared with the world.  

As always, we solicit and invite contributors to come and comment, critique or contribute. The more masterminds the better. Ask me anything, and keep your eyes peeled for what’s coming.

Craig Sellars

CTO, Mastercoin Foundation

craig (at) mastercoin.org

Hello, Masterminds!

As each week comes to a close, I like to see all the various pieces of the Mastercoin project pointed in the same direction, and this week was no disappointment. The team released a new Omniwallet milestone release and continues forward towards our next Master Core release.

We’re extremely fortunate to have an internal integration team for Master Core: Omniwallet is a great use case for what web wallets and exchanges need from Master Core in terms of functionality and visibility. The collaboration between the teams has helped refine our priorities and schedule, and with additional feedback from 3rd-party integrators, our targets for each Master Core milestone becomes more clear.

This week our focus has been on several fronts: the new database backend for Omniwallet, OmniEngine, the RPC layer of Master Core, the persistence engine behind Master Core, the MetaDEx internals, the Master Core UI, and a new asset issuance type.

For Omni’s database, we’ve been parsing and importing blockchain data and are creating the queries to pull the data. Having the blockchain data accessible in this fashion will enable some impressive visualization and information tools (such as an enhanced block explorer) as well increasing responsiveness.

The RPC layer of Master Core continues to get additions, guided by Omni, exchanges and requests from experienced traders. The MetaDEx RPC template is a work in progress.

On persistence, we’ve made progress exposing some of the state values from internal parsing operations so that users can get more atomic data. We’ve also worked to more elegantly handle blockchain reorgs and orphans here.

The Master Core UI continues to progress, with work on the Balances screen and updated iconography. Our target for the next release will include the ability to see token balances and to send transactions for any Master Protocol token.

Of note, we have updated the Master Protocol spec to include a new asset issuance type which can have tokens perpetually created and destroyed by the issuer as necessary. Asset-backed issuers will find this extremely useful to maintain a token count on par with the assets they are using to back the tokens. Now that this pull request has been merged we can start development of this extremely useful feature.

Next week, we’ll be coming up with the first milestone-based bounties and defining our target features for the next Master Core beta release.

Questions? Ask me anything! Want to get involved? Get in touch!

The more masterminds the better!

Craig Sellars

CTO, Mastercoin Foundation

craig (at) mastercoin.org