From: Pieter Wuille <pieter.wuille@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin TX fill-or-kill deterministic behavior
Date: Sat, 14 Apr 2012 23:27:16 +0200 [thread overview]
Message-ID: <20120414212715.GA6131@vps7135.xlshosting.net> (raw)
In-Reply-To: <CA+8xBpfKpzeq7qSUV5w6JNtTE1-zu58Zg_KCbFAx0JTGeeUG1g@mail.gmail.com>
On Sat, Apr 14, 2012 at 04:20:50PM -0400, Jeff Garzik wrote:
> >> Furthermore, many of these ideas -- like sending TX's directly to the
> >> merchant -- involve far more direct payee<->payer communication on the
> >> part of the wallet client than is currently envisioned
> >
> > Yes, though it's worth remembering that the original Bitcoin design
> > did have participants communicate directly. When I talked with Satoshi
> > in 2009 he saw the pay-to-IP-address mode imagined as the normal way
> > to make payments, with pay-to-address being used as a kind of backup
> > for when the recipient was offline.
> >
> > In the end that's not how things evolved, but it the pendulum could
> > easily swing back the other way.
>
> But I also have a "gut feeling" that these sorts of payments and
> direct communication should be done via a wholly separate protocol
> than the bitcoin P2P protocol. Doing p2ip as it was done originally,
> inside the bitcoin P2P protocol, was a mistake. Extensible as it is,
> I think a better job -- and faster evolution -- can be done with a
> separate protocol on a separate port.
>
> Some HTTP derivative would probably make life easier for mobile
> payments and firewalled scenarios, and for client->merchant
> communications, for instance.
Have you ever read https://gist.github.com/1237788 ?
--
Pieter
next prev parent reply other threads:[~2012-04-14 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 18:38 Jeff Garzik
2012-04-12 19:19 ` Alan Reiner
2012-04-12 19:26 ` Jeff Garzik
2012-04-13 8:35 ` Andy Parkins
2012-04-13 10:04 ` Mike Hearn
2012-04-13 16:41 ` Jeff Garzik
2012-04-14 15:13 ` Mike Hearn
2012-04-14 20:20 ` Jeff Garzik
2012-04-14 21:27 ` Pieter Wuille [this message]
2012-04-14 22:49 ` Jeff Garzik
2012-04-15 8:12 ` Andreas Schildbach
2012-04-15 10:54 ` Jorge Timón
2012-04-15 15:17 ` Jeff Garzik
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=20120414212715.GA6131@vps7135.xlshosting.net \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(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