public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: David Vorick <david.vorick@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Cc: Pieter Wuille <pieter.wuille@gmail.com>
Subject: Re: [bitcoin-dev] Miniscript
Date: Tue, 20 Aug 2019 08:14:13 +0000	[thread overview]
Message-ID: <YFM_3Midr1wdjxhejsksW0i4gTER2cF9XsjETAbJvnO_I77zkwJTHXKdDMK0qKSebO0KVTJ3sH0moZ6_olKUGAec0u9sgprInc6M3ktQR7w=@protonmail.com> (raw)
In-Reply-To: <CAFVRnyp0Z997-UwJMFn3H7N0ogHTkxc+fDj-yROit3coUk1rxw@mail.gmail.com>

Good morning David,

> Today, new Bitcoin applications such as JoinMarket, Wasabi wallet, and Arwen all
> suffer from a problem of having novel bitcoin scripts.

For CoinJoin (JoinMarket, Wasabi) at least, I believe there is no need of novel Bitcoin SCRIPTs.
Indeed, from what I can tell they use only P2WPKH `SIGHASH_ALL` signatures and P2WPKH outputs: there seems to be nothing to analyze there.

I do not believe Miniscript would benefit those in particular.
(though miniscript does have other benefits as well: in particular sufficiently-advanced miniscript compilers will be able to write shorter SCRIPTs than mere unaided humans can)

I have not investigated much of Arwen yet but it seems to me to be a sort of exchange-specific payment-channel implementation.

Regards,
ZmnSCPxj


      reply	other threads:[~2019-08-20  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 23:17 [bitcoin-dev] Miniscript Pieter Wuille
2019-08-20  7:15 ` David Vorick
2019-08-20  8:14   ` ZmnSCPxj [this message]

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='YFM_3Midr1wdjxhejsksW0i4gTER2cF9XsjETAbJvnO_I77zkwJTHXKdDMK0qKSebO0KVTJ3sH0moZ6_olKUGAec0u9sgprInc6M3ktQR7w=@protonmail.com' \
    --to=zmnscpxj@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=david.vorick@gmail.com \
    --cc=pieter.wuille@gmail.com \
    /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