From: Christopher Allen <ChristopherA@lifewithalacrity•com>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Jude Nelson <judecn@gmail•com>
Subject: Re: [bitcoin-dev] Claiming an OP_RETURN Prefix
Date: Wed, 15 Aug 2018 14:54:50 -0700 [thread overview]
Message-ID: <CACrqygBJ=RdPpHqHzPNqqj0V2w5XL6GVtKobOWnj1EsVykUS8w@mail.gmail.com> (raw)
In-Reply-To: <CAFsQEP1ttFbAZZzz49Jg3E3jbZjztNRDVGJAKOWULYzrn+7obQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Wed, Aug 15, 2018 at 2:24 PM Jude Nelson via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Can a miner identify which transactions came from your software simply by
> running a copy themselves? If so, then they can censor your transactions
> no matter how you encode them.
>
Possibly, but in the IPFS case I suspect the latency required to inspect
all hashes would likely impact the ability of the miner to succeed in the
block. (True? I don’t touch mining software.)
Thus as long as all hashes look the same, and there are multiple content
addressable schemes that use hashes that have to be searched in order to
know to censor, you have to censor all or none.
— Christopher Allen
>
[-- Attachment #2: Type: text/html, Size: 1273 bytes --]
next prev parent reply other threads:[~2018-08-15 21:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 18:34 Christopher Allen
2018-08-15 20:33 ` Jorge Timón
2018-08-15 20:40 ` Jude Nelson
2018-08-15 21:54 ` Christopher Allen [this message]
2018-08-16 1:06 ` Luke Dashjr
2018-08-16 2:22 ` Lautaro Dragan
2018-08-16 2:37 ` Luke Dashjr
2018-08-16 17:32 ` Ryan Grant
2018-08-15 21:46 ` Peter Todd
-- strict thread matches above, loose matches on Subject: below --
2018-08-05 21:11 Lautaro Dragan
2018-08-05 23:57 ` Peter Todd
2018-08-06 0:55 ` Lautaro Dragan
2018-08-06 1:54 ` CryptAxe
2018-08-06 2:04 ` Luke Dashjr
2018-08-06 2:19 ` Lautaro Dragan
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='CACrqygBJ=RdPpHqHzPNqqj0V2w5XL6GVtKobOWnj1EsVykUS8w@mail.gmail.com' \
--to=christophera@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=judecn@gmail$(echo .)com \
/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