public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: AdamISZ <AdamISZ@protonmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Draft BIP for SNICKER
Date: Sun, 01 Sep 2019 13:46:57 +0000	[thread overview]
Message-ID: <UiQv441rv_K_0cjwHlGpfL4jDhYibQ_cvgQMqGG4SPdXGf8PSaAWj9v3Um7ijn35A5r-kP2-V-MMNONjL0T7QtcIdfdVc86YsE5m1sDv5G4=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

Hello list,
Here is a link for a draft of a BIP for a different type of CoinJoin I've named 'SNICKER' = Simple Non-Interactive Coinjoin with Keys for Encryption Reused.

https://gist.github.com/AdamISZ/2c13fb5819bd469ca318156e2cf25d79

Summary in document abstract and motivation, but also there is a more discursive blog post I wrote a while back, linked in the abstract, if you find that helpful.

Purpose of writing this as a BIP:
There was some discussion on the Wasabi repo about this recently (https://github.com/zkSNACKs/Meta/issues/67) and it prompted me to do something I should have done way back when I came up with the idea in late '17: write a technical specification, because one of the main attractive points about this is that it isn't a hugely difficult task for a wallet developer to implement (especially: Receiver side), and it would only really have value if wallet developers did indeed implement it. To be specific, it requires ECDH (which is already available in libsecp256k1 anyway) and ECIES which is pretty easy to do (just ecdh and hmac, kinda).

Plenty of uncertainty on the specs, in particular the specification for transactions, e.g. see 'Partially signed transactions' subsection, point 3). Also perhaps the encryption specs. I went with the exact algo already used by Electrum here, but it could be considered dubious (CBC).

Thanks for any feedback.

Adam Gibson / waxwing

Sent with [ProtonMail](https://protonmail.com) Secure Email.

[-- Attachment #2: Type: text/html, Size: 2043 bytes --]

             reply	other threads:[~2019-09-01 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-01 13:46 AdamISZ [this message]
2019-10-20  0:29 [bitcoin-dev] Draft BIP for SNICKER SomberNight
2019-10-21  0:06 ` David A. Harding
2019-10-21 11:00   ` Riccardo Casatta
2019-10-21 15:04   ` SomberNight
2019-10-22 13:21     ` AdamISZ
2019-11-06 16:52       ` Riccardo Casatta
2019-11-22 14:02         ` AdamISZ
2019-11-22 14:57           ` popo
2019-11-23 12:43             ` AdamISZ

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='UiQv441rv_K_0cjwHlGpfL4jDhYibQ_cvgQMqGG4SPdXGf8PSaAWj9v3Um7ijn35A5r-kP2-V-MMNONjL0T7QtcIdfdVc86YsE5m1sDv5G4=@protonmail.com' \
    --to=adamisz@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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