[bitcoin-dev] Fw: Transaction signalling through output address hashing

John Hardy john at seebitcoin.com
Sun Feb 5 21:06:19 UTC 2017

Probabilistic collisions, while present, would be statistically insignificant at 4 chars length.

Implementation by wallets would just require a loop of their existing address generation until a match is found, trivial to implement. Wallets could provide a dropdown which shows the most commonly used signals as seen on the block chain, or a write-in.

Signalling within OP_RETURN increases the tx size and cost. This address hashing method keeps the very small economic cost of voting off the chain, rather than passing it cumulatively to everyone with the insertion of additional data.

Since I wrote this I have come across a similar idea called CryptoVoter which I think deserves more attention than it has had.

From: Natanael <natanael.l at gmail.com>
Sent: Sunday, February 5, 2017 4:22 PM
To: Bitcoin Dev; John Hardy
Subject: Re: [bitcoin-dev] Transaction signalling through output address hashing

Censorship by miners isn't the only problem. Existing and normal transactions will probabilistically collide with these schemes, and most wallets have no straightforward way of supporting it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170205/e1d82fb4/attachment.html>

More information about the bitcoin-dev mailing list