From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 04 Aug 2026 13:03:38 -0700 Received: from mail-oa1-f56.google.com ([209.85.160.56]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wrLMP-0002V9-Sl for bitcoindev@gnusha.org; Tue, 04 Aug 2026 13:03:38 -0700 Received: by mail-oa1-f56.google.com with SMTP id 586e51a60fabf-4583ab9a376sf148158fac.0 for ; Tue, 04 Aug 2026 13:03:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1785873811; x=1786478611; 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=Ue0XIR2ooh2JXN9VB28c9tfIpGe6UE5KhKkWzZsNdlg=; b=MxLoww/w87ZV28PYyVYGK980IrB4rXUm55/4CE4wyGfFhKALFlC4SmePVHLl2nTS8i ac6os5ejJoAnsxAnVpxm0GzwxXD2r5V3ccgOje6M/Uw3gIEMyB2JIj15o4tb0qf5yND2 i7fttFTdvPVKAVmd1GPzUd5XkxOkPFYbdqFWYw8dVWl9nk2oyIuFtx8sYTb/Umb7bTS4 +mBjtYM4iqk4ypHW8mM2SasA03f0cq1bRCNKnLujEEnI0UTDsg1yd2/Hj2fw5leDgwCe vLae9yUfPklLk1AZiyY7cgOCUBPiWJA2IAprzpiadXd8zM4dQsUsy1aNoxn2rOGDWK6Y qaUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1785873811; x=1786478611; 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=Ue0XIR2ooh2JXN9VB28c9tfIpGe6UE5KhKkWzZsNdlg=; b=RZ3/97nShzZU5LqTJauXXj4H4LSLHw6arMCJKaYpr5d+eGKeQ6crSr07/rNYRfyEus zTTZAaNBcfx0WewcCLsum1J+kxGqBIitn36v793y2dtVpNOFAr5NS6J0P8CTb+8Bws2/ 4TVfKzrFc0PfkfEv2pdv3npwqIpsYUnN2TivK2tHgaZINRM89KjalpkMFK6swIQ/nN6A vGDVwLxSNPiUDqSkXmDuFKbzDXeFv63b6WSxRyaajqZwSrceOrP4qQOGIZRd18//ZsMb KKQwSb8vwGxy4DgNdIsxfvWKsQM3tIYzgTUGLe5rcH5gDg2r0DxVOobt7DJX9PWHHvy5 KhJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785873811; x=1786478611; 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=Ue0XIR2ooh2JXN9VB28c9tfIpGe6UE5KhKkWzZsNdlg=; b=c4CHc597VLUQrFFwpgrNf0CaWgiNNDOzULW91I0RUOIG3B/YL+56VI0S1bPhEsGExS SPZ2Zdbbg9Rm4xxA8knnDQsKhD3KNFopCJN1uE+yBmBHQmwcSokJkD4gKCSESYWonVy6 fzx44MXNrz1sqwUVeW1TfUjm6lzJQX244wFBcpRYTnmD5flTgRUWaDV4fhvdhpf4xRkY +UDvJFkRDjjMYj9XHVSeABxMMlUszV9NGBu6usTqyJbtrRCY+Rmc5Qi/QHk8nERWp8Mk iF/6s6X0sRLbe8omOMzWHhhHWGXxkKo1EF4IqIiaZyIHGnECtIByk3JLvIh8sZyz+ycz BAWQ== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AHgh+Rr2bngQYbhajUsMvNqohWD9faxV8ltAr3cOdUia40Kv91ZnlQuoSylgE2zOEJKaAsCYfAjIpnVTB+KI@gnusha.org X-Gm-Message-State: AOJu0YzTc8zGgsS5TJRK2XP6EukleQk3m3261gxK2z+YWnK3/TPjP7Lk gYbOyrRXhB/IvfSBRuFxcYGA3shtCnok3xEX7ySJhbbS4S2EG/JgVQKW X-Received: by 2002:a05:6820:81d5:b0:6a1:7dcb:b9fc with SMTP id 006d021491bc7-6ae9706e2fcmr859506eaf.34.1785873811451; Tue, 04 Aug 2026 13:03:31 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="Aa7YSPSFWgWBFu9K/Ej6dTrqj5l+k9noR7pzBQ5VB5xqoK7TPA==" Received: by 2002:a05:6820:8590:10b0:6ae:98bc:10e0 with SMTP id 006d021491bc7-6ae98bc49a7ls52059eaf.2.-pod-prod-05-us; Tue, 04 Aug 2026 13:03:16 -0700 (PDT) X-Received: by 2002:a05:6808:1646:b0:496:559d:5474 with SMTP id 5614622812f47-4afadfb0140mr620067b6e.8.1785873796593; Tue, 04 Aug 2026 13:03:16 -0700 (PDT) Received: by 2002:a05:690c:610b:b0:81e:11b4:1172 with SMTP id 00721157ae682-81fc4a84b17ms7b3; Tue, 4 Aug 2026 12:56:33 -0700 (PDT) X-Received: by 2002:a05:690c:c4ea:b0:814:608a:a2f7 with SMTP id 00721157ae682-82022630dc8mr6048147b3.25.1785873392202; Tue, 04 Aug 2026 12:56:32 -0700 (PDT) Date: Tue, 4 Aug 2026 12:56:31 -0700 (PDT) From: Shannon Appelcline To: Bitcoin Development Mailing List Message-Id: <76b22b7a-cc05-4d5d-8664-84f8c916e3ccn@googlegroups.com> In-Reply-To: References: Subject: =?UTF-8?Q?=5Bbitcoindev=5D_Re=3A_Bitcoin_Resilience_Presentations_?= =?UTF-8?Q?=E2=80=94_August_5?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_13784_617520386.1785873391760" X-Original-Sender: Shannon.Appelcline@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_13784_617520386.1785873391760 Content-Type: multipart/alternative; boundary="----=_Part_13785_693580652.1785873391760" ------=_Part_13785_693580652.1785873391760 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Folks, Just a reminder that this presentation is tomorrow: WHAT? Securing Your Bitcoin with Entropy, Seeds, Shards, Airgaps, and More WHEN? August 5th, 10am PT WHERE?=20 https://us02web.zoom.us/j/88143195571?pwd=3DrgVeDCgOKT3IMtBiISego4p5wK0s6F.= 1 The Coldcard seed-creation failure revealed over the weekend definitely=20 showed off one of the many ways that self-sovereign controlled funds can be= =20 vulnerable. Some of the techniques that I plan to talk about tomorrow help= =20 you to control the fallout of that sort of failure by maintaining good=20 metadata that records where a seed or key originated from. Hope to see you there. Shannon On Thursday, July 30, 2026 at 1:40:45=E2=80=AFPM UTC-10 Shannon Appelcline = wrote: > Next Wednesday, August 5th at 10am PT, Blockchain Commons will host a=20 > Bitcoin-focused Gordian Developers Meeting about improving the protection= =20 > of your secrets. > > The general goal is to demonstrate how you can ensure the resilience of= =20 > your Bitcoin Core=E2=80=93stored assets by integrating Bitcoin Core into = the wider=20 > Bitcoin ecosystem.=20 > > We will demonstrate how to: > * Export descriptors from Bitcoin Core. > * Export extended private keys from Bitcoin Core. > * Use Shamir's Secret Sharing & metadata to store & protect that exported= =20 > data. > > Also: > * Create a BIP-39 secret remotely. > * Shard that secret. > * Import descriptors derived from the BIP-39 secret into Bitcoin Core. > > Finally: > * Exchange QRs for all of the above (and more) securely on the internet > > This will be done through two presentations: "Sharding Secrets to Protect= =20 > Your Bitcoin" and "Using Keylay to Securely Exchange Airgapped QRs". We= =20 > think they'll both be of interest to the Bitcoin community & we invite yo= u=20 > to attend! > > WHAT? Securing Your Bitcoin with Entropy, Seeds, Shards, Airgaps, and Mor= e > > WHEN? August 5th, 10am PT > > WHERE?=20 > https://us02web.zoom.us/j/88143195571?pwd=3DrgVeDCgOKT3IMtBiISego4p5wK0s6= F.1 > > Shannon Appelcline (that's me!), Lead Author of Learning Bitcoin from the= =20 > Command Line, will present on *"Sharding Secrets to Protect Your Bitcoin"= *.=20 > Currently, Bitcoin Core doesn't support a number of notable resilience=20 > features such as BIP-39 entropy or mnemonics, seed import, or Shamir's=20 > Secret Sharing. This presentation will talk about the difference between= =20 > BIP-32 and BIP-39 before demonstrating how to make use of all of these=20 > features while working with Bitcoin Core, either by importing an=20 > entropy-based descriptor into Bitcoin Core or exporting a master extended= =20 > key from it. It'll also offer additional best practices on using metadata= =20 > to ensure that you know what a secret is at some far future date when you= =20 > recover it. > > Stan Reeves, Professor Emeritus of ECE, Auburn University, will present o= n=20 > *Keylay*. BIP-129 standardized the multisig setup file format, but=20 > nothing standardizes how remote participants exchange it. In practice,=20 > xpubs, descriptors, and PSBTs move over email, messaging apps, or=20 > centralized coordinators, breaking air gaps and leaking metadata. Thie=20 > presentation will demonstrate a session-layer design for remote multisig= =20 > coordination: ephemeral X25519 pairwise sessions with no accounts or=20 > persistent identity, a relay treated as adversarial (ciphertext only),=20 > air-gap bridging via BC-UR/BBQr animated QR, and pluggable transport=20 > targeting Nostr (websocket now, Nostr proposed).=20 > > Shannon > Lead Tech Writer > Blockchain Commons > --=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/= 76b22b7a-cc05-4d5d-8664-84f8c916e3ccn%40googlegroups.com. ------=_Part_13785_693580652.1785873391760 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Folks,

Just a reminder that this presentation is t= omorrow:

WHAT? Securing Your Bitcoin with Entropy, Seeds, Shards= , Airgaps, and More
WHEN? August 5th, 10am PT
WHERE?=C2=A0https://us02web.zoom.us/j/88143195571?pwd=3DrgVeDCgOKT3IMtBiISego4p5wK0s= 6F.1

The Coldcard seed-creation failure revealed = over the weekend definitely showed off one of the many ways that self-sover= eign controlled funds can be vulnerable. Some of the techniques that I plan= to talk about tomorrow help you to control the fallout of that sort of fai= lure by maintaining good metadata that records where a seed or key originat= ed from.

Hope to see you there.

Shann= on

On Thursday, July 30, 2026 at 1:40:45=E2=80=AFPM UTC-10 Sha= nnon Appelcline wrote:
Next Wednesday, August 5th at 10am PT, Blockchain Commons will ho= st a Bitcoin-focused Gordian Developers Meeting about improving the protect= ion of your secrets.

The general goal is to demonstrate how you can = ensure the resilience of your Bitcoin Core=E2=80=93stored assets by integra= ting Bitcoin Core into the wider Bitcoin ecosystem.

We will demonst= rate how to:
* Export descriptors from Bitcoin Core.
* Export extende= d private keys from Bitcoin Core.
* Use Shamir's Secret Sharing &= ; metadata to store & protect that exported data.

Also:
* Cre= ate a BIP-39 secret remotely.
* Shard that secret.
* Import descripto= rs derived from the BIP-39 secret into Bitcoin Core.

Finally:
* E= xchange QRs for all of the above (and more) securely on the internet
This will be done through two presentations: "Sharding Secrets to Pro= tect Your Bitcoin" and "Using Keylay to Securely Exchange Airgapp= ed QRs". We think they'll both be of interest to the Bitcoin commu= nity & we invite you to attend!

WHAT? Securing Your Bitcoin with= Entropy, Seeds, Shards, Airgaps, and More

WHEN? August 5th, 10am PT=

WHERE? https:= //us02web.zoom.us/j/88143195571?pwd=3DrgVeDCgOKT3IMtBiISego4p5wK0s6F.1<= br>
Shannon Appelcline (that's me!), Lead Author of Learning Bitcoin= from the Command Line, will present on "Sharding Secrets to Protec= t Your Bitcoin". Currently, Bitcoin Core doesn't support a num= ber of notable resilience features such as BIP-39 entropy or mnemonics, see= d import, or Shamir's Secret Sharing. This presentation will talk about= the difference between BIP-32 and BIP-39 before demonstrating how to make = use of all of these features while working with Bitcoin Core, either by imp= orting an entropy-based descriptor into Bitcoin Core or exporting a master = extended key from it. It'll also offer additional best practices on usi= ng metadata to ensure that you know what a secret is at some far future dat= e when you recover it.

Stan Reeves, Professor Emeritus of ECE, Aubur= n University, will present on Keylay. BIP-129 standardized the multi= sig setup file format, but nothing standardizes how remote participants exc= hange it. In practice, xpubs, descriptors, and PSBTs move over email, messa= ging apps, or centralized coordinators, breaking air gaps and leaking metad= ata. Thie presentation will demonstrate a session-layer design for remote m= ultisig coordination: ephemeral X25519 pairwise sessions with no accounts o= r persistent identity, a relay treated as adversarial (ciphertext only), ai= r-gap bridging via BC-UR/BBQr animated QR, and pluggable transport targetin= g Nostr (websocket now, Nostr proposed).=C2=A0

Shannon
Lead Tech Writer
Blockchain Commons

--
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/76b22b7a-cc05-4d5d-8664-84f8c916e3ccn%40googlegroups.com.
------=_Part_13785_693580652.1785873391760-- ------=_Part_13784_617520386.1785873391760--