From: Sjors Provoost <sjors@sprovoost•nl>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
DKBryant@gmail•com
Subject: Re: [bitcoin-dev] Sign / Verify message against SegWit P2SH addresses.
Date: Sat, 9 Dec 2017 13:57:52 +0100 [thread overview]
Message-ID: <69F75C75-6E51-4189-B3AE-032573B49A92@sprovoost.nl> (raw)
In-Reply-To: <CAAUFj10gEPBS3nTZ6aJn4UazhcJKPni6_pYGWwOs+QNeDo9NaA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1700 bytes --]
I would like to see this specifically for P2SH-PWPKH and/or native SegWit bech32 addresses.
Use cases I can think of are "I'm the whale in charge of these funds, listen to me" and some form of polling.
It's nice if funds aren't excluded from these type of functionalities just because they have a complicated redeem script. So something more generic like the Elements implementation / suggestion Greg Maxwell referred to in the Github thread would be nice too.
Is it also useful or possible to sign a message proving you are able to redeem some arbitrary branch in a MAST-like tree of scripts? What about being a minority part of a multisig?
All these features have privacy trade-offs, as well as perhaps security trade-offs, e.g. when you reveal a public key that was otherwise hidden behind a hash (i.e. if someone were to break secp256k1, they'd first organize a popular poll).
There's no BIP for the current message signing mechanism either afaik.
Sjors
> Op 8 dec. 2017, om 19:25 heeft Dan Bryant via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> het volgende geschreven:
>
> I know there are posts, and an issue opened against it, but is there anyone writing a BIP for Sign / Verify message against a SegWit address?
>
> I realize it is not a feature in wide use, but I think it still serves an important purpose, such as when proof of assets are requested.
>
> ref: https://github.com/bitcoin/bitcoin/issues/10542 <https://github.com/bitcoin/bitcoin/issues/10542>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #1.2: Type: text/html, Size: 2755 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-09 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 18:25 Dan Bryant
2017-12-09 12:57 ` Sjors Provoost [this message]
2017-12-19 21:36 ` Pavol Rusnak
2017-12-19 21:58 ` Mark Friedenbach
2017-12-21 11:19 ` Damian Williamson
2017-12-21 16:29 ` Mark Friedenbach
2017-12-21 17:23 ` Jason Dreyzehner
2017-12-21 22:22 ` Dan Bryant
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=69F75C75-6E51-4189-B3AE-032573B49A92@sprovoost.nl \
--to=sjors@sprovoost$(echo .)nl \
--cc=DKBryant@gmail$(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