Wallets that support 40 byte message attachment via OP_RETURN? Desktop / Mobile?

Question

I see that many new Bitcoin 2.0 apps are making use of the additional OP_RETURN parameter for attaching data. I see that max limit is 40 bytes or roughly 40 characters? My question now regarding OP_RETURN is:

• So is it one OP_RETURN parameter for each bitcoin transaction or per each input/output address? If its each transaction, so its safe to say its about .0001 btc to send 40 byte message?

• Which desktop / mobile wallets support adding a custom OP_RETURN message? (ex. attach a short url link)

• Aside from OP_RETURN message attachment, what other methods are there to attach custom data?

Answer 1

I work with obviously unspendable addresses. Send any one single line from a thin client, phone. Use a core node to bundle long messages with sendmany.

https://live.blockcypher.com/doge/tx/63de9f4da10693813c977e895dafff0ae725ff9011c76d90f483c6243890ebb6/

This message goes on for 83 addresses and includes a real address, which causes the wallet on my phone to complain, but still worked.

Answer 2

So is it one OP_RETURN parameter for each bitcoin transaction or per each input/output address?

One OP_RETURN output per transaction regardless of the number of inputs and outputs is standard for 0.9.x bitcoin core clients.

If its each transaction, so its safe to say its about .0001 btc to send 40 byte message?

Yes, but you should not do it without significant reasons.

Aside from OP_RETURN message attachment, what other methods are there to attach custom data?

There are different methods. You can use fake public keys in bare multisig outputs. Or encode some data with values or addresses of other outputs.

Answer 3

Aside from OP_RETURN message attachment, what other methods are there to attach custom data?

IP Transactions can do that. BIP0070 will probably be able to do that.

Answer 4

Which desktop / mobile wallets support adding a custom OP_RETURN message? (ex. attach a short url link)

Coinb.in

New -> Transaction -> Advanced Options

Null Data (80 byte limit, 40 bytes recommended)

Allow data to be sent within the transaction and stored in the blockchain by using OP_RETURN.

When using this option you may enter a hex string or address into the address field on the output tab.