Shawn A. Wilson

I admit I'm still pretty ignorant to the actual standard(s) and protocol requirements, so I have not tried it with OP_PUSH. That's a relief if we can actually get more...

Thanks, I'm on it! Do you have any insight about the rejection of transactions with multiple OP_RETURN vouts? The Script wiki says: > Currently it is usually considered non-standard (though...

I just did a successful test too. Waiting for it to confirm to be sure.

# Blockchain storage else: size = len(dest) script = OP_RETURN if size > MESSAGE_LIMIT_SANS_PUSH: script += OP_PUSHDATA_1 script += size.to_bytes(1, byteorder='little') + dest output_block += b'\x00\x00\x00\x00\x00\x00\x00\x00'

I think yours might be more future-proof, moving into OP_PUSHDATA_2 :) This got me curious though, since the size has been appended immediately after OP_RETURN when there is no OP_PUSHDATA,...

Have you seen https://github.com/grantcoin/grantcoin/blob/master/contrib/counterpartyd/lib/bitcoin.py ? That `serialize()` function is a beauty. Notice how it too seems to imply that multiple OP_RETURN is supported. I'm going to try this against my...

I answered my question just as I was asking it. It's a hack, really, since pushdata ops are seemingly the only op type allowed to follow an op_return... they simply...

You know you want to add that PUSHDATA_4 now... otherwise you're only going halfway on the not-expected-to-work-now-but-maybe-later ops :)

Yeah it must be something like that. I only just realized that there are no opcodes 1-75, so it is in fact defined that anytime you expect to read an...

Only issue remaining here is the multiple OP_RETURN support. I recommend we simply raise an exception for now if multiple OP_RETURN outputs would be created, since the API does not...