public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <bitcoin-dev@wuille•net>
To: Bitcoin dev list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP341 test vectors for wallet implementations
Date: Mon, 01 Nov 2021 18:48:49 +0000	[thread overview]
Message-ID: <Vhp3DuXMyu5U7nc8nK6nRT3UiPbWtsTBX6eo1k-VyKRmVizUSyF017nD7XNOY2GNAkcWdnZdjtU5DBhEfB3N43HYKGnbXzERDaXBfV0XpBI=@wuille.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

Hi all,

I wanted to bring some attention to a set of test vectors I'm proposing to add to BIP341 in https://github.com/bitcoin/bips/pull/1225.

These are focused on wallet implementations, covering Merkle root / tweak / scriptPubKey computation from key/scripts, sigmsg/sighash/signature computation for key path spending, and control block computation for script path spending.

Given the short time that remains before BIP341's activation, I think this may be helpful to people working on implementations, even before it's merged. All values in it are automatically generated from an actual scenario tested against Bitcoin Core (which involves constructing and mining transactions with specified data).

The tests are mostly focused on features that are likely useful/testable in implementations right now, and e.g. excludes sighashes that involve annexes for that reason. It's also specific to BIP341, and doesn't cover BIP342 script semantics. Still, if anyone relies on features that are useful, but aren't covered, I'm happy to add more scenarios.

Cheers,

--
Pieter

[-- Attachment #2: Type: text/html, Size: 1576 bytes --]

                 reply	other threads:[~2021-11-01 18:48 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='Vhp3DuXMyu5U7nc8nK6nRT3UiPbWtsTBX6eo1k-VyKRmVizUSyF017nD7XNOY2GNAkcWdnZdjtU5DBhEfB3N43HYKGnbXzERDaXBfV0XpBI=@wuille.net' \
    --to=bitcoin-dev@wuille$(echo .)net \
    --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