Delivery-date: Fri, 03 Oct 2025 01:58:31 -0700
Sender: bitcoindev@googlegroups.com
Date: Fri, 3 Oct 2025 00:34:51 -0700 (PDT)
From: blocktraveler <ueberspannung@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <ad14b140-9e02-466c-8226-304ec651f4ben@googlegroups.com>
Subject: [bitcoindev] Add importprivkeys RPC
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_162502_1800324069.1759476891912"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_162502_1800324069.1759476891912
Content-Type: multipart/alternative; 
	boundary="----=_Part_162503_71230100.1759476891912"

------=_Part_162503_71230100.1759476891912
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


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=
=20
to import private keys (both legacy and Bech32/SegWit) into a Bitcoin Core=
=20
descriptor wallet. This issue is especially common in Namecoin. I see no=20
reason why importing private keys, a very basic feature, should be=20
restricted to the point that it's impossible for the average user to=20
succeed. That's why I created the Core-Wallet-Migration-Tools=20
<https://github.com/blocktraveler/Core-Wallet-Migration-Tools> in Python.

However, it would be much easier to have an 'importprivkeys' RPC for=20
descriptor wallets (not to be confused with the legacy 'importprivkey'=20
call). Pls check my initial thoughts:

Proposal: Add importprivkeys RPC (helper for WIF =E2=86=92 descriptor impor=
t)=20
<https://gist.github.com/blocktraveler/3e6198c698a272bd8b13b16e0f13d390>

Thx!
Uwe


--=20
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 e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
ad14b140-9e02-466c-8226-304ec651f4ben%40googlegroups.com.

------=_Part_162503_71230100.1759476891912
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<br />Hy there!<br /><br />Unfortunately, the PRs are locked, so I'm sharin=
g my thoughts this way.<br /><br />Over the years, people have asked countl=
ess times on various platforms how to import private keys (both legacy and =
Bech32/SegWit) into a Bitcoin Core descriptor wallet. This issue is especia=
lly 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 t=
he average user to succeed. That's why I created the <a href=3D"https://git=
hub.com/blocktraveler/Core-Wallet-Migration-Tools">Core-Wallet-Migration-To=
ols</a> in Python.<br /><br />However, it would be much easier to have an '=
importprivkeys'=C2=A0RPC for descriptor wallets (not to be confused with th=
e legacy 'importprivkey' call). Pls check my initial thoughts:<br /><br /><=
a href=3D"https://gist.github.com/blocktraveler/3e6198c698a272bd8b13b16e0f1=
3d390">Proposal: Add importprivkeys RPC (helper for WIF =E2=86=92 descripto=
r import)</a><br /><br />Thx!<br />Uwe<br /><br /><br />

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/ad14b140-9e02-466c-8226-304ec651f4ben%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/ad14b140-9e02-466c-8226-304ec651f4ben%40googlegroups.com</a>.<br />

------=_Part_162503_71230100.1759476891912--

------=_Part_162502_1800324069.1759476891912--