From: Mike Hearn <mike@plan99•net>
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 17:13:47 +0200 [thread overview]
Message-ID: <CANEZrP33d9zHaf9A9+2BG-YHZEf_pA2SSTNL-_Ht4tT22qV6Xw@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpcNd-s9S-zDGO6gGwnd1sFSUikH1fAnCUoG1WiL5kkmVg@mail.gmail.com>
> So, to be specific... a A->B chain of transactions, that collectively
> meet the network's fee requirements?
Yes.
> Ideally the fee, if any, is market based and negotiated. Problem is... like
> democracy, no matter how ugly it is, people have trouble finding a
> better system :)
I think this is something we can explore over the coming years. I
favor having people commonly pass transactions around outside the
broadcast network with the transactions and their dependencies being
broadcast only when there's a lack of trust between recipient and
sender. The block chain is an optional service after all.
> 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.
next prev parent reply other threads:[~2012-04-14 15:13 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 [this message]
2012-04-14 20:20 ` Jeff Garzik
2012-04-14 21:27 ` Pieter Wuille
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=CANEZrP33d9zHaf9A9+2BG-YHZEf_pA2SSTNL-_Ht4tT22qV6Xw@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--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