Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: marcotheminer on April 01, 2019, 06:30:50 PM



Title: Finding the Script from "Unable to Decode Output" Transactions
Post by: marcotheminer on April 01, 2019, 06:30:50 PM
Example: https://www.blockchain.com/btc/address/1HunaHazCAVrUh6wY4eXgPTgHdtvt2g24k

Take a look, many transactions since just a couple days.

Now, I understand what "Unable to Decode Output" is: a non-standard script that blockchain.info cannot "figure out". Please correct me if I'm wrong.

My questions are:

How would one find out (is it possible?) the up-to 80 bytes of information in each of those transactions?

What could be the purpose of such transactions? Sharing secret messages? Sharing any sort of info?

Thanks!


Title: Re: Finding the Script from "Unable to Decode Output" Transactions
Post by: djhomeschool on April 01, 2019, 06:44:25 PM
Example: https://www.blockchain.com/btc/address/1HunaHazCAVrUh6wY4eXgPTgHdtvt2g24k

Take a look, many transactions since just a couple days.

Now, I understand what "Unable to Decode Output" is: a non-standard script that blockchain.info cannot "figure out". Please correct me if I'm wrong.

My questions are:

How would one find out (is it possible?) the up-to 80 bytes of information in each of those transactions?

What could be the purpose of such transactions? Sharing secret messages? Sharing any sort of info?

Thanks!

From blockstream.info

(https://blockstream.info/address/1HunaHazCAVrUh6wY4eXgPTgHdtvt2g24k)

Code:
TYPE	OP_RETURN

SCRIPTPUBKEY (ASM)
OP_RETURN OP_PUSHDATA1 0000433f000278046e5fc242dd3c5e0535d39e144ff10be17edb7a9c68a3dfbc587d6c77e39c3ae1c64782e8972f1ab25dbf330b5ca2569107028dcccfa9624db2bac94eaf5deee6e5c5beff281213a1

SCRIPTPUBKEY (HEX) 6a4c500000433f000278046e5fc242dd3c5e0535d39e144ff10be17edb7a9c68a3dfbc587d6c77e39c3ae1c64782e8972f1ab25dbf330b5ca2569107028dcccfa9624db2bac94eaf5deee6e5c5beff281213a1

No idea what OP_RETURN is though


Title: Re: Finding the Script from "Unable to Decode Output" Transactions
Post by: achow101 on April 01, 2019, 07:32:55 PM
No idea what OP_RETURN is though
OP_RETURN just means that the output is unspendable. It's used to indicate that the following script is just arbitrary data that can be pruned from the UTXO set.

In this case, I'm pretty sure the reason for these specific OP_RETURN outputs is for VeriBlock where part of their protocol is to commit data to the Bitcoin blockchain using OP_RETURN outputs.


Title: Re: Finding the Script from "Unable to Decode Output" Transactions
Post by: pooya87 on April 02, 2019, 03:22:29 AM
Now, I understand what "Unable to Decode Output" is: a non-standard script that blockchain.info cannot "figure out". Please correct me if I'm wrong.

that is correct but remember that just because blockchain.info(.com) says they can't decode it doesn't mean the script is actually non-standard. there are some other cases (like SegWit P2WPH outputs) that they also show as "Unable to Decode Output" while it has been standard for more than a year now.


Title: Re: Finding the Script from "Unable to Decode Output" Transactions
Post by: nc50lc on April 02, 2019, 04:39:46 AM
achow101 is correct that those transaction are for VeriBlock and you can verify it by copy-pasting any confirmed transaction from your link to VeriBlock's own mainnet-explorer: https://explore.veriblock.org/search (https://explore.veriblock.org/search)
Also, by doing so, you can get the information about those specific "Unable to Decode Output" from blockchain.com.

Example: Transaction 2a5cb76291b9a38877fd250049d50cdf9bd28ffb80f2b0bfee9154020c3029a4 (https://www.blockchain.com/btc/tx/2a5cb76291b9a38877fd250049d50cdf9bd28ffb80f2b0bfee9154020c3029a4) from the same address.
When searched through their explorer: VeriBlock POP 95E0200278CBE9F93D092819D3130AB577694F0664429988D476254115C2BAA1 (https://explore.veriblock.org/tx/2A5CB76291B9A38877FD250049D50CDF9BD28FFB80F2B0BFEE9154020C3029A4).


Title: Re: Finding the Script from "Unable to Decode Output" Transactions
Post by: marcotheminer on April 02, 2019, 04:05:13 PM
Thanks for replies, all! I will investigate further. Always something to look into on the technical side of things.