From: Mike Hearn <mike@plan99•net>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Draft BIP for geutxos message
Date: Wed, 16 Jul 2014 14:37:35 +0200 [thread overview]
Message-ID: <CANEZrP20E5R3D+Em4hordpSpe-e88iyHwyq=WdffsTCpTm+RVA@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0NhZ=RuUMts19EUhY6C1+dy1yaje3Hb5Lfm+AqjRRL5uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
Thanks Jeff.
I do feel like a lot of this is covered in the writeup I attached to the
implementation pull request, and I went over it again in the ensuing
discussion, and also in the BIP.
The discussion of how to make it secure is covered in the "Upgrade" section
of the writeup and in the "Authentication" section of the BIP. Please do
let me know if these sections are missing something. The ideas discussed
there are not implemented in this pull request because outside of some
special cases, it is a very large project that involves a chain fork. You
can see the start of a solution here:
https://github.com/bitcoin/bitcoin/pull/3977
> If one implements your BIP in a naive manner -- simply find a node, and
> issue a single query -- they are dangerously exposed to malicious
> information. The BIP should describe this major security issue, and
> describe at least one method of solving it (ditto implementation, if
> lighthouse has not already solved this).
>
The BIP already does discuss this, in the authentication section.
Suggestions for how to make it better are welcome.
> Comparison between this and BIP 35 (mempool command) are not apt, as
> miners and full nodes treat "mempool" returned data just like any other
> randomly solicited "tx" command on the network. Unlike "mempool" cmd, this
> "getutxos" cmd proffers post-verification trusted data.
>
I don't think it does proffer that, but if a part of the BIP could be read
as doing so, let me know which part and I'll fix it.
[-- Attachment #2: Type: text/html, Size: 2422 bytes --]
next prev parent reply other threads:[~2014-07-16 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 14:29 Mike Hearn
2014-07-10 14:44 ` Mike Hearn
2014-07-16 12:11 ` Jeff Garzik
2014-07-16 12:37 ` Mike Hearn [this message]
2014-07-16 14:25 ` Jeff Garzik
2014-07-16 14:39 ` Mike Hearn
2014-07-16 14:57 ` Gregory Maxwell
2014-07-16 15:01 ` Mike Hearn
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='CANEZrP20E5R3D+Em4hordpSpe-e88iyHwyq=WdffsTCpTm+RVA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(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