From: John Hardy <john@seebitcoin•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Fw: Transaction signalling through output address hashing
Date: Sun, 5 Feb 2017 21:06:19 +0000 [thread overview]
Message-ID: <BL2PR03MB435DEA7CFB526C4DB58F740EE410@BL2PR03MB435.namprd03.prod.outlook.com> (raw)
In-Reply-To: <BL2PR03MB435D7E36434A342BBEBC735EE410@BL2PR03MB435.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
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@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.
[-- Attachment #2: Type: text/html, Size: 2226 bytes --]
next prev parent reply other threads:[~2017-02-05 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 0:13 [bitcoin-dev] " John Hardy
2017-02-05 16:22 ` Natanael
[not found] ` <BL2PR03MB435D7E36434A342BBEBC735EE410@BL2PR03MB435.namprd03.prod.outlook.com>
2017-02-05 21:06 ` John Hardy [this message]
2017-02-05 16:26 ` Andrew C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BL2PR03MB435DEA7CFB526C4DB58F740EE410@BL2PR03MB435.namprd03.prod.outlook.com \
--to=john@seebitcoin$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox