|
Title: Unable to decode output address Post by: OmegaStarScream on September 29, 2016, 08:56:27 AM I was always wondering how It is possible to burn (destroy) bitcoins , so I google and found this nice article : https://medium.com/@alcio/how-to-destroy-bitcoins-255bb6f2142e#.d2uxzkakv (In case you are interested).
So , from that thread , I ended up with this address 1BitcoinEaterAddressDontSendf59kuE (https://blockchain.info/address/1BitcoinEaterAddressDontSendf59kuE) while checking the transactions , I've seen somewhere there is "Unable to decode output address" and "0 BTC" near them and I want to understand what does it mean ? I searched a little bit but I found a lot of technical details that I don't really understand so I'd appreciate simplifying things. Title: Re: Unable to decode output address Post by: steven0021 on September 29, 2016, 09:19:08 AM Those transactions have OP_RETURN code as output. OP_RETURN allows you to put 80byte long (IIRC) hex string in the blockchain. When blockchain.info decode the raw transaction it expects to find an address for each output scripts so when it can't find one you get that message.
Title: Re: Unable to decode output address Post by: Coding Enthusiast on September 29, 2016, 12:09:38 PM the hex of this transaction (https://blockchain.info/tx/83a23fcf32c5f4d65d707890c52a7807bdae0d7573b2348d6df25773ba4a4a87) looks like this:
Code: 01000000 (====input output and numbers in parenthesis was added ====) (1) is 1BitcoinEat.... hash (2) is the part BC.I can not decode OP_RETURN : 0x6a (3) is the other address output 16c6U.... Title: Re: Unable to decode output address Post by: Carlton Banks on September 29, 2016, 12:28:20 PM OP_RETURN allows you to put 80byte long (IIRC) hex string in the blockchain. That got cut down to 40 bytes, I believe Title: Re: Unable to decode output address Post by: DannyHamilton on September 29, 2016, 12:43:13 PM That got cut down to 40 bytes, I believe No. It got increased from 40 bytes to 80 bytes in Bitcoin Core 0.11.0 (back in July 2015) and has been 80 bytes ever since. Title: Re: Unable to decode output address Post by: Coding Enthusiast on September 29, 2016, 12:45:57 PM OP_RETURN allows you to put 80byte long (IIRC) hex string in the blockchain. That got cut down to 40 bytes, I believe it is still 80 bytes (https://github.com/bitcoin/bitcoin/blob/master/src/script/standard.h#L30) as it is also said in the Wiki (https://en.bitcoin.it/wiki/OP_RETURN) Well, I remember the 2nd layer alt-coin camp complaining about it getting cut to 40 bytes, but I guess that didn't happen in the end. Accept my apologies. Or was it cut to 40, then increased back to 80 again in Bitcoin 0.11, maybe? THE HISTORY (https://github.com/bitcoin/bitcoin/commits/master/src/script/standard.h) i suppose yes in 2014 (https://github.com/bitcoin/bitcoin/commit/a9306587a42eac7fb889b9c8d03140980fdf1398) Title: Re: Unable to decode output address Post by: Carlton Banks on September 29, 2016, 12:50:47 PM Well, I remember the 2nd layer alt-coin camp complaining about it getting cut to 40 bytes, but I guess that didn't happen in the end. Accept my apologies.
Or was it cut to 40, then increased back to 80 again in Bitcoin 0.11, maybe? |