From: blocktraveler <ueberspannung@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Add importprivkeys RPC
Date: Fri, 3 Oct 2025 00:34:51 -0700 (PDT) [thread overview]
Message-ID: <ad14b140-9e02-466c-8226-304ec651f4ben@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1331 bytes --]
Hy there!
Unfortunately, the PRs are locked, so I'm sharing my thoughts this way.
Over the years, people have asked countless times on various platforms how
to import private keys (both legacy and Bech32/SegWit) into a Bitcoin Core
descriptor wallet. This issue is especially common in Namecoin. I see no
reason why importing private keys, a very basic feature, should be
restricted to the point that it's impossible for the average user to
succeed. That's why I created the Core-Wallet-Migration-Tools
<https://github.com/blocktraveler/Core-Wallet-Migration-Tools> in Python.
However, it would be much easier to have an 'importprivkeys' RPC for
descriptor wallets (not to be confused with the legacy 'importprivkey'
call). Pls check my initial thoughts:
Proposal: Add importprivkeys RPC (helper for WIF → descriptor import)
<https://gist.github.com/blocktraveler/3e6198c698a272bd8b13b16e0f13d390>
Thx!
Uwe
--
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/ad14b140-9e02-466c-8226-304ec651f4ben%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1659 bytes --]
reply other threads:[~2025-10-03 8:58 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=ad14b140-9e02-466c-8226-304ec651f4ben@googlegroups.com \
--to=ueberspannung@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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