From: "James O'Beirne" <james.obeirne@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] CTV vaults in the wild
Date: Sun, 6 Mar 2022 12:35:17 -0500 [thread overview]
Message-ID: <CAPfvXfK4PckDdKG4aLASF4p-E8L8YyAbD8M3S_Zwk=wOuA0vfA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
A few months ago, AJ wrote[0]
> I'm not really convinced CTV is ready to start trying to deploy
> on mainnet even in the next six months; I'd much rather see some real
> third-party experimentation *somewhere* public first
In the spirit of real third-party experimentation *somewhere* in public,
I've created this implementation and write-up of a simple vault design
using CTV.
https://github.com/jamesob/simple-ctv-vault
I think it has a number of appealing characteristics for custody
operations at any size.
Regards,
James
[0]:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-February/019920.html
[-- Attachment #2: Type: text/html, Size: 906 bytes --]
next reply other threads:[~2022-03-06 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 17:35 James O'Beirne [this message]
2022-03-06 23:15 ` Antoine Riard
2022-03-08 0:57 ` ZmnSCPxj
2022-03-10 21:12 ` Antoine Riard
2022-03-08 19:46 ` James O'Beirne
2022-03-10 22:31 ` Antoine Riard
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='CAPfvXfK4PckDdKG4aLASF4p-E8L8YyAbD8M3S_Zwk=wOuA0vfA@mail.gmail.com' \
--to=james.obeirne@gmail$(echo .)com \
--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