From: Jeremy <jlrubin@mit•edu>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [Bitcoin Advent Calendar] POWSWAP: Oracle Free Bitcoin Hashrate Derivatives
Date: Tue, 21 Dec 2021 16:25:04 -0800 [thread overview]
Message-ID: <CAD5xwhj6TT11Mg91wF_e5+CGa0ERFKOxYe08+PpNaaGkws04zQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Hi devs,
Today's post details how to make fully trustless hashrate derivative
contracts that can be embedded on-chain, inside of channels, options, or
inside of DCFMPs. These contracts can be used today without CTV, but they
obviously get better with CTV :)
enjoy: https://rubin.io/bitcoin/2021/12/21/advent-24/
I have not done any work to analyze the profitability of these contracts or
how you might price and risk them, or if a two sided market among miners
actually exists. That's not really my expertise.
But maybe someone can figure that out and let us all know :)
cheers,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 1574 bytes --]
reply other threads:[~2021-12-22 0:25 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=CAD5xwhj6TT11Mg91wF_e5+CGa0ERFKOxYe08+PpNaaGkws04zQ@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