From: Anthony Towns <aj@erisian•com.au>
To: Pieter Wuille <bitcoin-dev@wuille•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot testnet wallet
Date: Fri, 15 Oct 2021 11:05:12 +1000 [thread overview]
Message-ID: <20211015010512.GC6451@erisian.com.au> (raw)
In-Reply-To: <jNk5M87QACL8ySLGzR5sQVaJkQcIV8RrHnbWv6-lkjRhjTL6vEmaMJI7hENUO803wSZM0hOaCyeQI3jjPBbJKiMy8gBXtS_HLmKzPivk2M0=@wuille.net>
On Sat, Oct 09, 2021 at 04:49:42PM +0000, Pieter Wuille via bitcoin-dev wrote:
> You can construct a taproot-capable wallet in Bitcoin Core as follows:
> * Have or create a descriptor wallet (createwallet RPC, with descriptors=true).
> * Import a taproot descriptor (of the form "tr(KEY)"), as active descriptor
> (with active=true), where KEY can be a tprv.../* or any other supported key
> expression.
> * Get a new address with addresstype=bech32m
Running master (which has PR#21500 merged), then the above can be
done with:
1. create a descriptor wallet
bitcoin-cli -signet -named createwallet wallet_name=descwallet descriptors=true load_on_startup=true
2. get the associated bip32 tprv private key
TPRV=$(bitcoin-cli -rpcwallet=descwallet -signet listdescriptors true | jq '.descriptors | .[].desc' | sed 's/^.*(//;s/[)/].*//' | uniq | head -n1)
(This step requires PR#21500 to extract the wallet's tprv; you'll need to
be running an updated version of bitcoin-cli here as well as bitcoind. You
could also generate the tprv some other way.)
3. construct the taproot descriptor per BIP 86
DESC="tr($TPRV/86'/1'/0'/0/*)"
CHK="$(bitcoin-cli -rpcwallet=descwallet -signet getdescriptorinfo "$DESC" | jq -r .checksum)"
4. import the descriptor
bitcoin-cli -rpcwallet=descwallet -signet importdescriptors "[{\"desc\": \"$DESC#$CHK\", \"active\": true, \"timestamp\": \"now\", \"range\": [0,1000], \"next_index\": 1}]"
5. get an address
bitcoin-cli -rpcwallet=descwallet -signet getnewaddress '' bech32m
You can then use the signet faucet to send a few million ssats to that
address directly.
Same stuff works with testnet, though I'm not sure if any testnet faucets
will accept bech32m addresses directly.
This is all a bit deliberately cumbersome prior to taproot activating on
mainnet; once that happens and PR#22364 is merged, you'll only need to
do steps (1) and (5).
Cheers,
aj
next prev parent reply other threads:[~2021-10-15 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 15:36 Andreas Schildbach
2021-10-09 16:49 ` Pieter Wuille
2021-10-15 1:05 ` Anthony Towns [this message]
2021-10-15 11:51 ` vjudeu
2021-10-15 14:12 Prayank
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=20211015010512.GC6451@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-dev@wuille$(echo .)net \
/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