From: Pieter Wuille <bitcoin-dev@wuille.net>
To: andreas@schildbach.de, bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Taproot testnet wallet
Date: Sat, 09 Oct 2021 16:49:42 +0000 [thread overview]
Message-ID: <jNk5M87QACL8ySLGzR5sQVaJkQcIV8RrHnbWv6-lkjRhjTL6vEmaMJI7hENUO803wSZM0hOaCyeQI3jjPBbJKiMy8gBXtS_HLmKzPivk2M0=@wuille.net> (raw)
In-Reply-To: <cf1aa346-4f0d-8192-c8e8-1861e7840371@schildbach.de>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Oct 9, 2021, 11:36, Andreas Schildbach via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote:
> I'm trying to finish off bitcoinj's implementation for sending to
taproot addresses. For this, I'd like to test against a wallet that can
receive to P2TR and spend back.
> I've been trying to get a taproot address from Bitcoin Core 22.0 and
spent many hours, but in vain. Can someone please simply send my a
testnet wallet that has at least one taproot address? (I don't care
about anyone stealing my testnet coins, so don't worry about the
compromised private key.)
Hi Andreas,
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
I've also created one myself for testing: tb1p84x2ryuyfevgnlpnxt9f39gm7r68gwtvllxqe5w2n5ru00s9aquslzggwq
If you send testnet coins there email me an address, I'll return them.
Cheers,
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1578 bytes --]
next prev parent reply other threads:[~2021-10-09 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 15:36 [bitcoin-dev] Taproot testnet wallet Andreas Schildbach
2021-10-09 16:49 ` Pieter Wuille [this message]
2021-10-15 1:05 ` Anthony Towns
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='jNk5M87QACL8ySLGzR5sQVaJkQcIV8RrHnbWv6-lkjRhjTL6vEmaMJI7hENUO803wSZM0hOaCyeQI3jjPBbJKiMy8gBXtS_HLmKzPivk2M0=@wuille.net' \
--to=bitcoin-dev@wuille.net \
--cc=andreas@schildbach.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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