From: blocktraveler <ueberspannung@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Add importprivkeys RPC
Date: Thu, 20 Aug 2026 21:10:36 -0700 (PDT) [thread overview]
Message-ID: <7051ea50-7b27-4540-a82f-527be9707f2dn@googlegroups.com> (raw)
In-Reply-To: <370fcce3-843d-4bcd-ac32-a6b157f7dc59n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 3996 bytes --]
ℹ️ Meanwhile, I changed the Core Wallet Migration Tools
<https://github.com/namecoin-dev/Core-Wallet-Migration-Tools> to
combo-import for more address type support (according to my original Proposal:
Add importprivkeys RPC
<https://gist.github.com/blocktraveler/3e6198c698a272bd8b13b16e0f13d390>).
Furthermore, I released the Core Wallet Maintenance Tools
<https://github.com/namecoin-dev/Core-Wallet-Maintenance-Tools/tree/main/Bitcoin>,
including a script for extracting private keys from descriptors. Created it
for Namecoin a while ago, but published it now on request
<https://github.com/namecoin-dev/Core-Wallet-Migration-Tools/issues/2> for
both, Bitcoin and Namecoin.
Regards,
Uwe
blocktraveler schrieb am Donnerstag, 23. Oktober 2025 um 04:00:02 UTC+2:
>
> Hy and thx for the feedback, much appreciated!
>
> * Regarding return scheme: Sure, redundant or competing returns should be
> unified. The question is, at which point the 'importprivkeys' call could
> just proxy or complement the return of the 'importdescriptors' routine.
>
> * Regarding checksum flag: Good point as well. Adding an 'auto_checksum'
> boolean to 'importdescriptors' would simplify things. Not sure if this has
> been discussed before or in case, what was the reason for not implementing
> it.
>
> Happy to address this in the proposal or the PR.
>
> Best regards,
> Uwe
>
>
>
> Email para newsletters schrieb am Mittwoch, 22. Oktober 2025 um 00:28:32
> UTC+2:
>
>> IMO thats a very good proposal and should be really easy to implement.
>>
>> Allow me to share some points.
>>
>> * The return scheme somewhat extends the one from the already existing
>> `importdescriptors`. This can be considered a corner to cut if theres
>> implementation burn.
>>
>> * I do not have any idea about others opinion but I consider a flaw to
>> not have a checksum induction flag in `importdescriptors`, which could
>> reduce `importprivkeys` command dependency as well extending them both.
>>
>> Best,
>> Joao Leal
>>
>> Em sexta-feira, 3 de outubro de 2025 às 05:58, blocktraveler <
>> uebers...@gmail.com> escreveu:
>>
>>
>> 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+...@googlegroups.com.
>> To view this discussion visit
>> https://groups.google.com/d/msgid/bitcoindev/ad14b140-9e02-466c-8226-304ec651f4ben%40googlegroups.com
>> .
>>
>>
>>
--
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/7051ea50-7b27-4540-a82f-527be9707f2dn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 6225 bytes --]
prev parent reply other threads:[~2026-08-24 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 7:34 [bitcoindev] Add importprivkeys RPC blocktraveler
2025-10-21 19:21 ` 'Email para newsletters' via Bitcoin Development Mailing List
2025-10-23 1:55 ` blocktraveler
2026-08-21 4:10 ` blocktraveler [this message]
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=7051ea50-7b27-4540-a82f-527be9707f2dn@googlegroups.com \
--to=ueberspannung@gmail.com \
--cc=bitcoindev@googlegroups.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