I've created public keys for a  "Sell Mastercoin for Bitcoin" offer. I would appreciate it if an other developer could decode the keys and tell me what they think it says before I broadcast it to the world

Payment confirmed, thanks again!

MSC received. Thanks for the generous offer lishbtc.

I will focus on concatting for now but I would love to hear from Grazcoin and Zarthras when you guys have the chance.

Address confirmed!

I'm missing a whitepaper to read or at least some documentation. It's not in the OP. Do you know if it can be found somewhere else?

I'm not sure if this has been discussed before but I couldn't find it. I'm trying to work on encoding Mastercoin data that's larger then just one public key and I'm wondering how we should split data across two keys.

The most space efficient way would be to just concat the two keys as it were and divide them in the middle. (I've added parentheses around the compressed key and sequence for easier readibility)

I.e.
(0201)00000014000000020000000005f5e10000000000000f424060000000000018
(0202)6a00000000000000000000000000000000000000000000000000000000000

The last value here being 186a.

What we could also do is only have whole values per key. In that example the data would be divided as follows.

(0201)00000014000000020000000005f5e10000000000000f424060000000000000
(0202)186a000000000000000000000000000000000000000000000000000000000

I personally prefer the latter version as I think it's cleaner but it does reduce the available space in general.

Thoughts?

Could you explain what you are talking about?

Confirmed as well. Since the price is very volatile the last 24 hours (High: 146.95, low: 135.00) I would recommend you change the amounts before paying out or you might pay out too much, or too little.   

I'm guessing it were all small inputs and the transaction size became very large resulting in a higher required fee. 

Yeah I'm looking over the fee code handling for the Lite GUi at the moment and it's pretty crappy. Since 1.9 is a rewrite anyway I will see if we can share the fee code between the GUI's.

Thanks for the report.

Electrum is licensed under GNU GPL 3. You are free to modify the source code to your hearts content.

This shouldn't be the case. Which version of Electrum are you using?

How high are your fees?

Man I thought I squashed that bug. I'm working on refactoring the whole blockchain scanning part anyway so I will just take this in the new implementation.

Congrats guys. I think we should be very proud of what we accomplished together in such a short timeframe!

Not yet. But the protocol has a build in exchange option, as soon as it's coded up

I'm betting it's a float rounding error.

Code contributions

Mastercoin-ruby: A ruby library to parse MasterCoin data. Source

• Decoda a Mastercoin data-address
• Decode a Mastercoin data-public key
• Encode data to an address
• Encode data to a public key
• Advise how to create a 'old school' transaction using sendmany
• Get the amount of coins bought via Exodus for a given Bitcoin address
• Get the amount of coins bought via Exodus for a given Bitcoin transaction-id
• Decode a Mastercoin transaction based on given Bitcoin transaction-id
• Create and relay a Mastercoin multisig transaction through Bitcoind

Mastercoin-explorer.com: A Ruby on Rails application to index all Mastercoin transactions and show other data. Source.

• Index all Mastercoin related transactions both Exodus payments and simple send transactions.
• Offer a public JSON API so others can easily parse this data without having to index everything themselves. Documentation here.
• Multi-currency support currently has real and test Mastercoins

Mastercoin-wallet: A (QT-based) Mastercoin thin-client implementation. Source

• Uses the forementioned Mastercoin-explorer API to communicatie balance data.
• Only requires a private key with an existing Mastercoin balance to use.
• Saves keys encoded in config files.
• Does not require local Bitcoind/QT.
• Uses multisig approach.

Other contributions

• Come up with multisig approach to replace data-addresses.
• Ported J.R.'s Python script for creating transactions to Mastercoin-Explorer, so people can create transactions without downloading custom software.
• Cross-checked parsing code with implementations by grazcoin and Zathras
• Answered numerous technical questions from other developers on the forums/irc
• Offered an alternative "Selling Mastercoin for Bitcoin spec"

Ik heb succesvol een aankoop gedaan via Bitspenders, alles is vlekkeloos verlopen en had netjes volgende dag mijn aankoop binnen. In het verleden behaalde resultaten bieden geen garantie voor de toekomst maar mijn ervaring was dus geweldig