MasterCoin: New Protocol Layer Starting From “The Exodus Address”

[grazcoin]

P.S. I added masterchain.info links to the OP and to our reddit side-bar

Thanks

[1713987518]

1713987518

[1713987518]

1713987518

[1713987518]

1713987518

[1713987518]

1713987518

[1713987518]

1713987518

[grazcoin]

Just before this round ends, I decided to challenge the parsing of the different implementations and manually created invalid transactions, according to:
https://bitcointalk.org/index.php?topic=265488.msg3190175#msg3190175

The transactions are:

• https://blockchain.info/tx/c2a904dd47797736617bf5df555f029064de0fc2ff5ba71197638e469caae7f5
• https://blockchain.info/tx/ecb792bf58c67120d6d62149f542271c33e3df046460aebc2bae1012e5ba52e5

On masterchain.info you can see that they don't appear, and if you ask for them directly:

• http://masterchain.info/Transaction.html?tx=c2a904dd47797736617bf5df555f029064de0fc2ff5ba71197638e469caae7f5
• http://masterchain.info/Transaction.html?tx=ecb792bf58c67120d6d62149f542271c33e3df046460aebc2bae1012e5ba52e5

you would see that they are indeed invalid.

For the reason of invalidity, you can check the json:

• http://masterchain.info/tx/c2a904dd47797736617bf5df555f029064de0fc2ff5ba71197638e469caae7f5.json
• http://masterchain.info/tx/ecb792bf58c67120d6d62149f542271c33e3df046460aebc2bae1012e5ba52e5.json

On the first tx, "invalid" field has the value [true, "ambiguous sequence [77, 77, 78]"]
On the second tx, "invalid" field has the value [true, "perfect sequence [75, 76, 77]"]

It seems that mastercoin-explorer.com treats them as valid:
http://mastercoin-explorer.com/transactions/c2a904dd47797736617bf5df555f029064de0fc2ff5ba71197638e469caae7f5
http://mastercoin-explorer.com/transactions/ecb792bf58c67120d6d62149f542271c33e3df046460aebc2bae1012e5ba52e5

On https://masterchest.info they don't appear.
zathras, please verify that the tx got invalid for this reason (and not for some other parsing reason).

I hope this help.

[Tirapon]

What happened to the tool on mastercoin-explorer.com that created transaction specifications for you?

[zathras]

Just before this round ends, I decided to challenge the parsing of the different implementations and manually created invalid transactions, according to:
https://bitcointalk.org/index.php?topic=265488.msg3190175#msg3190175

The transactions are:

• https://blockchain.info/tx/c2a904dd47797736617bf5df555f029064de0fc2ff5ba71197638e469caae7f5
• https://blockchain.info/tx/ecb792bf58c67120d6d62149f542271c33e3df046460aebc2bae1012e5ba52e5

On the first tx, "invalid" field has the value [true, "ambiguous sequence [77, 77, 78]"]
On the second tx, "invalid" field has the value [true, "perfect sequence [75, 76, 77]"]

On https://masterchest.info they don't appear.
zathras, please verify that the tx got invalid for this reason (and not for some other parsing reason).

Hey Grazcoin,

I can confirm both these transactions are dropped as they are ambiguous under the processing rules in my implementation (here)

Thanks!

[bybitcoin]

While contest-form of development is good and healthy at early stages, I hope the foundation get convinced that the current developers are doing pretty well, so decide to allocate a fund to hire them (at least part time) to push things more effectively and more collective based.
By the way I should thank you all for the excellent effort, Tachikoma, zathras and grazcoin, very good work!
And my especial thanks to grazcoin team for their sensational new approach, wonderful

[HammerFist]

While contest-form of development is good and healthy at early stages, I hope the foundation get convinced that the current developers are doing pretty well, so decide to allocate a fund to hire them (at least part time) to push things more effectively and more collective based.
By the way I should thank you all for the excellent effort, Tachikoma, zathras and grazcoin, very good work!
And my especial thanks to grazcoin team for their sensational new approach, wonderful

I don't like this.  It discourages newcomers.  Tomorrow may bring a fourth brilliant coder who would like to get it a try.  However, she will be disinclined to try if grazcoin, zathras and tachi are all warm and fuzzy in bed together with solid jobs.  It is better to have the door wide open to people who want to enter and make it very easy for them to come in. 

I am not saying the early guys don't deserve a great reward for their efforts - they do.  Also, they deserve whatever it takes to keep them going in the future.  But, lets don't put them on easy street while blocking out the path for others to join. 

Let's run another contest.  Make it independent of the features those three have conquered.  Those three continue their efforts (with pay) to complete them.  Those three are excluded from the new contest.  This assures that at the end of the contest, we have three new stars on the team. 

Giving these guys steady jobs now assures a high barrier to entry for newcomers and pushes them off to work on other projects.  We've got about 479 tasks to complete.  Let's form new contests which attract new talent while locking up that great talent we found last time.

[bybitcoin]

I don't like this.  It discourages newcomers.  Tomorrow may bring a fourth brilliant coder who would like to get it a try.  However, she will be disinclined to try if grazcoin, zathras and tachi are all warm and fuzzy in bed together with solid jobs.  It is better to have the door wide open to people who want to enter and make it very easy for them to come in.

I didn't mean guaranteed solid jobs, I meant result-based fund allocated part time jobs for these guys. And of course doors should be open with new contests, so the project be able to attract new talents.

I am not saying the early guys don't deserve a great reward for their efforts - they do.  Also, they deserve whatever it takes to keep them going in the future.  But, lets don't put them on easy street while blocking out the path for others to join.  

Dude, It is not about who deserves the cake or reward, it's about give this proved talents a guaranteed modest piece of cake for them to continue their efforts in the same direction, still it will be result based and their works will be continually monitored.

Let's run another contest.  Make it independent of the features those three have conquered.  Those three continue their efforts (with pay) to complete them.  Those three are excluded from the new contest.  This assures that at the end of the contest, we have three new stars on the team.  

Well you say the same thing as me, but with the opposition mark?! After all this is btt forum

Giving these guys steady jobs now assures a high barrier to entry for newcomers and pushes them off to work on other projects.  We've got about 479 tasks to complete.  Let's form new contests which attract new talent while locking up that great talent we found last time.

Not steady but rather result based fully monitored modest salary packed jobs. One or two new contests will be healthy as well. But I am sure nobody wants it to continue forever, spending money to create contests again and again ad infinitum, mastercoin is not a high school league!
After one or two more contests and when we got a stable team, talent hunting can be continued per se, necessity and applied based, driven by the foundation.

[zathras]

One last update before the contest ends

I felt I was perhaps being a little eager in calling my wallet 'multi-currency' when it only supports transacting Mastercoin & Test Mastercoin.  The wallet has always supported working with Bitcoin balances, but offers no way to actually send Bitcoin.  As such I've now added initial send support (just sendtoaddress via RPC at this stage) for Bitcoin.

Note. to address the inevitable "what's the point when you already have a bitcoin wallet running anyway?" - I'm of the impression that a full-featured Mastercoin wallet should be able to transact in Bitcoin in addition to Mastercoin & the various Mastercoin-backed currencies/derivatives and this just adds the initial round of code.  There is of course no requirement to use this functionality over your local bitcoin wallet.

Unconfirmed transaction support is now included for Bitcoin also.

Additionally I've spun up some extra test machines which has allowed me to locate and resolve some more bugs in the wallet & library - this release should hopefully be less buggy to get running:

Code:

# FIXED: broken dependencies on sqlce libs
# FIXED: getting started finish button empty field check not working
# FIXED: getting started panel may incorrectly fail bitcoind test using finish button while test button shows success
# FIXED: getting started panel transaction index check performed with test button but not finish button
# FIXED: wallet fails to syncronize leaving just two 'thread exited' messages in debug panel
# FIXED: error conditions not examined on blockchain scanning thread exit
# FIXED: address enumeration & BTC balance gathering during startup thread no longer working
# FIXED: getting started finish button not disabled after click so repeated clicks can run setup code multiple times
# FIXED: send address list only populated after full sync, not in startup thread
# FIXED: available balance for bitcoin in send panel incorrectly displays unconfirmed instead of confirmed balance
# FIXED: change of currency does not reset available balance
# FIXED: border paint sometimes does not occur until after first background thread has returned
# FIXED: welcome panel enter key on wallet passphrase does not submit and continue
# FIXED: focus is not on passphrase entry when welcome panel is shown requiring tabs before passphrase entry
# FIXED: default radio button for mastercoin currency type not working

This is a testing release only and is not fit for real usage - do not under any circumstances plug it into a bitcoin wallet with any sizable amount of bitcoins/mastercoins.  Test only with an almost empty wallet.

Source & Binary : GitHub

Note download & extract MasterChestWalletAlphaWin.zip for binary and please remember a transaction index is required to use this software (txindex=1 in bitcoin.conf and next bitcoin run add -reindex switch).

Test safely!

As always please feel free to ask any questions & let me have any feedback, thanks!

[grazcoin]

• Sequences for multisig public keys need to start with 01 instead of 00. If you don't do this more often then not the public key won't be a valid ECDSA point.

Tachikoma:

I was trying to understand the compressed public key issue you described, and I checked your code:
https://github.com/maran/mastercoin-ruby/blob/master/lib/mastercoin-ruby/simple_send.rb#L29
It seems you always add '02' at the beginning, and you never use the '03' option.
Choosing '02' or '03' depends on odd/even characteristics of the data, and you could find an example here:
https://github.com/salfter/fillet/blob/master/hex2wifaddr.py#L193
I am not sure that this is the reason, but maybe it eliminates your voodoo rule.

[zathras]

• Sequences for multisig public keys need to start with 01 instead of 00. If you don't do this more often then not the public key won't be a valid ECDSA point.

Tachikoma:

I was trying to understand the compressed public key issue you described, and I checked your code:
https://github.com/maran/mastercoin-ruby/blob/master/lib/mastercoin-ruby/simple_send.rb#L29
It seems you always add '02' at the beginning, and you never use the '03' option.
Choosing '02' or '03' depends on odd/even characteristics of the data, and you could find an example here:
https://github.com/salfter/fillet/blob/master/hex2wifaddr.py#L193
I am not sure that this is the reason, but maybe it eliminates your voodoo rule.

Hey Grazcoin,

In a nutshell a compressed public key is simply the uncompressed key cut in half and the 02 or 03 prefixed is derived from the last digit of the second half of the uncompressed key (whether odd or even).  Since the first half of the uncompressed key is used for the compressed key, a bitcoin node seeing the transaction has no way to know what the last digit of the second half of the uncompressed key was (as they don't have that half), hence they have no way to verify if it should start with a 02 or an 03.  Thus we don't need to do any evaluation of our data pubkey and can just prefix using a known value (02).

As to using 01 instead of 00 for sequence numbers and ECDSA point validity, to be honest that's above me at the moment (I'm trying to get my head around elliptic curve cryptography in general but it's a slow process!).  All I can say is I have 100% tx acceptance with 0201, but not much joy with 0200 (if I recall correctly, so much has happened this month!).

[grimentz]

As always please feel free to ask any questions & let me have any feedback, thanks!

Hi, I do not manage to compile and build the project with msbuild. Some source and resource files seem to be missing. e.g. My Project\Resources.resx, invalid.png and so on. Am I missing something?

Error:

http://s12.postimg.org/ij3varq1p/masterchest_error.png

[zathras]

Yeah I can see there are some source resources like icons missing from the git repo.  I've done a commit which should resolve it.

[StarenseN]

Zathras, the insallation seems not so easy and I don't wanna spend time on it right now. Is it possible to do a brief tutorial/how-to install your software?

I'd be glad to beta-test it afterwhile !

[grimentz]

Yeah I can see there are some source resources like icons missing from the git repo.  I've done a commit which should resolve it.

Thanks! I am able to compile and build it now.

[zathras]

Zathras, the insallation seems not so easy and I don't wanna spend time on it right now. Is it possible to do a brief tutorial/how-to install your software?

I'd be glad to beta-test it afterwhile !

Sure.  Installation should be pretty straight forward but I'm happy to detail it out here.

1] Ensure you have .NET4 installed
2] Ensure you have the transaction index enabled in your bitcoind/qt server.  This is disabled by default in 0.8.x, and can be enabled by adding txindex=1 to bitcoin.conf and starting bitcoind/qt with the -reindex option.
3] Download the file MasterChestWalletAlphaWin.zip from here (github)
4] Extract the contents to a folder somewhere
5] Open Masterchest_Wallet.exe
6] On the getting started panel, enter your bitcoin rpc server information and click test.  This will check the connection and test for the transaction index.
7] Once you get a successful connection and test, enter a new wallet passphrase and tick the box for preseeded database if you want to use it, then click finish.
    
    

8] You should be at the welcome screen where you can then enter your passphrase to access the wallet.

That should be it!  Let me know if I can help further.

Thanks! I am able to compile and build it now.

Great, let me know if I you have any other questions, happy to answer them in the morning

[dacoinminster]

Should MasterCoin do DNS?

I just noticed that NameCoin is having some serious problems: https://bitcointalk.org/index.php?topic=310954.0

Obviously MasterCoin could do DNS. We'd just need a message for "name=IP address" to register a domain name (probably add a fee to discourage squatting), and the sending address would be authorized to rebroadcast with the same name and a different IP address as needed. Might as well support IPV6 while we're at it . . .

I would consider this feature low priority though, since my feature priority ordering is based on what will raise the price of MasterCoins the most, and this doesn't seem like a huge economic value to me . . .

[ripper234]

Should MasterCoin do DNS?

I just noticed that NameCoin is having some serious problems: https://bitcointalk.org/index.php?topic=310954.0

Obviously MasterCoin could do DNS. We'd just need a message for "name=IP address" to register a domain name (probably add a fee to discourage squatting), and the sending address would be authorized to rebroadcast with the same name and a different IP address as needed. Might as well support IPV6 while we're at it . . .

I would consider this feature low priority though, since my feature priority ordering is based on what will raise the price of MasterCoins the most, and this doesn't seem like a huge economic value to me . . .

+1

While it might be interesting if really needed in the future, it's low priority, and I think Namecoin can be fixed to address these issues (but I haven't dug deep enough into Namecoin code). We shouldn't focus on this.

[grazcoin]

zathras:
What is the reason that this tx is invalid? (It is valid on the other 2 implementations).
https://masterchest.info/lookuptx.aspx?txid=9b7506074bab082a75943f3c67c353e27c4e2a926825aa08ebbf13e27eed1869
It seems that also your parsing says that there are enough funds:
https://masterchest.info/lookupadd.aspx?address=1GD6YyXnd7DKvfUKs22Fp3FSGuvK6n4F4j

[Tachikoma]

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

[troiste]

Hi,

I sent some BTC to that exodus address in mid August, how do I get my 100x Master coins?

Thanks!

You already have them.

See:

http://wiki.mastercoin.org/index.php/FAQ#How_do_I_see_my_Mastercoins.3F
http://wiki.mastercoin.org/index.php/FAQ#How_do_I_send_Mastercoins.3F

Great thanks! I see them

Are there any exchanges out there already?

Thanks