All in the pocket of the dev. Including what they sent to themselves to get MSC share.
Oh, + 10% of all MSC created on top of that as "devMSC" to fund development and bounties I guess.
(like the previous 100% wasn't enough...)
And there is a rumour: a part of every single MSC transaction is going to the exodus address (to the dev pocket, again). I haven't verified this 3rd statement.
The first two are way enough to keep me at good distance.

And what do I read: copyright O.o?
Are you serious guys?
Like someone is gonna respect it...

No idea.
Last time I checked it was pure vaporware, words.
XCP seem to be the first one with something other than words.

If I had to take a guess, I would say more like close to at least 20 BTC invested 

A mastercoin development update was released today.   It sounds like a distributed exchange is not ready yet, but is is in the works.

http://blog.mastercoin.org/2014/01/10/master-protocol-%E2%86%92-mastercoin-development-update-2/

Also I saw in another thread that there is a bounty for distributed exchange, and that good progress has been made.

So it seems that counterparty could still be first with a workable implementation, though that will depend on when bitcoin 0.9 is released.

I dunno what is going on with NXT in that regard, if anything.  anyone?

So, provided that the counterpartyd.conf has changed to include:

bitcoind-rpc-connect=
bitcoind-rpc-port=
bitcoind-rpc-user=
bitcoind-rpc-password=
rpc-user=
rpc-password=

instead of

rpc-connect=
rpc-port=
rpc-user=
rpc-password=

Should I download any new installer for windows? Or do something manually?

How are you guys correlating that these payments come from the same individuals?

hmm i should have been more clear in that update I guess.  

you can do dist ex right now, but it is being limited to test mastercoins until a couple consensus issues get resolved. here is one implementation, as you can see their are transactions on mainnet http://mastercoin-explorer.com/order_books

having looked through the xcp code to me it seems the main difference is that the xcp dev (btw you code is very clear and well commented, easy to read for a noncoder like me) is using what mastercoin calls class c op_return transactions, and mastercoin does class a and class b as well, since when it was initially funded way before the pull request that led to op_return being included in 0.9.  in  that case the xcp code is a bit more rigid, but it allows faster development of a lot of the features in the mastercoin spec.  

obviously everything is open source, so folks can borrow from one another and probably do.

rofl @ the guy trying to claim copyright on proof of burn...

You need to run bitcoind with the command-line option -reindex the first time.

congrats you now have over 500 BTC burned.

who wants to bet me that by the time this is done over 1000 btc will be burned?   i'll give 10:1 odds.

Thanks, that seem to have resolved the situation.
Weird, my mind stopped reading the doc halfway.
Probably because on first-update-this-way I didn't rerun setup.py and yet saw change.

This trouble made me stop from burning more.
Which is probably a good thing after all.