From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 22 Oct 2025 19:00:09 -0700 Received: from mail-oa1-f59.google.com ([209.85.160.59]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1vBkca-0000e2-UP for bitcoindev@gnusha.org; Wed, 22 Oct 2025 19:00:09 -0700 Received: by mail-oa1-f59.google.com with SMTP id 586e51a60fabf-34c14f3b822sf851491fac.1 for ; Wed, 22 Oct 2025 19:00:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1761184802; x=1761789602; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=3cKhniRgkernzkwYB2bOm9a83DAxwGsbcrmKYVrHCzU=; b=MxlBOHSln3d1sL+ITbNGXEcdWbznTAG1mDnyxqqrgpY3/rVqxYgAFKo9ujIIydW3lR N0W1k7y7AnLY+vY/ZCHF8/p+TP4HzU0B3q5DEVpB++e0Y/Bllzm7PxnZp9WbOi22F0vX UGjSu1x+hdghDfz5zEm5SFzZbtVb+ax0sEjbrT5FQi8B3f4alsfarlg85A/tDIjKChiE GGR5FpAuLRg5BoMOQclqHnN8I69f/PILNrlMiS51YE8W85ebw8ooLXgMqeFgn5QYpeXp FVQZD65vKCmDBB/1xrnSzdNpWzN0ZtORiEPgqqVUz7Xa+hLdlJaqRMEbdXyxntYud+bm 19gw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1761184802; x=1761789602; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=3cKhniRgkernzkwYB2bOm9a83DAxwGsbcrmKYVrHCzU=; b=TRCGCbr6vXsXJIBY3xzM7Igmq0OEKjJ5VoA72M2VB24/qgpOVMDOyk6j3I5+zXKV49 12g1o9FKQyayKmH81ZuC+3KCoMPLw59Zmqshg4z2naP64VqqKTMmKeBs3Q3ldm8rBN9D iTJQRT5qR+/TWyMGM89/NvhhEVLKteaDl687vnx34jkyBiafl911SVpS7UpmKn3TnlIt GMOsFSkn65Nx3HilZFtL9j7vYfo/F8rzlIFwy7CK34+ni2YEgHt9O7+qpvbvxdMxY1Uy 8e9+U/eKeHRum6PnMkTpoHOJ2zpKgkrY+yf1+fNdT+1QO55pTh1inXRoqGhLwqxfDUvH FnXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761184802; x=1761789602; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender: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; bh=3cKhniRgkernzkwYB2bOm9a83DAxwGsbcrmKYVrHCzU=; b=KHfouLVUYSfWLkG3ElscGgGbR7ETUgN1ue9Z+FE/Kyz/i/WyqcOjEDpZdptP2NgQ8E gqRjhv1kgJUszY2WoqeKNWSJAKyaWnVgqprnbILDBBzP3nioxDPOjnCQxydl2d4C4+nS uGgn58xBLhVLR+Tw9+MSn9cG5jsqzeWqvHPyufB3WsaXkxWVW6ftCjfuG7mAimrnR2AX nkmo3u7JhkgMBY14PDRobyiaNQk+Xcs/liUTrnW2X/QPXppFP34Rgaicfhn0ipjaCakR 09ds8CtRDHrDuObJE7mettgk01Cktj0kixh8jwqdsQUr78H2AU5nML3dnxOUOeT+yfeO PavA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWDQg+ixz39k8xDzkjz5/9JVlJ5AoLZDpOn73gq8KJr9pni/SuVQGB29wKYDL57TIQJNe2+8BoFceuk@gnusha.org X-Gm-Message-State: AOJu0Yxu8n9RRN2piXQI4pIjtQwXS/LXrPb5f91MMUum98d9KNKixw6e E/BWvLc8G6HjXA11opDYXlup0H0hg04FrEd2KHI+9dD/smXj+bYjJQnT X-Google-Smtp-Source: AGHT+IGwJd0URJk82K0J04hUYvgBBfxkgbhxA6kAyPvHR17V+Feb4rj3mS2AEi1XcBOm4VRkij+1jw== X-Received: by 2002:a05:6870:a990:b0:36c:abe0:83d3 with SMTP id 586e51a60fabf-3c98d13ab47mr9393712fac.39.1761184802202; Wed, 22 Oct 2025 19:00:02 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="ARHlJd5XjZ7vMjZQK++di3mQ/SQiyO122GGceOP7cVDo2a5vmg==" Received: by 2002:a05:6871:5226:b0:3c9:a01c:15c2 with SMTP id 586e51a60fabf-3cdc67f82eals57609fac.2.-pod-prod-02-us; Wed, 22 Oct 2025 18:59:57 -0700 (PDT) X-Received: by 2002:a05:6808:18a7:b0:438:8ad:16b9 with SMTP id 5614622812f47-443a30d1062mr8339714b6e.32.1761184797255; Wed, 22 Oct 2025 18:59:57 -0700 (PDT) Received: by 2002:a05:690c:a96:b0:780:f7eb:fdf with SMTP id 00721157ae682-785bdcaff52ms7b3; Wed, 22 Oct 2025 18:55:18 -0700 (PDT) X-Received: by 2002:a05:690c:608a:b0:785:c770:fd97 with SMTP id 00721157ae682-785c7710004mr27877757b3.69.1761184517589; Wed, 22 Oct 2025 18:55:17 -0700 (PDT) Date: Wed, 22 Oct 2025 18:55:17 -0700 (PDT) From: blocktraveler To: Bitcoin Development Mailing List Message-Id: <370fcce3-843d-4bcd-ac32-a6b157f7dc59n@googlegroups.com> In-Reply-To: References: Subject: Re: [bitcoindev] Add importprivkeys RPC MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_192228_792375319.1761184517314" 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_192228_792375319.1761184517314 Content-Type: multipart/alternative; boundary="----=_Part_192229_1105003820.1761184517314" ------=_Part_192229_1105003820.1761184517314 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 has= =20 been discussed before or in case, what was the reason for not implementing= =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 no= t=20 > have a checksum induction flag in `importdescriptors`, which could reduce= =20 > `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 ho= w=20 > to import private keys (both legacy and Bech32/SegWit) into a Bitcoin Cor= e=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 > 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 imp= ort)=20 > > > Thx! > Uwe > > > --=20 > You received this message because you are subscribed to the Google Groups= =20 > "Bitcoin Development Mailing List" group. > To unsubscribe from this group and stop receiving emails from it, send an= =20 > email to bitcoindev+...@googlegroups.com. > To view this discussion visit=20 > https://groups.google.com/d/msgid/bitcoindev/ad14b140-9e02-466c-8226-304e= c651f4ben%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/= 370fcce3-843d-4bcd-ac32-a6b157f7dc59n%40googlegroups.com. ------=_Part_192229_1105003820.1761184517314 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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.

*=C2= =A0Regarding checksum flag: Good point as well. Adding an 'auto_checksum' b= oolean to 'importdescriptors' would simplify things. Not sure if this has b= een discussed before or in case, what was the reason for not implementing i= t.

Happy to address this in the proposal or the PR.

B= est regards,
Uwe



Email para newsletters schrieb am Mittw= och, 22. Oktober 2025 um 00:28:32 UTC+2:

IMO thats a very good proposal and should be rea= lly easy to implement.

Allow me to share some points.

=

* The return scheme somewhat extends the one from the alread= y existing `importdescriptors`. This can be considered a corner to cut if t= heres 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 depend= ency 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> e= screveu:

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 bitc= oindev+...@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/370fcce3-843d-4bcd-ac32-a6b157f7dc59n%40googlegroups.com.
------=_Part_192229_1105003820.1761184517314-- ------=_Part_192228_792375319.1761184517314--