Quote from: etotheipi on July 11, 2014, 03:01:19 PM

Quote from: rbdrbd on July 11, 2014, 02:39:02 PM

Quote from: PhantomPhreak on July 10, 2014, 04:11:35 AM

Quote from: fthoughts on July 09, 2014, 09:17:56 PM

Hm, I'm curious, how or where are you getting the data to reconstruct the Armory tx? If you haven't looked at their code, I think this approach is perilous, since Armory's custom format will surely throw your code in disarray.

For example, I'm not sure if the bytes from utxo's are appended like this:

Code:

for coin in inputs:
tx_list += get_raw_transaction(coin['txid'], json=False)
for byte in range(0,len(tx_list),80):
txdp.append(tx_list[byte:byte+80] )

I'm looking at https://github.com/bitcoin/bips/blob/master/bip-0010.mediawiki, and, yes, at the code itself. These lines, in particular, are what I'm working off of: https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine/Transaction.py.

I'm actually xnova (another one of the Counterparty devs). Any assistance here would be very much welcome. Getting this working would allow us to add Armory offline signing support to counterpartyd and Counterwallet, which would be great for our users and probably add dozens of more new armory users, at the very least.

From a glance, I'm not sure that you should be using .decode('utf-8') when doing the serializations. This is binary data, not unicode. Construct all pieces as raw binary and convert to hex. There shouldn't be any utf-8 calls in it.

binascii.hexlify() returns ASCII-encoded hex only, at least in Python 3:

Code:

Python 3.4.1 (default, May 19 2014, 17:23:49)
[GCC 4.9.0 20140507 (prerelease)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import binascii
>>> foo = binascii.hexlify(b'\x00')
>>> foo
b'00'
>>>
>>> foo.decode('utf-8')
'00'
>>>