Hello, all.
I'm having trouble with a Mastercoin transaction that I just crafted (using my own software): 'ecb77ee990de29745de949462e1f6e44584c310a0da12c9fbdf86dbe6ffabcfc'. It's called 'Valid' on Mastercoin explorer, but the destination address isn't being properly recognised. It isn't even showing up on Masterchest. It seems that the problem may be with the sequence numbers, which are, in that transaction, ascending. Previous transactions that I sent from that address (using Test MSC), used descending sequence numbers and were parsed properly. But the latest spec (on GitHub) says that they should be ascending, no? In any case, it's not a big deal to me if the transaction in question is invalidated, because I control the destination address, too.
So for this one, it looks like a mastercoin transaction (specifically Class A simple send):
Console.WriteLine(mlib.ismastercointx(bitcoin_con, "ecb77ee990de29745de949462e1f6e44584c310a0da12c9fbdf86dbe6ffabcfc"))
simple
However as you note the sequence numbers are not correct:
50 15a4XCuWmx2cCQVf8wZK7mqdvj5uwo1vby
51 15efTnSCG13druGmetEp1AULCEqudtCSwq
Sequence number 51 is your data address, so your reference address should be 52, not 50 - this is why Masterchest throws it out.
From my suggested appendix:
The reference address sequence number must be the data address sequence number + 1
I hope JR won't mind me saying this, but I think my suggested
appendix is the most up to date reflection of how we're parsing transactions at this point in time. With that said I understand JR is slap bang in the middle of a spec update, and these changes will (I believe) make it into rev 1.2 of the spec.
Tachikoma, I don't consider this valid but mastercoin-explorer seems to (though it does seem to throw a bad destination address), is that a bug or do we have differing interpretations of Class A?
Thanks!
. 
