From: alicexbt <alicexbt@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Mempool and Privacy
Date: Sun, 19 Jun 2022 16:50:38 +0000 [thread overview]
Message-ID: <mOv_C0lFfadFPK_idvT-D4NQ2GBB_8s10ooKAHTsEKWSOMVPIZmXcs2a3rQcN0aBAr6nH6cW73-jz4DXhX8KchnJILjYUILpPXwVBZxOCyE=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
Hi Bitcoin Developers,
Bitcoin knots has a config option to disallow address reuse in mempool: spkreuse=conflict or GUI -> Settings -> Options -> Mempool. I tried experimenting with it and running 2 nodes(signet) for which anyone can check 'getrawmempool' at a given time using:
GET /mempool?node=1 HTTP/1.1
Host: api.spkreuse.funContent-Type: application/json
Node 2 has 'spkreuse=conflict' saved in bitcoin_rw.conf and it will reject all transaction reusing addresses in mempool. I have tried testing it on signet and it works as expected. Replacement transactions are exceptions and ignored even if address appears twice in mempool. I could not find any issues however debug=mempool did not print logs that could be helpful to know which transactions are getting rejected in mempool for address re-use. So running 2 nodes and comparing mempool transactions.
What other things could affect privacy in mempool and not explored yet? I could think of 3:
- RBF policies
- Rebroadcasting mechanism- Different types of relay fee
This could be used by lot of bitcoin nodes, not sure about miners. I do not believe mempool policies only rely on miner incentives, minimum fee rate won't be be 1 sat/vbyte if that was the case. Even if its never used by lot of nodes and some miners, it was fun to play with and I like knots for providing such options.
/dev/fd0
Sent with [Proton Mail](https://proton.me/) secure email.
[-- Attachment #2: Type: text/html, Size: 2513 bytes --]
reply other threads:[~2022-06-19 16:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='mOv_C0lFfadFPK_idvT-D4NQ2GBB_8s10ooKAHTsEKWSOMVPIZmXcs2a3rQcN0aBAr6nH6cW73-jz4DXhX8KchnJILjYUILpPXwVBZxOCyE=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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