public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ali Sherief <ali@notatether.com>
To: bitcoin-dev@lists.linuxfoundation.org
Cc: luke_bipeditor@dashjr.org
Subject: [bitcoin-dev] BIP-notatether-signedmessage
Date: Thu, 04 Aug 2022 12:18:56 +0000	[thread overview]
Message-ID: <20220804121851.7e4zoqxaaolseazn@artanis> (raw)
In-Reply-To: <4Lz70s3l79z4x2h7@mail-41103.protonmail.ch>

Hi,

I have created a new BIP, called notatether-signedmessage. It can be viewed at https://github.com/ZenulAbidin/bips/blob/master/bip-notatether-signedmessage.mediawiki.

For those who want a quick summary, it defines a step-by-step process for signing and verifying messages from legacy, native/nested segwit, and taproot addresses. It does not define a new signature format itself, except in the case of Taproot. For those addresses, I have defined a signature format that has 1 byte header/recID, 64 bytes signature, and 32 bytes x coordinate of a public key. This is required to run the BIP340 Schnorr verify algorithm using only the signature - and the header byte is added for backwards compatibility. Otherwise, it completely integrates BIP137 signatures.

I am planning to move that format to its own BIP as soon as possible, in lieu that it is unacceptable to define formats in an Informational BIP.

Please leave your comments in this mailing list. CC'ing BIP editors.

- Ali



       reply	other threads:[~2022-08-04 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4Lz70s3l79z4x2h7@mail-41103.protonmail.ch>
2022-08-04 12:18 ` Ali Sherief [this message]
2022-08-04 17:54   ` [bitcoin-dev] BIP-notatether-signedmessage Ali Sherief
2022-08-04 18:36   ` Peter (Coinkite Inc)
     [not found]   ` <202208041926.37309.luke@dashjr.org>
2022-08-05  4:05     ` Ali Sherief
2022-08-05  6:51       ` Luke Dashjr
2022-08-05  7:39         ` Ali Sherief
2022-08-05  9:12   ` Pavol Rusnak
2022-08-05 10:52     ` Ali Sherief

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=20220804121851.7e4zoqxaaolseazn@artanis \
    --to=ali@notatether.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=luke_bipeditor@dashjr.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