public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Achow101 <achow101-lists@achow101•com>
To: me@tobin•cc, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP174 PSBT test vector
Date: Tue, 05 Apr 2022 23:21:17 +0000	[thread overview]
Message-ID: <meGUGwCx1VbGvZ_trhPJW_yYJih9R9hoeSYO9k2G7OlweJ2rkQipQJqrs26kqnJf5IGX-NY_VSWyINQ4Wm6VQ5cobwp2DTXtq8CDMifLmMU=@achow101.com> (raw)
In-Reply-To: <20220405225518.GA73803@aerus>

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

The seed is encoded as a WIF private key. Decoding as WIF will result in the 32 byte seed that can be used as specified in BIP 32.

Andrew

-------- Original Message --------
On Apr 5, 2022, 6:55 PM, Tobin Harding via bitcoin-dev wrote:

> Hi,
>
> Does anyone have software that successfully parses the extended private key seed
> found in the BIP174 test vector? I have been implementing the test vector PSBT
> workflow in Rust and have everything working except I can only create the
> extended private key from the xpriv, I am unable to use the seed to create it?
>
> BIP174: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#test-vectors
>
> PSBT workflow in BIP174 starting at the line:
>
> "The private keys in the tests below are derived from the following master private key:"
>
> xpriv:
>
> tprv8ZgxMBicQKsPd9TeAdPADNnSyH9SSUUbTVeFszDE23Ki6TBB5nCefAdHkK8Fm3qMQR6sHwA56zqRmKmxnHk37JkiFzvncDqoKmPWubu7hDF
>
> seed:
>
> cUkG8i1RFfWGWy5ziR11zJ5V4U4W3viSFCfyJmZnvQaUsd1xuF3T
>
> I've tried decoding it as base64 and as base58.
>
> Thanks in advance,
> Tobin.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

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

  reply	other threads:[~2022-04-05 23:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 22:55 Tobin Harding
2022-04-05 23:21 ` Achow101 [this message]
2022-04-06 22:15   ` Tobin Harding

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='meGUGwCx1VbGvZ_trhPJW_yYJih9R9hoeSYO9k2G7OlweJ2rkQipQJqrs26kqnJf5IGX-NY_VSWyINQ4Wm6VQ5cobwp2DTXtq8CDMifLmMU=@achow101.com' \
    --to=achow101-lists@achow101$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=me@tobin$(echo .)cc \
    /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