[prev in list] [next in list] [prev in thread] [next in thread]
List: bitcoin-dev
Subject: [bitcoin-dev] Mempool and Privacy
From: alicexbt via bitcoin-dev <bitcoin-dev () lists ! linuxfoundation ! org>
Date: 2022-06-19 16:50:38
Message-ID: mOv_C0lFfadFPK_idvT-D4NQ2GBB_8s10ooKAHTsEKWSOMVPIZmXcs2a3rQcN0aBAr6nH6cW73-jz4DXhX8KchnJILjYUILpPXwVBZxOCyE= () protonmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
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 #5 (text/html)]
<div style="font-family: arial; font-size: 14px;">Hi Bitcoin Developers,</div><div \
style="font-family: arial; font-size: 14px;"><div><br></div><div><span>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:</span></div><div><span><br></span></div><div>GET /mempool?node=1 \
HTTP/1.1</div><div><span><div><span>Host: \
api.spkreuse.fun</span></div><span>Content-Type: \
application/json</span><br></span></div><div><br></div><div><span><span>Node 2 has \
'spkreuse=conflict' saved in bitcoin_rw.conf and it will reject all transaction \
reusing addresses in mempool. </span></span>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.</div><div><br></div><div><span>What other things could affect privacy \
in mempool and not explored yet? I could think of \
3:</span></div><div><br></div><div><span>- RBF policies</span></div><div><span>- \
Rebroadcasting mechanism</span></div><span>- Different types of relay \
fee</span><br></div><div style="font-family: arial; font-size: \
14px;"><span><br></span></div><div style="font-family: arial; font-size: 14px;">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.</div><div style="font-family: arial; font-size: \
14px;"><span><br></span></div><div style="font-family: arial; font-size: \
14px;"><span>/dev/fd0</span></div><div style="font-family: arial; font-size: \
14px;"><br></div> <div class="protonmail_signature_block" style="font-family: arial; \
font-size: 14px;"> <div class="protonmail_signature_block-user \
protonmail_signature_block-empty">
</div>
<div class="protonmail_signature_block-proton">
Sent with <a target="_blank" href="https://proton.me/" rel="noopener \
noreferrer">Proton Mail</a> secure email. </div>
</div>
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic