Fields for "raw" asm in /api/tx/:hash about insight-api

[matiu]

Currently the output of /api/tx is not been parsed by insight using bitcore, but only proxied from the trusted bitcoind server.
Therefore, the output format is actually from bitcoind RPC interface, plus some info about outpoints and spent added by insight.

Implementing asm_raw would require some changes. You can do it at you app using bitcore's Script.fromHumanReadable.

[prusnak]

I thought that Bitcore is a standalone full node implementation and thus not using bitcoind at all.

[matiu]

@prusnak Bitcore is not, at the moment, a full node implementation. There are some ongoing efforts to do that, but the main work is been done in other directions.

insight does require a trusted bitcoind node to run, and that probably wont change even if bitcore could implement a full node.

[nilnullzip]

@matiu Regarding your reply: "Implementing asm_raw would require some changes. You can do it at you app using bitcore's Script.fromHumanReadable."

Actually I found that does not work. The asm parser requires a hex field to be prefixed by 0x but the asm does not include that prefix.

If the asm is proxied from bitcoind decoderawtransaction, then the "hex" field in scriptPubKey contains the raw. Could you pass that one through? Here's the output I'm talking about from bitcoind:

"vout" : [
{
"value" : 0.00100000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_HASH160 8ade6188f68b3a7cd468f3f322cc97ca61f9adcd OP_EQUAL",
"hex" : "a9148ade6188f68b3a7cd468f3f322cc97ca61f9adcd87",
"reqSigs" : 1,
"type" : "scripthash",
"addresses" : [
"2N5uVe4NsP5WLSDzRUxSC99y7dPzgJxNvfC"
]
}
},

It would be helpful to retain the bitcoind "hex" field name instead of inventing a new term. I found it really helpful that insight uses the exact same format as the bitcoind json.

I need this hex/raw function also. I tried implementing the assembler as you describe but encountered the ambiguity. I couldn't find a good way around it. You can't generally get the raw transaction from bitcoind as bitcoind only tracks addresses for which it has the priv and pub keys.