From: Aaron Voisine <voisine@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
Date: Thu, 11 Jun 2015 23:44:57 -0700 [thread overview]
Message-ID: <CACq0ZD4wEBDKV8WtEsZJ54hxA9UP+T2N0g-7cxmgynZK+yaMxA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2MiU8=sUXqAAjoJtkcdu4oAKmqVxM3ERz_fuknzWGiiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
One possible solution that wallets could adopt when blocks fill up, would
be to abandon the p2p network for transaction propagation altogether, and
instead work directly with a handful of the largest miners and pools to get
transactions into blocks. The miners could auction off space in their
blocks with the guarantee that they will be included in the order accepted.
We'd lose the peer-to-peer nature of sending transactions for a federated
service operator style model, but avoid the problem of unpredictable
transaction failure. Also, unlike replace-by-fee, this would allow for
a send-and-forget usage pattern, as well as known up-front fees. Something
like this is certainly what I imagine the large hosted wallet companies
will end up moving to.
Aaron
On Thursday, June 11, 2015, Mike Hearn <mike@plan99.net> wrote:
> > Re: "dropped in an unpredictable way" - transactions would be dropped
>> > lowest fee/KB first, a completely predictable way.
>>
>> Quite agreed.
>
>
> No, Aaron is correct. It's unpredictable from the perspective of the user
> sending the transaction, and as they are the ones picking the fees, that is
> what matters.
>
--
Aaron Voisine
co-founder and CEO
breadwallet.com
[-- Attachment #2: Type: text/html, Size: 1834 bytes --]
next prev parent reply other threads:[~2015-06-12 6:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 17:37 [Bitcoin-development] Proposal: SPV Fee Discovery mechanism Nathan Wilcox
2015-06-10 19:19 ` Aaron Voisine
2015-06-10 20:00 ` Nathan Wilcox
2015-06-10 20:03 ` Peter Todd
2015-06-11 18:30 ` Nathan Wilcox
2015-06-11 18:55 ` Aaron Voisine
2015-06-13 15:38 ` Nathan Wilcox
2015-06-10 21:18 ` Aaron Voisine
2015-06-10 20:26 ` Mike Hearn
2015-06-10 21:18 ` Aaron Voisine
2015-06-11 10:19 ` Mike Hearn
2015-06-11 13:10 ` Peter Todd
2015-06-11 14:11 ` Martin Lie
2015-06-11 17:10 ` Tom Harding
2015-06-11 17:52 ` Mike Hearn
2015-06-12 6:44 ` Aaron Voisine [this message]
2015-06-11 18:18 ` Nathan Wilcox
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=CACq0ZD4wEBDKV8WtEsZJ54hxA9UP+T2N0g-7cxmgynZK+yaMxA@mail.gmail.com \
--to=voisine@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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