public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Aaron Voisine <voisine@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
Date: Thu, 11 Jun 2015 12:19:09 +0200	[thread overview]
Message-ID: <CANEZrP2V_XAk-=XSmNywXKXmKN9W-eT_gS72te6P65OqAC5P_Q@mail.gmail.com> (raw)
In-Reply-To: <CACq0ZD6Qr7F7_20Nfd0a8TTHEVMR0fxu-T5bO4FfN1Lp9PcGDQ@mail.gmail.com>

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

>
> If we assume that transactions are being dropped in an unpredictable way
> when blocks are full, knowing the network congestion *right now* is
> critical, and even then you just have to hope that someone who wants that
> space more than you do doesn't show up after you disconnect.
>

Yeah, my proposal is not intended to function correctly with full blocks,
as Bitcoin cannot work at all in such a state. It assumes that fees only
change slowly and that transactions are being cleared normally.

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

  reply	other threads:[~2015-06-11 10:19 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 [this message]
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
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='CANEZrP2V_XAk-=XSmNywXKXmKN9W-eT_gS72te6P65OqAC5P_Q@mail.gmail.com' \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=voisine@gmail.com \
    /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