* [bitcoin-dev] Mempool and Privacy
@ 2022-06-19 16:50 alicexbt
0 siblings, 0 replies; only message in thread
From: alicexbt @ 2022-06-19 16:50 UTC (permalink / raw)
To: Bitcoin Protocol Discussion
[-- 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 --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-06-19 16:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-19 16:50 [bitcoin-dev] Mempool and Privacy alicexbt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox