public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Shannon Appelcline <shannon.appelcline@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Bitcoin Resilience Presentations — August 5
Date: Thu, 30 Jul 2026 16:00:13 -0700 (PDT)	[thread overview]
Message-ID: <c02e2f36-0e87-4968-8700-6b5a648a9397n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3100 bytes --]

Next Wednesday, August 5th at 10am PT, Blockchain Commons will host a 
Bitcoin-focused Gordian Developers Meeting about improving the protection 
of your secrets.

The general goal is to demonstrate how you can ensure the resilience of 
your Bitcoin Core–stored assets by integrating Bitcoin Core into the wider 
Bitcoin ecosystem. 

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 
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 
Your Bitcoin" and "Using Keylay to Securely Exchange Airgapped QRs". We 
think they'll both be of interest to the Bitcoin community & 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=rgVeDCgOKT3IMtBiISego4p5wK0s6F.1

Shannon Appelcline (that's me!), Lead Author of Learning Bitcoin from the 
Command Line, will present on *"Sharding Secrets to Protect Your Bitcoin"*. 
Currently, Bitcoin Core doesn't support a number of notable resilience 
features such as BIP-39 entropy or mnemonics, seed 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 importing an 
entropy-based descriptor into Bitcoin Core or exporting a master extended 
key from it. It'll also offer additional best practices on using metadata 
to ensure that you know what a secret is at some far future date when you 
recover it.

Stan Reeves, Professor Emeritus of ECE, Auburn University, will present on 
*Keylay*. BIP-129 standardized the multisig setup file format, but nothing 
standardizes how remote participants exchange it. In practice, xpubs, 
descriptors, and PSBTs move over email, messaging apps, or centralized 
coordinators, breaking air gaps and leaking metadata. Thie presentation 
will demonstrate a session-layer design for remote multisig coordination: 
ephemeral X25519 pairwise sessions with no accounts or persistent identity, 
a relay treated as adversarial (ciphertext only), air-gap bridging via 
BC-UR/BBQr animated QR, and pluggable transport targeting Nostr (websocket 
now, Nostr proposed). 

Shannon
Lead Tech Writer
Blockchain Commons

-- 
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/c02e2f36-0e87-4968-8700-6b5a648a9397n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3474 bytes --]

                 reply	other threads:[~2026-07-30 23:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c02e2f36-0e87-4968-8700-6b5a648a9397n@googlegroups.com \
    --to=shannon.appelcline@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