From: Mike Hearn <mike@plan99•net>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin address TTL & key expiration?
Date: Tue, 15 Jul 2014 18:26:15 +0200 [thread overview]
Message-ID: <CANEZrP1n+oK1_OH2njmYy0S9J1qLb9MqHF2HY6NONovwB9bC0A@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0M9UC+7D+5NK7eHMPMPJb+K-eqpGC77t4ikKLz76GtVPw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
>
> Actually, and this is key, there _are_ reasons why deposits might not
> be able to use PaymentRequests. Payments happen even when
> wallets/computers are offline.
>
I don't understand this point. It's the *sender* that is parsing the
PaymentRequest and following the instructions. By definition the sender
must be online. A computer that is switched off cannot sign a transaction
at all.
> If you have negotiated HD wallet details, you can use a new address
> every time, as mentioned.
Yes, and an extension to BIP 70 to allow for this (or stealth addresses or
whatever) has been discussed several times.
This thread started by proposing (I think) an expiry time for addresses.
BIP70 satisfies this use case, I think we all agree on that. Now for cases
where someone can't use BIP70 for whatever reason, or it's suboptimal,
absolutely we should design extensions to fix that.
[-- Attachment #2: Type: text/html, Size: 1336 bytes --]
prev parent reply other threads:[~2014-07-15 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 8:00 Jeff Garzik
2014-07-15 8:19 ` Wladimir
2014-07-15 8:23 ` Jeff Garzik
2014-07-15 8:31 ` Jeremy Spilman
2014-07-15 8:48 ` Wladimir
2014-07-15 8:20 ` Peter Todd
2014-07-15 10:25 ` Mike Hearn
2014-07-15 14:02 ` Jeff Garzik
2014-07-15 14:27 ` Mike Hearn
2014-07-15 14:48 ` Luke Dashjr
2014-07-15 15:11 ` Jeff Garzik
2014-07-15 15:18 ` Mike Hearn
2014-07-15 15:35 ` Jeff Garzik
2014-07-15 15:41 ` Luke Dashjr
2014-07-15 15:55 ` Jeff Garzik
2014-07-15 16:26 ` Mike Hearn [this message]
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=CANEZrP1n+oK1_OH2njmYy0S9J1qLb9MqHF2HY6NONovwB9bC0A@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