From: Nadav Kohen <nadav@suredbits•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Update on DLCs (new mailing list)
Date: Mon, 25 Jan 2021 16:17:36 -0600 [thread overview]
Message-ID: <CALGTLwMwja3Jj8imfEeqZU8h9R3oSDuqn9L7xCFHQKeEO6L7mg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
Hi all,
A Discreet Log Contract (DLC) is a Bitcoin-compatible oracle contract
enabling transactions to be contingent on signatures broadcasted by some
set of oblivious oracles. This scheme is a contracting building block that
enables a variety of applications such as disintermediated betting,
hedging, financial contracts, and even such things as synthetic assets.
I am excited to announce that there is now a dlc-dev mailing list (
https://mailmanlists.org/mailman/listinfo/dlc-dev) for anyone who wants to
follow or participate in work related to Discreet Log Contracts! Here is
the repository which has links to many resources including blog posts and
the white paper: https://github.com/discreetlogcontracts/dlcspecs.
We also have monthly specification meetings on the first Tuesday of every
month, if you are interested in attending and do not have an invite feel
free to reach out.
In case you haven't been following recent progress in DLCs, here's a quick
(incomplete) list of updates:
* We are using ECDSA Adaptor signatures, soon to be PR'd to secp256k1-zkp:
https://github.com/discreetlogcontracts/dlcspecs/pull/114.
* We have defined TLV-serializations for messages (like Lightning) required
to set up DLCs between parties (including messages from oracles).
* We have multiple compatible DLC implementations.
* We have specified (and implemented) compression algorithms which make
DLCs that are contingent on numeric outcomes (such as prices) practical and
expressive enough to support any payout curve.
* We have specified (and implemented) algorithms which allow users to use a
threshold t-of-n oracles, even supporting numeric cases where some bounded
difference is permitted between oracles.
* We are aiming to have a more stable v0 tag/release of the specification
in a few months!
Best,
Nadav Kohen
[-- Attachment #2: Type: text/html, Size: 2245 bytes --]
reply other threads:[~2021-01-25 22:24 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=CALGTLwMwja3Jj8imfEeqZU8h9R3oSDuqn9L7xCFHQKeEO6L7mg@mail.gmail.com \
--to=nadav@suredbits$(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