Quote from: FrictionlessCoin on January 07, 2015, 04:25:47 PM

Quote from: kraizi on January 07, 2015, 03:18:01 PM

Quote from: mrbodz on January 07, 2015, 07:42:07 AM

Quote from: kraizi on January 07, 2015, 03:46:55 AM

Quote from: ahmed_ on January 04, 2015, 01:16:41 AM

0.9.3 is COMPLETE. As i stated earlier it has been for some time (In the time since its been done ive even hard forked DGC to V3 from the original V2 code) which shows the time since its been done. If @Frictionless you do plan on doing it. I must insist that you start ASAP. Once v0.10 launches i plan on upgrading straight to it, and any of your counterparty work if not completed will NOT be ported. Which will leave you left with porting counterparty to a 0.10 base.

Ahmed

@Ahmed: Are you saying a 0.9.x implementation of Counterparty won't work with 0.10.x clients? Please clarify.

not at all. I'm saying i wont put put a 1/2 backed counterparty implementation into 0.10. It'll have to be fully working when i upgrade ixc to 0.10 or it wont go in at all. (I've already started work on the changes needed)

I'm still not understanding. I thought Counterparty could be deployed independant from the crypto client software. Bitcoin actually tried to kill Counterparty by reducing the size of OP_RETURN, but it was deployed regardless. So it shouldn't require any work on your part (iXcoin client) to get Couterparty working. Am I missing something?

The OP_RETURN functionality isn't in the old version of IXC that is deployed at GHASH.IO.

Yes, I know most pools are still using the ancient version 0.3.24, but it sounded like Ahmed was saying you need to target your implementation of counterparty to version 0.9.x or 0.10.x. I thought it didn't matter. They will both have OP_RETURN = 80 bytes. Right?