From: prayank@tutanota•de
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Post-mix(coinjoin) usage with multisig and cpfp in bitcoin core wallet
Date: Sun, 24 May 2020 23:44:27 +0200 (CEST) [thread overview]
Message-ID: <M87d6RV--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
I have explained the whole idea with a proof of concept in this link: https://medium.com/@prayankgahlot/post-mix-usage-using-multisig-and-cpfp-e6ce1fdd57a1
Does it make sense to add such options in bitcoin core wallet and how is the overall idea once we have taproot because for now people can check if the tx involves a multisig address?
Reading Peter Wuille's reply here it seems taproot will improve privacy for multisig:
https://www.reddit.com/r/Bitcoin/comments/etagx4/please_explain_taproot_and_schnorr_signatures/fffljnl/
Looking for some feedback to work on this idea and don't want it to just remain an article on medium.
Thanks
Prayank
[-- Attachment #2: Type: text/html, Size: 1296 bytes --]
next reply other threads:[~2020-05-24 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 21:44 prayank [this message]
2020-05-25 6:54 ` ZmnSCPxj
2020-05-25 12:16 ` prayank
2020-05-26 2:46 ` ZmnSCPxj
2020-05-26 12:50 ` Prayank
2020-05-27 4:11 ` ZmnSCPxj
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=M87d6RV--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--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