From: Jeremy <jlrubin@mit•edu>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [Bitcoin Advent Calendar] Inheritance Schemes
Date: Wed, 8 Dec 2021 11:20:54 -0800 [thread overview]
Message-ID: <CAD5xwhjFxwgftr7ORa14MupWVaiqgoxHn16NR1vXH6K7ERghjA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
Devs,
For today's post, something near and dear to our hearts: giving our sats to
our loved ones after we kick the bucket.
see: https://rubin.io/bitcoin/2021/12/08/advent-11/
Some interesting primitives, hopefully enough to spark a discussion around
different inheritance schemes that might be useful.
One note I think is particularly discussion worthy is how the UTXO model
makes inheritance backups sort of fundamentally difficult to do v.s. a
monolithic account model.
Cheers,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 2295 bytes --]
reply other threads:[~2021-12-08 19:21 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=CAD5xwhjFxwgftr7ORa14MupWVaiqgoxHn16NR1vXH6K7ERghjA@mail.gmail.com \
--to=jlrubin@mit$(echo .)edu \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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