public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ryan Grant <bitcoin-dev@rgrant.org>
To: Jude Nelson <judecn@gmail.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Claiming an OP_RETURN Prefix
Date: Thu, 16 Aug 2018 17:32:25 +0000	[thread overview]
Message-ID: <CAMnpzfqLQYboGgGHVYF_SjOs_nZd8cvD3chydcu1W1Ef_kLRPA@mail.gmail.com> (raw)
In-Reply-To: <CAFsQEP1ttFbAZZzz49Jg3E3jbZjztNRDVGJAKOWULYzrn+7obQ@mail.gmail.com>

On Wed, Aug 15, 2018 at 8:40 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.

The hash of the file is deterministic and `ipfs add` tells us what it
is whether the network is connected or disconnected.  We don't upload
files to IPFS until the transaction has settled with several
confirmations.


  parent reply	other threads:[~2018-08-16 17:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 18:34 [bitcoin-dev] Claiming an OP_RETURN Prefix Christopher Allen
2018-08-15 20:33 ` Jorge Timón
2018-08-15 20:40   ` Jude Nelson
2018-08-15 21:54     ` Christopher Allen
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 [this message]
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=CAMnpzfqLQYboGgGHVYF_SjOs_nZd8cvD3chydcu1W1Ef_kLRPA@mail.gmail.com \
    --to=bitcoin-dev@rgrant.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=judecn@gmail.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