public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: jeremy <jeremy.l.rubin@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Un-FE’d Covenants: Char-ting a new path to Emulated Covenants via BitVM Integrity Checks
Date: Tue, 26 Nov 2024 19:05:35 -0800 (PST)	[thread overview]
Message-ID: <30440182-3d70-48c5-a01d-fad3c1e8048en@googlegroups.com> (raw)


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

Esteemed Bitcoin Developers,

Sharing below an approach to implementing Bitcoin covenants without 
requiring native protocol changes. The approach uses covenant emulators 
signing servers.

Unlike approaches to date for covenant emulation, the oracle signers put up 
bonds to BitVM auditors subject to a BITVM style fraud proof, whereby their 
funds can be stolen if the emulator oracle ever signs a transaction in 
violation of the covenant rules.
you can find the paper here: 
https://rubin.io/bitcoin/2024/11/26/unfed-covenants/

Regards,

Jeremy

-- 
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/30440182-3d70-48c5-a01d-fad3c1e8048en%40googlegroups.com.

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

                 reply	other threads:[~2024-11-27  3: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=30440182-3d70-48c5-a01d-fad3c1e8048en@googlegroups.com \
    --to=jeremy.l.rubin@gmail$(echo .)com \
    --cc=bitcoindev@googlegroups.com \
    /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