From: "Jeremy Spilman" <jeremy@taplink•co>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Access to Mempool
Date: Fri, 27 Dec 2013 23:29:52 -0800 [thread overview]
Message-ID: <op.w8skf2pmyldrnw@laptop-air.hsd1.ca.comcast.net> (raw)
I was reading there are some commands to access a peer's mempool state.
The purpose being to allow miners to recover faster after a reboot, I
think?
Reading peer mempool definitely allows recovering faster after a reboot.
So does persisting mempool in a database locally. But what can you learn
about a node from its mempool? Basically, are there distinguishing
features in the mempool, or could there be?
Are there transactions you can receive which go into your own mempool but
which you don't forward? How about 'nLockTime' transactions?
Is this new feature off by default? Which clients support it?
By the way, are there recommended places to go to compare features
implemented by different wallet software?
Sorry, so many questions...
next reply other threads:[~2013-12-28 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 7:29 Jeremy Spilman [this message]
2013-12-28 14:46 ` Mike Hearn
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=op.w8skf2pmyldrnw@laptop-air.hsd1.ca.comcast.net \
--to=jeremy@taplink$(echo .)co \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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