Mastercoin on TestNet

Testing is a hugely interesting topic for some, mainly developers, looking to develop some intuition about how a particular piece of software works to integrate into their use case. It is very helpful, therefore, that Bitcoin provides access to a ‘Testnet’ for the transmission and spending of transactions in a sandbox where Bitcoin Testcoins have no real value.

As this is hugely beneficial for normal Bitcoin developers, we at Mastercoin also realized the huge benefit for the developer community if we were able to send TestNet transactions in Mastercoin, which would reduce the cost to develop on our infrastructure.

Without further ado:

A guide to running TestNet for Mastercoin (A primer):

  • Download and build the latest hash/tag of MasterCore from Github here.
  • Run MasterCore in Testnet from the command-line, `./bitcoind -txindex -testnet`and allow it to sync to the furthest block (at time of writing, this is 262068). Command line output might result [2]
  • Check if you have any Bitcoin Testnet addresses with ‘./bitcoind listaccounts’and then ‘./bitcoind getaccountaddress’. You can also generate a TestNetaddress using vanitygen ( Testnet addresses start with an ‘m’, usually. Take note of this address.
  •  Request some Testnet coins from the TestNet Faucet ( – Please do not abuse!)
  •  Add a file to ~/.bitcoin/testnet3/ called ‘mastercoin_balances.txt’.In this file enter your address, followed by your desired MSC amount, followed by a 0 [0]

You can send some MSC now using the following command (full list of commands are obtained using ‘./bitcoind help’):

`./bitcoind send_MP (your address) (their address) (amount-in-floating-point)`[1]

And that’s the quickstart guide for TestNet. There are numerous other commands suffixed with ‘_MP’ in the output of `bitcoind help`, feel free to test those out. Report bugs and difficulties to the repository directly if you locate any, and questions can be asked of the devs through either Github Issues, the mailing list, or directly through email.

[0] For example, the file contents would look like:

[1] Example of successful send on TestNet


[2] Example of debug output


Mastercoin on TestNet

Master Core beta on August 1st

You may have noticed that the countdown timer on has been changed. Not the deadline, but what is going to happen when the counter reaches zero.

August 1st is Mastercoin’s first birthday. And just as when something begins to grow up and it begins to get its legs, so does this metaphor. We have an opportunity to provide a better platform, upon which we can build better features. The developers have convinced me that if the focus were on a single implementation, the half of the time that is spent working out consensus would be regained. We realized how quickly developers could adapt and create new features upon this new platform. We realized we could build a better MetaDEx on this new platform.

So we’ve decided to do that: instead of the MetaDEx being released on the legacy platform, on that day, we will present Master Core’s first official beta release, with testnet support. Happy Birthday, Masterminds!

tl;dr: coding it twice is silly, and doing it right takes a little bit more time. Master Core is the right way to get it done. (Master Core beta, followed by the MetaDEx is going to impress you.)

Current Master Core beta deliverable: August 1st.
Current MetaDEx deliverable: soon thereafter.

Master Core beta on August 1st

Mastercoin is proud to support the Bitcoin network using

We are very happy to announce that we have purchased our very own server on, and are running a full Bitcoin node at AKA (you can verify this by checking it on is an initiative to combat the problem of a declining number of Bitcoin nodes. It is a one-click Cloud service for setting up Bitcoin nodes, that anyone can use (by donating bitcoins) to “adopt” a full Bitcoin node and thus support the network’s health. We are proud to support and promote this initiative and encourage other Bitcoin organizations, companies and individuals to do the same.

The cost of adopting a fullnode is $10 a month, payable in Bitcoin of course.

We will soon be adding another full Bitcoin node to the network in the form of a Master Core node powering Omniwallet. However, regardless of any other servers we are running, we wanted to donate this little bit of extra compute, bandwidth, and P.R to the Fullnode effort in order to raise awareness.

So go ahead – adopt your own Fullnode! It really takes just a couple of minutes and only $10 per month.

P.S – it’s quite possible that the real, complete solution to the ‘Full Node Problem’ in Bitcoin requires some heavy thinking, and changing the monetization model, to properly incentives full nodes. Until that happens, we will be running a

Mastercoin is proud to support the Bitcoin network using

All your attack surface are not belong to Omni.

Omniwallet is not built like most other web applications. We built Omni from the ground up with security in mind. First of all, as a rule omni never sends your password to the server. Your password is only used locally to unlock your private key(s). Speaking of keys, they are also not stored un-encrypted on the server.

Continue reading here as we  go through our login and send transaction workflows with a technical eye.


Mastercoin Security.

All your attack surface are not belong to Omni.

Core project hits its first development milestone!

Hey guys!

The Core development team is very excited to be able to share with you our latest update on the Master Core project.

Our first milestone requested initial functional alpha code for the following:

  • Single Currency Support – support for currency ID 1; Mastercoin
  • Persistence – the ability to maintain the state between closing down and relaunching Master Core
  • Consensus – 100% matching consensus with existing implementations, namely OmniWallet and MasterChest
  • send_MP RPC call – the ability to send a Master Protocol currency
  • getbalance_MP RPC call – the ability to check an address for the balance of a Master Protocol currency/property
  • gettransaction_MP RPC call – the ability to lookup a Master Protocol transaction
  • listtransactions_MP RPC call – the ability to list the last n Master Protocol transactions for an address (or * for wallet)

It’s been quite a challenge, but we’re pleased to say we’ve been able to deliver on all of these milestones. The next steps will involve improving on the initial alpha code for the first milestone, along with moving towards our second milestone which, at a high level, is multi-currency support and support for all existing smart property transactions.

If you’d like to get a feel for how these RPC calls are looking so far, I’ve prepared a few examples for your perusal here:

I also wanted to take a quick moment to thank our Core developers, the work ethic is just incredible and I feel extremely privileged to be part of such a hard working and knowledgeable team.

Please note: it is important to us to make sure our readers are aware this is a development milestone and not a release. We’re very proud to have achieved the first alpha code for these functions but it is initial alpha code only – there are still lots of quirks to be worked out, testing to be done, and bugs to be resolved. We would like to caution against any usage outside of testing and development.

Zathras, on behalf of Core Dev

Core project hits its first development milestone!

PGP, encryption and Mastercoin

We at the Mastercoin Foundation take pride in our privacy and security,
and would like to make the following announcement regarding use of PGP
within the organization. Looking forward, our team will use PGP to sign
and verify commits in all our upstream repositories, and these dev blog
posts will be verified with a signature every time. This ensures consistency
and security, to know the folks behind the product, and to understand
the implications of downloading and executing our code.

Web of Trust
Our web of trust is based on a secure network of face-to-face confirmations
and keysignings. Currently, our web of trust is as follows:

Trusted Leadership:
– – – – – Ron Gross, Executive Director (28277264)
– – – – – J.R Chief Architect (8D5F5A9A)
– – – – – Craig Sellars, CTO (1F00C8D6)

Trusted Developers:
– – – – – Zathras, Core Developer (BE91B32B)
– – – – – Michael, Core Developer (612F1CEF)
– – – – – Shannon Code, Head of Security (65C309B9)
– – – – – Marv Schneider, Product Manager (9BF81EFD)
– – – – – Nevtep, Developer (6D463F34)
– – – – – Bart Wyatt, Developer (A12BB6C8)
– – – – – Adam Chamely, Omniwallet Lead (83A266F3)
– – – – – Sean Gilligan, Developer (6E4EE875)
– – – – – Faiz Khan, Developer (8C399E1F)

Commit Rights
We have a highly trusted network of developers who merge code, accompanied
by an untrusted network of external developers who submit pull requests to
be reviewed by the trusted parties. This process is managed by “merge leaders”
who lead the feature direction and development discussion. The developers
take lead from these leaders and follow suit committing code that suits
the current milestones.

This state will likely never change as we transition forward into a model
of continuous integration (see
The Omniwallet and Master Core teams look forward, as always, to lead
these security efforts. Our merge and scrum leaders are Adam, Marv,
Zathras, Sean and Michael.

Shouts to Adam, DexX, Craig, Ron and anonymous others for assisting in the
editing of this post.

“Pleasure. Life is pleasure expressed.”
        – Ron Gross

Full, PGP signed article linked here

PGP, encryption and Mastercoin

Master Core

Hi everyone,

My name is Michael & a few months ago I joined the Master Protocol team as a core developer. I’d like to take a moment to introduce you to a project we’re very passionate about.

You may’ve heard that an expert Mastercoin team has been working on a strategic project for a good number of weeks now.
You may’ve heard that we are developing a very welcome and important product.

And that would be true.

It is the fastest and the most portable Master Protocol implementation.
It runs within the same proven Bitcoin Core (currently 0.9.1) we all know and love.
It requires no external dependancies, no databases, no script tools; it is native to the Bitcoin network just like 100,000 other nodes.
It’s C++, compiles its protocol & UI extensions into the same daemon and QT binaries you’re all used to.
In its wallet form it will be seamlessly available on 3 platforms: Windows, Linux & Mac OS.
In its node form it exposes Master Protocol extensions via JSON-RPC which makes integration a breeze.
Most importantly, it will be the flagship reference client of the Foundation.

I’d like to present to you : Master Core.


We’ll post further updates to this blog as we get closer to release.


Master Core