public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ryan Grant <bitcoin-dev@rgrant.org>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Cc: Peter <peter@coinkite.com>
Subject: Re: [bitcoin-dev] Trying all address types in message signing verification (BIP)
Date: Sat, 23 Jul 2022 04:28:08 +0000	[thread overview]
Message-ID: <CAMnpzfo_tGk3ifbpo5nGn6-+Z1_P=Epw-+JCyGvgWErkkSuVfw@mail.gmail.com> (raw)
In-Reply-To: <YtgDqWSIbX8EJc3B@coinkite.com>

On Wed, Jul 20, 2022 at 9:46 PM Peter (Coinkite Inc) via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> [...] the various BIP-322 proposals never gained wide acceptance.

There's renewed interest in using BIP322 to validate signatures
related to work upgrading the Bitcoin-native Decentralized Identifier
Method (did:btcr) beyond its current specification, to version 2.0.

  https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/bip322-signature-suite.md
  https://www.w3.org/TR/did-core/


      parent reply	other threads:[~2022-07-23  4:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7QoRGux2ow375UP6-XXIF6kI_0tbt-RxKrXiyuDBWVWh6Shjia-ShKy_or5FK9u46KkPAvK2biaSe_x8fMWP0Q==@protonmail.internalid>
     [not found] ` <mailman.84940.1658205911.8511.bitcoin-dev@lists.linuxfoundation.org>
     [not found]   ` <20220719104725.ppic7jy4ghfieeap@artanis>
2022-07-20  4:10     ` [bitcoin-dev] Trying all address types in message signing verification (BIP) Ali Sherief
2022-07-20 13:31       ` Peter (Coinkite Inc)
2022-07-20 21:50         ` Greg Sanders
2022-07-21  7:06           ` Craig Raw
2022-07-22 15:20             ` Ali Sherief
2022-07-21  5:36         ` Ali Sherief
2022-07-23  4:28         ` Ryan Grant [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='CAMnpzfo_tGk3ifbpo5nGn6-+Z1_P=Epw-+JCyGvgWErkkSuVfw@mail.gmail.com' \
    --to=bitcoin-dev@rgrant.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=peter@coinkite.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