(ATTN Wallet Devs) Wallet support for "op_return" parameter in bitcoincash: URI's

on

Electron Cash has recently added support for "op_return" parameters in bicoincash: style URI's.

https://github.com/Electron-Cash/Electron-Cash/commit/530b84e62f584380c1e9eedb80a28c652f77b737

The use-case for this is that it allows one to track a particular wallet address for a transaction without having to act as a mediator of exchange (i.e. first receiving the payment to a controlled address and then forwarding it to the target address). Acting as a mediator of exchange carries high risk (potential for forwarding service to get hacked) and introduces a lot of technical overhead.

There are a few projects I'm working on that require this functionality and it opens up quite a few new use-cases.

  1. Comments service - Here I'm referring to something similar to Disqus. A user types a comment on a page, but in order for that comment to be submitted, they must scan a QR code and post it as a BCH transaction. The URI might look something like: bitcoincash:qqelaxzt50r0r789df90f0njrpnfp3apk56dt2nk5m?op_return={SHA256(URL)}_I%20really%20like%20this%20movie
  2. Accounting - Similar principle to how current Direct Deposit works. Attaching an ID for the reciever so that they can identify the transaction.
  3. Memo.cash - Great service, but in a similar manner to how Twitter contains a "Share" button with pre-filled text, this would allow a user to simply scan a QR code and "share" a comment natively through their wallet application.

If wallet developers could consider adding support for this, it'd be much appreciated.

submitted by /u/jimfriendo
[link] [comments]

source https://www.reddit.com/r/btc/comments/9zv4zv/attn_wallet_devs_wallet_support_for_op_return/

Comments

Post a Comment