From: alicexbt <alicexbt@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] P2P trading replacement transactions
Date: Fri, 05 Aug 2022 14:44:52 +0000 [thread overview]
Message-ID: <AnStgXF197_nYPr6hRYS8w4aAHnBLqxhxJdQTFk_wtJmxlnqv0AJMdHtKuuYCXFMfvcTOyTDvbg75q7aq45NVMLbRKUOb_5DW87wv8Aw5q8=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
Hi Bitcoin Developers,
Does it make sense to trade replacement transactions for privacy? I have shared basic details to implement this and would love to read opinions about it or ways to improve it:
=============================
alice
=============================
tx1: input a (0.01) -> output b1 (0.008)
-> change c1 (0.001)
tx2: input a (0.01) -> output e2 (0.007)
-> output f2 (0.001)
=============================
bob
=============================
tx1: input d (0.011) -> output e1 (0.007)
-> change f1 (0.003)
tx2: input d (0.011) -> output b2 (0.008)
-> output c2 (0.001)
=============================
carol
=============================
- creates an API to manage trades that will use 2 of 3 multisig
- alice and bob create orders for replacement
- either they could be matched automatically using some algorithm or bob manually accepts the offer
- 2 of 3 multisig is created with Alice, Bob and Carol keys
- bob locks 0.01 BTC in it and shares outputs e2,f2 with alice
- alice signs tx2 and shares tx with bob
- alice locks 0.011 BTC in it and shares outputs b2,c2 with bob
- bob signs tx2 and shares with alice
- both replacement txs can be broadcasted
- funds are released from 2 of 3 multisig with a tx having 3 outputs (one to pay fee which goes to carol)
positives:
- privacy
negatives:
- extra fees
- will take some time although everything will be managed by wallet with API provided by carol
- need to lock bitcoin with same amount as used in tx1
- amounts could still be used to link txs in some cases- carol and other peer knows the details
/dev/fd0
Sent with [Proton Mail](https://proton.me/) secure email.
[-- Attachment #2: Type: text/html, Size: 4820 bytes --]
next reply other threads:[~2022-08-05 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 14:44 alicexbt [this message]
2022-08-06 12:55 ` Michael Folkson
2022-08-06 14:11 ` alicexbt
2022-08-06 14:16 Ali Sherief
2022-08-08 13:12 ` alicexbt
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='AnStgXF197_nYPr6hRYS8w4aAHnBLqxhxJdQTFk_wtJmxlnqv0AJMdHtKuuYCXFMfvcTOyTDvbg75q7aq45NVMLbRKUOb_5DW87wv8Aw5q8=@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