From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 24 Aug 2026 06:19:55 -0700 Received: from mail-yx1-f61.google.com ([74.125.224.61]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wyUag-0007Nr-O4 for bitcoindev@gnusha.org; Mon, 24 Aug 2026 06:19:55 -0700 Received: by mail-yx1-f61.google.com with SMTP id 956f58d0204a3-66c70fa2ba4sf2130955d50.2 for ; Mon, 24 Aug 2026 06:19:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1787577588; x=1788182388; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :sender:from:to:cc:subject:date:message-id:reply-to:content-type; bh=3lWL6wNX0YRBUq05pcStWICrwqGluMnq/mAu1x6K8xM=; b=yDMg2IBXa6+P7TsuhVzBye3ZabB3GhpXlmU4c8xOUlC80ZKRCoCXVuFaLemsqVpvh8 u+MrrkKBnhhetF5/H+dr3GRSEU0mYJ4p7i+5dV8qJyAN2ZSBocuo+zOQrFBUf3/ORy5n adjiWhZsiTn8GKAO79C0zXb1SYQNjCgwfvTKJmnRa+VMqXfGgPFFDntDW8uKbgPH8sps tPgtTVa3sq/Z8P7BR6v8Hdt2xgDYahcRZ/PqovrYCkG7yCZ2JB46M+P0OcseWg4SsA8N ctRdadggftOHyy/sWv333Xcjxr/vU0ZkmdoKHyvrU0vLeAovAUKHjQqeD86xLVPSVfO3 wQLg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1787577588; x=1788182388; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to:content-type; bh=3lWL6wNX0YRBUq05pcStWICrwqGluMnq/mAu1x6K8xM=; b=JYObRQ3v+uTu2yyHmerF6Wke0Kf89KqZ9rf1KaurGuJgAnONfDquIPYZciIY3fjwch eKpHeg/AQ2IcLt9b6IxJIB96MWQMFES4dTVWNWQPwxfjsilEi8+tbUTsTrDOxaA30JVQ qdS1pr3Xxfm0cD57zdgVYlQ5q+qjiVvTaV/tM3JuPFPsrXFkjbd1rLTMS6NEBRS/vf/3 9I00YuOwEdQXqES2QFk4uTWyyyVb6wPYMKrl6BOmqYTA1Rz71KTNbvVmSuY6CLAzFHc7 n41Y+Wt43xhS1hJ8SsNKZi7+JCggy4ZMKoj97iWxmbbHgJ7470DAsDWzJl3siMhfQBtc IlSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1787577588; x=1788182388; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :x-beenthere:x-gm-message-state:sender:from:to:cc:subject:date :message-id:reply-to:content-type; bh=3lWL6wNX0YRBUq05pcStWICrwqGluMnq/mAu1x6K8xM=; b=MeaAANyul7disfmqG9BPv8zOgFsQ19j1KV1WiWqHY1NUfOwqNBsAxKGCH27rzIx641 rnokpnA/JPH/1GfBH9YUFwg3H19bFKMCLiyKkPAWbAmBK//Qy0tLSP9XegQ6J9eqdJvz fmhSybVm/GCJ+fjjKNTyaYMzrDl+cC/6pYZICtK9OzFI7Ae+gkJcdP5XgYwZtPodKOwr HmtelNyjUtxVjO1NpgApza1vyTF14EE7AQk4D4Cz///WG+SUHOtsaKJdnIFULBRogj8p MDm6DfDTZQlqgLCVxuUIg+tcZok/piKQxTB7pDDbqN5U8yJF7FxrdQgoB161GK0enpTS +Tbg== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AHgh+RopqnY8dvYMeqECVChAkyH/rs3AXVtqQ+1/Jn4eimXlrFmSPQ3eNibJA9FA/gOORQRUd/nqEvCBR+rv@gnusha.org X-Gm-Message-State: AFuF++lgOD13ICd5KNsLaanXRyIdC48gkuDa20wEHPHdZY2PevVXZaA6 rjgut51pxCSCVmkrV0LfaL6Uf2XcOlXlZN4LetTzFGULp3+6Nb9HFrY8 X-Received: by 2002:a05:690e:80f:20b0:66c:b671:e1a6 with SMTP id 956f58d0204a3-66cf2172d5emr4412527d50.18.1787577588204; Mon, 24 Aug 2026 06:19:48 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="ATskLddKY7r0o/IX7h43HKcJqdwObo5vUFaV7oaho8Hk2B6ipA==" Received: by 2002:a53:4901:0:b0:668:17dd:4bd2 with SMTP id 956f58d0204a3-66d09233b5cls882115d50.0.-pod-prod-04-us; Mon, 24 Aug 2026 06:19:42 -0700 (PDT) X-Received: by 2002:a05:690c:c625:b0:81e:8577:d044 with SMTP id 00721157ae682-84c9c1a900cmr49481767b3.35.1787577582466; Mon, 24 Aug 2026 06:19:42 -0700 (PDT) Received: by 2002:a05:690c:e192:20b0:844:b608:e8f7 with SMTP id 00721157ae682-84a7ddc1b02ms7b3; Thu, 20 Aug 2026 21:10:37 -0700 (PDT) X-Received: by 2002:a05:690c:e3cd:b0:81e:b981:3eb5 with SMTP id 00721157ae682-849f449e26dmr13530757b3.23.1787285437092; Thu, 20 Aug 2026 21:10:37 -0700 (PDT) Date: Thu, 20 Aug 2026 21:10:36 -0700 (PDT) From: blocktraveler To: Bitcoin Development Mailing List Message-Id: <7051ea50-7b27-4540-a82f-527be9707f2dn@googlegroups.com> In-Reply-To: <370fcce3-843d-4bcd-ac32-a6b157f7dc59n@googlegroups.com> References: <370fcce3-843d-4bcd-ac32-a6b157f7dc59n@googlegroups.com> Subject: Re: [bitcoindev] Add importprivkeys RPC MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_59742_1518977972.1787285436776" X-Original-Sender: ueberspannung@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_59742_1518977972.1787285436776 Content-Type: multipart/alternative; boundary="----=_Part_59743_567017031.1787285436776" ------=_Part_59743_567017031.1787285436776 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =E2=84=B9=EF=B8=8F Meanwhile, I changed the Core Wallet Migration Tools=20 to=20 combo-import for more address type support (according to my original Propos= al:=20 Add importprivkeys RPC=20 ). Furthermore, I released the Core Wallet Maintenance Tools=20 ,=20 including a script for extracting private keys from descriptors. Created it= =20 for Namecoin a while ago, but published it now on request=20 for= =20 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= =20 > unified. The question is, at which point the 'importprivkeys' call could= =20 > just proxy or complement the return of the 'importdescriptors' routine. > > * Regarding checksum flag: Good point as well. Adding an 'auto_checksum'= =20 > boolean to 'importdescriptors' would simplify things. Not sure if this ha= s=20 > been discussed before or in case, what was the reason for not implementin= g=20 > 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= =20 > 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= =20 >> `importdescriptors`. This can be considered a corner to cut if theres=20 >> implementation burn. >> >> * I do not have any idea about others opinion but I consider a flaw to= =20 >> not have a checksum induction flag in `importdescriptors`, which could= =20 >> reduce `importprivkeys` command dependency as well extending them both. >> >> Best, >> Joao Leal >> >> Em sexta-feira, 3 de outubro de 2025 =C3=A0s 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= =20 >> how to import private keys (both legacy and Bech32/SegWit) into a Bitcoi= n=20 >> Core descriptor wallet. This issue is especially common in Namecoin. I s= ee=20 >> no 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 >> 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 im= port)=20 >> >> >> Thx! >> Uwe >> >> >> --=20 >> You received this message because you are subscribed to the Google Group= s=20 >> "Bitcoin Development Mailing List" group. >> To unsubscribe from this group and stop receiving emails from it, send a= n=20 >> email to bitcoindev+...@googlegroups.com. >> To view this discussion visit=20 >> https://groups.google.com/d/msgid/bitcoindev/ad14b140-9e02-466c-8226-304= ec651f4ben%40googlegroups.com >> . >> >> >> --=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/= 7051ea50-7b27-4540-a82f-527be9707f2dn%40googlegroups.com. ------=_Part_59743_567017031.1787285436776 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=E2=84=B9=EF=B8=8F Meanwhile, I changed the Core Wallet Migration = Tools to combo-import for more address type support (according to my or= iginal Proposal: Add importprivkeys RPC).

Furthermor= e, I released the Core Wallet Maintenance Tools, inclu= ding a script for extracting private keys from descriptors. Created it for = Namecoin a while ago, but published it now on request for both, B= itcoin and Namecoin.

Regards,
Uwe



blocktravel= er schrieb am Donnerstag, 23. Oktober 2025 um 04:00:02 UTC+2:

Hy and thx for the fee= dback, 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.

*=C2=A0Regarding checksum = flag: Good point as well. Adding an 'auto_checksum' boolean to '= ;importdescriptors' would simplify things. Not sure if this has been di= scussed 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 th= ats a very good proposal and should be really easy to implement.

Allow me to share some points.

* The return sche= me 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 c= ould reduce `importprivkeys` command dependency as well extending them both= .

Best,
Joao Leal

=20
=20
=20

<= /div>
Em sexta-feira, 3 de outubro de 2025 =C3=A0s 05:58, blocktraveler &= lt;uebers...@gmail.com> escreveu:

Hy there!

Unfortunately, the PRs are locked, so I= 9;m sharing my thoughts this way.

Over the years, people have asked = countless times on various platforms how to import private keys (both legac= y and Bech32/SegWit) into a Bitcoin Core descriptor wallet. This issue is e= specially common in Namecoin. I see no reason why importing private keys, a= very basic feature, should be restricted to the point that it's imposs= ible for the average user to succeed. That's why I created the Core-Wallet-Migration-Tools in Pytho= n.

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

Proposal: Add importprivkey= s RPC (helper for WIF =E2=86=92 descriptor import)

Thx!
Uwe

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail 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 &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/7051ea50-7b27-4540-a82f-527be9707f2dn%40googlegroups.com.
------=_Part_59743_567017031.1787285436776-- ------=_Part_59742_1518977972.1787285436776--