From: Chris Stewart <chris@suredbits•com>
To: Christian Decker via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [Annoucement] Discreet Log Contract Protocol Specification
Date: Mon, 13 Jan 2020 06:27:34 -0600 [thread overview]
Message-ID: <CAFQwNuz5YtpWZh7UF_b5zVz2gspMnWfdaMRdVhobZSq6pcxybQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
Hi all,
Suredbits and Crypto Garage have begun to work on a specification for
using discreet
log contracts <https://adiabat.github.io/dlc.pdf> in a safe, private and
interoperable way. We are writing to the mailing list to inform and solicit
feedback for the protocol specification so that we can -- as a community --
agree on a common standard to use Bitcoin oracles.
Our goal is to end up with a set of documents like the BIPs (Bitcoin
Improvement Proposals) and BOLTs (Basis of Lightning Technology) so that
others that wish to use the technology can easily write software to
integrate into the protocol.
A secondary goal of ours is to remain compatible with standards used by
other bitcoin related protocols (like Lightning) so that every future
bitcoin related protocol can reach for a “toolbox” of agreed standards for
things like funding transactions and closing transactions. We want to avoid
reinventing the wheel where possible and allow for library developers to
re-use software to hook into many bitcoin related protocols.
You can find the specification repository here:
https://github.com/discreetlogcontracts/dlcspecs/
For more information on DLCs:
[1] - https://adiabat.github.io/dlc.pdf
[2] - https://cryptogarage.co.jp/p2pd/
[3] -
https://suredbits.com/discreet-log-contracts-part-1-what-is-a-discreet-log-contract/
[4] -
https://blockstream.com/2019/04/19/en-transacting-bitcoin-based-p2p-derivatives/
[5] - https://dci.mit.edu/smart-contracts
-Chris
[-- Attachment #2: Type: text/html, Size: 7615 bytes --]
next reply other threads:[~2020-01-13 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 12:27 Chris Stewart [this message]
2020-01-28 9:28 ` Lloyd Fournier
2020-02-27 16:17 ` Nadav Kohen
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=CAFQwNuz5YtpWZh7UF_b5zVz2gspMnWfdaMRdVhobZSq6pcxybQ@mail.gmail.com \
--to=chris@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