public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "'Pol Espinasa' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: "bitcoindev@googlegroups.com" <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Draft] bip39() Descriptor Key Expression
Date: Mon, 16 Nov 2026 15:52:59 +0000	[thread overview]
Message-ID: <JiUeNigF_rzI9YOrqHZrjBrjYeoxPWHsbVSHAaSoA2vimubD0Z-t8eAxL5DfWGTeWuLGxx3xpg-u6MOjYIS17a_MxFA-GiCM5hmaASrAixU=@protonmail.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1581 bytes --]

Dear list,

I am sharing a BIP draft for a new key expression for output script descriptors.
A mnemonic alone does not fully describe a wallet: reliable recovery also requires information such as the derivation paths and script types used. Descriptors capture that information.
This proposal aims to standarize mnemonic imports into descriptor-based workflows, by allowing wallets to represent an English BIP39 mnemonic and optional passphrase directly through a descriptor.

For example:
wpkh(bip39([word1, ..., wordN], "passphrase")/84h/0h/0h/0/*)

The expression derives the BIP32 master extended private key and behaves like the equivalent xprv key expression, including multi-key expressions, derivation paths and multipath descriptors.

You can find the full text to read and comment on in the following draft PR: https://github.com/polespinasa/bips/pull/2
There is also a first-draft implementation on top of Bitcoin Core here https://github.com/polespinasa/bitcoin/pull/8 in case anyone wants to test it and leave feedback.

Feel free to leave comments in the PR or respond here on the list.


Pol

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/JiUeNigF_rzI9YOrqHZrjBrjYeoxPWHsbVSHAaSoA2vimubD0Z-t8eAxL5DfWGTeWuLGxx3xpg-u6MOjYIS17a_MxFA-GiCM5hmaASrAixU%3D%40protonmail.com.

[-- Attachment #1.1.2.1: Type: text/html, Size: 3401 bytes --]

[-- Attachment #1.2: publickey - polespinasa@protonmail.com - 0x44205759.asc --]
[-- Type: application/pgp-keys, Size: 856 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 323 bytes --]

                 reply	other threads:[~2026-11-16 15:54 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='JiUeNigF_rzI9YOrqHZrjBrjYeoxPWHsbVSHAaSoA2vimubD0Z-t8eAxL5DfWGTeWuLGxx3xpg-u6MOjYIS17a_MxFA-GiCM5hmaASrAixU=@protonmail.com' \
    --to=bitcoindev@googlegroups.com \
    --cc=polespinasa@protonmail.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