From: "Jorge Timón" <jtimon@jtimon•cc>
To: Patrick Strateman <patrick.strateman@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Do we really need a mempool? (for relay nodes)
Date: Tue, 21 Jul 2015 00:14:41 +0200 [thread overview]
Message-ID: <CABm2gDqayOVT6YHf5w5qTOtsKCBsOxc=fxMpR2YZJs26km=vNQ@mail.gmail.com> (raw)
In-Reply-To: <55AAACF9.90007@gmail.com>
On Sat, Jul 18, 2015 at 9:46 PM, Patrick Strateman via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> Relay nodes do not need a mempool, but do need some mechanism to avoid DoS
> issues.
>
> Wallet nodes can use the mempool for fee estimation (in addition to looking
> at past blocks).
Exactly, so an anti-DoS mechanism that would be sufficient for a
non-mempool node would be also useful for small values in -maxmempool.
I think a simple cache for transaction validations should be enough.
Please, review a draft for that in the newest #6448.
https://github.com/bitcoin/bitcoin/pull/6448
I would be happy to rebase it back to 0.11 and even 0.10.
prev parent reply other threads:[~2015-07-20 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 18:52 Peter Todd
2015-07-18 19:46 ` Patrick Strateman
2015-07-19 8:59 ` odinn
2015-07-20 22:14 ` Jorge Timón [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='CABm2gDqayOVT6YHf5w5qTOtsKCBsOxc=fxMpR2YZJs26km=vNQ@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=patrick.strateman@gmail$(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