Return-Path: Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 9147BC0177 for ; Thu, 27 Feb 2020 16:23:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id 73DD3878C2 for ; Thu, 27 Feb 2020 16:23:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id timVKLqCESJa for ; Thu, 27 Feb 2020 16:23:15 +0000 (UTC) X-Greylist: delayed 00:05:17 by SQLgrey-1.7.6 Received: from mail-io1-f52.google.com (mail-io1-f52.google.com [209.85.166.52]) by whitealder.osuosl.org (Postfix) with ESMTPS id 5119C878A4 for ; Thu, 27 Feb 2020 16:23:15 +0000 (UTC) Received: by mail-io1-f52.google.com with SMTP id z1so56114iom.9 for ; Thu, 27 Feb 2020 08:23:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suredbits-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=zSVjG7uM4O2GezNNV16IULK24VR3GJZyTRQw1UqpE9g=; b=BIhFZYBtILaEN3zaIgr+G5e8/cxZBv7aiaZ2IZ8dfDpHjj/22L+nQXrtOy6YnWZDP6 iRy2reXVqP5K+pUyBlw4mohF198tkuKQyiL+b/P53NNPCUcrVsaQmuio/xpGjp4d6JMd 9qmAyvlt3qug1eV8opD9VFmFOW9nnFFEMlqyuHl+zBnaR/vd3FcV3S/7N/HPh80PEiEI sCSYFlIYjVQq2Cgqwn9//pF/QIq9Gi6392s0HpUv0ii1cIYi1ZoQ6Ey8qz8ob7kVjqyS 1jU+yXqZvxQAUyuKZwXtfBuqwRWIIqFf+gdrcrrgb6mGMfbmkP+qnW6jDJDa4hlB9RUn mU1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=zSVjG7uM4O2GezNNV16IULK24VR3GJZyTRQw1UqpE9g=; b=tMzHozJ/y+AscuQhZT+ua+hlXLyPpLHOaz/T99We7Ix1vQ/A6KbrAwl0WzoFZAimSZ x960wLQ9Y7YWP/EHGWTeCn5ahDMMUiGJIuh6txcEA8CZQI1SzhNWQ+0rAzSGePPj18ft 6CRXfuZDrL4GAX7co6Abvurbzt8dbSiVQsHzoxXd/VhxhHNIouIZjtqIHdAO97Law0h4 wZdT23XXJ5pVvTMa/jrcKphUFN+IusXnnUjy11uJNpzlunpdkWE8e0X7hc6PV7PGiqxP 02OZorl2FzZyp25QAQpp6uGxMk2pDNwgS4/o+hi2JN1YzAq/UPewlc2XFcZNAgNLUbEA 76WQ== X-Gm-Message-State: APjAAAXBsYDg7qkZdDCew2nzXBhxMj72IiTGP5EGntB2piDb59Ko2tYY K54Hfe7COBehluTvtxoHhV0eQbJfrw7gmVDDYcFTM4Q4MzLmYQ== X-Google-Smtp-Source: APXvYqzORDT59BzivbK4pX6EyhqDVonQzKb98tvIt7FfaopdVIzyYmpMZqhVmrCsmxPsDz212kH6TNchjH2cxCAgTAg= X-Received: by 2002:a5d:9593:: with SMTP id a19mr68156ioo.244.1582820277708; Thu, 27 Feb 2020 08:17:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Nadav Kohen Date: Thu, 27 Feb 2020 10:17:47 -0600 Message-ID: To: Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000657af4059f911027" X-Mailman-Approved-At: Thu, 27 Feb 2020 16:30:29 +0000 Subject: Re: [bitcoin-dev] [Annoucement] Discreet Log Contract Protocol Specification X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2020 16:23:16 -0000 --000000000000657af4059f911027 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi List, We now have have some working code for executing 2-outcome Discreet Log Contracts as well as documentation on how to use it, and would love if anyone wanted to try it out! Here's a short blog post with a video demo of an execution. And as always, we would also be thrilled if anyone interested in reviewing or contributing took a look at our work-in-progress specification . Best, Nadav On Tue, Jan 28, 2020 at 3:38 AM Lloyd Fournier via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Hi Chris, > > This is a really exciting effort. I hope I will be able to contribute to > it. I was wondering if you had seen the idea that DLCs can be done in onl= y > two transaction using Schnorr[1]. I also think this can be done in Bitcoi= n > as it is today using ECDSA adaptor signatures [2]. In my mind, the adapto= r > signature protocol is both easier to specify and implement on top of bein= g > cheaper and more private. > > LL > > [1] https://lists.launchpad.net/mimblewimble/msg00485.html > [2] > https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-November/0= 02316.html > > On Tue, Jan 14, 2020 at 2:12 AM Chris Stewart via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > >> Hi all, >> >> Suredbits and Crypto Garage have begun to work on a specification for >> using discreet log contracts 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 ca= n >> -- 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 =E2=80=9Ctoolbox=E2=80=9D of ag= reed standards for >> things like funding transactions and closing transactions. We want to av= oid >> 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-l= og-contract/ >> >> [4] - >> https://blockstream.com/2019/04/19/en-transacting-bitcoin-based-p2p-deri= vatives/ >> >> [5] - https://dci.mit.edu/smart-contracts >> >> -Chris >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >> > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000657af4059f911027 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi List,

We now have have some working = code for executing 2-outcome Discreet Log Contracts as well as=C2=A0documentation on = how to use it, and would love if anyone wanted to try it out!
Here's a short blog post with a video demo of an execution.=

And as always, we would also be thrilled if anyon= e interested in reviewing or contributing took a look at our work-in-progre= ss specificat= ion.

Best,
Nadav

On Tue, Jan 28= , 2020 at 3:38 AM Lloyd Fournier via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
Hi Chris,=C2=A0

This is a really exciting = effort. I hope I will be able to contribute to it. I was wondering if you h= ad seen the idea that DLCs can be done in only two transaction using Schnor= r[1]. I also think this can be done in Bitcoin as it is today using ECDSA a= daptor signatures [2]. In my mind, the adaptor signature protocol is both e= asier to specify=C2=A0and implement on top of being cheaper and more privat= e.

LL


On Tue, Jan 14,= 2020 at 2:12 AM Chris Stewart via bitcoin-dev <bitcoin-dev@lists.linuxf= oundation.org> wrote:

Hi all,=


Suredbits and Crypto Garage have begun to work on a specification for = using discreet log contracts in a safe, private = and interoperable way. We are writing to the mailing list to inform and sol= icit feedback for the protocol specification so that we can -- as a communi= ty -- agree on a common standard to use Bitcoin oracles.=C2=A0

Our goal= is to end up with a set of documents like the BIPs (Bitcoin Improvement Pr= oposals) and BOLTs (Basis of Lightning Technology) so that others that wish= to use the technology can easily write software to integrate into the prot= ocol.


A secondary goal of ours is to remain compatible with standards u= sed by other bitcoin related protocols (like Lightning) so that every futur= e bitcoin related protocol can reach for a =E2=80=9Ctoolbox=E2=80=9D of agr= eed standards for things like funding transactions and closing transactions= . We want to avoid reinventing the wheel where possible and allow for libra= ry developers to re-use software to hook into many bitcoin related protocol= s.=C2=A0


You can find the specification repository here:=C2=A0

https://github.com/discreetlogco= ntracts/dlcspecs/


For more information on DLCs:=C2=A0

[1] - https://adiabat.github.io/dlc.pdf=C2=A0

<= p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><= span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-= color:transparent;font-weight:400;font-style:normal;font-variant:normal;tex= t-decoration:none;vertical-align:baseline;white-space:pre-wrap">[2] - https://cryptogar= age.co.jp/p2pd/

[3] - https://suredbits.com/discreet-log-contracts-pa= rt-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

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000657af4059f911027--