From: Natanael <natanael.l@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
John Hardy <john@seebitcoin.com>
Subject: Re: [bitcoin-dev] Transaction signalling through output address hashing
Date: Sun, 5 Feb 2017 17:22:11 +0100 [thread overview]
Message-ID: <CAAt2M18uMt7BA_brpFM+zipodDkj_bdnZ3SXMxOpVPN+YqgMoA@mail.gmail.com> (raw)
In-Reply-To: <BL2PR03MB4358286BE7F0D51F99B8EC6EE4C0@BL2PR03MB435.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
Den 5 feb. 2017 16:33 skrev "John Hardy via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org>:
Currently in order to signal support for changes to Bitcoin, only miners
are able to do so on the blockchain through BIP9.
One criticism is that the rest of the community is not able to participate
in consensus, and other methods of assessing community support are fuzzy
and easily manipulated through Sybil.
I was trying to think if there was a way community support could be
signaled through transactions without requiring a hard fork, and without
increasing the size of transactions at all.
My solution is basically inspired by hashcash and vanity addresses
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: 1525 bytes --]
next prev parent reply other threads:[~2017-02-05 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 0:13 [bitcoin-dev] Transaction signalling through output address hashing John Hardy
2017-02-05 16:22 ` Natanael [this message]
[not found] ` <BL2PR03MB435D7E36434A342BBEBC735EE410@BL2PR03MB435.namprd03.prod.outlook.com>
2017-02-05 21:06 ` [bitcoin-dev] Fw: " John Hardy
2017-02-05 16:26 ` [bitcoin-dev] " 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=CAAt2M18uMt7BA_brpFM+zipodDkj_bdnZ3SXMxOpVPN+YqgMoA@mail.gmail.com \
--to=natanael.l@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=john@seebitcoin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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