From: Ali Sherief <ali@notatether•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP-notatether-signedmessage (appendix)
Date: Fri, 05 Aug 2022 07:50:17 +0000 [thread overview]
Message-ID: <q-wyD4WemLRDZ1-QWcqtJoYnuqJFLMnxKRYgAjqAMoMpI2S6h2S5LB1oVIxw9tTAJrX3wvzYAH0dJCHxhUVrFK9DiVoOV86l7sOR7O2WLb0=@notatether.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Also, I forgot to write in the previous message, that this BIP is not a standard - that's the reason I raised the N+1 problem in the first place. As mentioned previously, it's strictly limited to a reference manual - which could've been hosted anywhere else (such as my own website), but these instructions ought to be made official.
- Ali
[-- Attachment #2: Type: text/html, Size: 432 bytes --]
reply other threads:[~2022-08-05 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='q-wyD4WemLRDZ1-QWcqtJoYnuqJFLMnxKRYgAjqAMoMpI2S6h2S5LB1oVIxw9tTAJrX3wvzYAH0dJCHxhUVrFK9DiVoOV86l7sOR7O2WLb0=@notatether.com' \
--to=ali@notatether$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)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