public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Forget dormant UTXOs without confiscating bitcoin
Date: Sun, 20 Dec 2015 22:34:06 -0500	[thread overview]
Message-ID: <CADm_Wca33DiFjDttGz2YVzNMEfGKb7GwTz0BuFpz7UOThsnRYQ@mail.gmail.com> (raw)
In-Reply-To: <99D24C78-CAEE-4E48-A454-CA82B317D44B@petertodd.org>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

On Sun, Dec 20, 2015 at 11:35 AM, Peter Todd <pete@petertodd•org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
>
>
> On 20 December 2015 08:30:45 GMT-08:00, Chris Pacia <ctpacia@gmail•com>
> wrote:
> >On Dec 20, 2015 6:34 AM, "Jeff Garzik via bitcoin-dev" <
> >bitcoin-dev@lists•linuxfoundation.org> wrote:
> >
> >> 2) This reverses the useful minimization attribute of HD wallets -
> >"just
> >backup the seed"
> >
> >It would be nice if the bip37 filter matching algorithm was extended to
> >serve up the proof.
> >
> >And if server-based wallets did the same it would preserve the "just
> >backup
> >the seed" functionality.
>
> Exactly! The information will be out there - "just backup the seed"
> requires someone to have the exact same data needed to generate the
> TXO-unspent proof that my proposal requires to spend an old txout.
>
> tl;dr: jgarzik is incorrect; theres no difference at all from the status
> quo.
>

The data stored in the legacy case makes it possible to sign and send a
transaction without any connection to a network.  The data stored in the
upgraded case, absent grandfathering, requires significant network sync at
a minimum.

The user experience and security parameters are different.

Thus, issue/recommendation #1.

[-- Attachment #2: Type: text/html, Size: 1951 bytes --]

  reply	other threads:[~2015-12-21  3:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 20:09 jl2012
2015-12-12 23:01 ` gb
2015-12-13  1:00   ` Vincent Truong
2015-12-13  2:07     ` Gregory Maxwell
2015-12-13  8:13       ` Chris Priest
2015-12-13  8:18         ` Gregory Maxwell
2015-12-13  9:17           ` Chris Priest
2015-12-13  9:24             ` Gregory Maxwell
2015-12-13 18:11             ` jl2012
2015-12-13 21:20               ` Ricardo Filipe
2015-12-13 21:36               ` Tier Nolan
2015-12-20 11:24       ` Peter Todd
2015-12-20 11:34         ` Jeff Garzik
2015-12-20 11:43           ` s7r
2015-12-20 16:30           ` Chris Pacia
2015-12-20 16:35             ` Peter Todd
2015-12-21  3:34               ` Jeff Garzik [this message]
2015-12-21  3:23           ` Tom Harding
2015-12-13 16:14 ` Danny Thorpe

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=CADm_Wca33DiFjDttGz2YVzNMEfGKb7GwTz0BuFpz7UOThsnRYQ@mail.gmail.com \
    --to=jgarzik@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=pete@petertodd$(echo .)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