public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeremy Rubin <jeremy.l.rubin@gmail•com>
To: Lloyd Fournier <lloyd.fourn@gmail•com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Cc: dlc-dev@mailmanlists•org
Subject: Re: [bitcoin-dev] CTV dramatically improves DLCs
Date: Tue, 15 Mar 2022 10:28:05 -0700	[thread overview]
Message-ID: <CAD5xwhiMxGjLAkQAcyb8Fd3H1jBi+1+FmzWNoxD138A-nFC+Lw@mail.gmail.com> (raw)
In-Reply-To: <CAH5Bsr2vxL3FWXnJTszMQj83jTVdRvvuVpimEfY7JpFCyP1AZA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

I've created a prototype of this protocol in Sapio for your perusal:

https://github.com/sapio-lang/sapio/blob/master/sapio-contrib/src/contracts/derivatives/dlc.rs

Feel free to tweak the test and use it as a benchmark, i tested 1 oracle
with 100,000 different payouts and saw it take around 13s on a release
build.

I'll be playing around with this a bit (I doubt Sapio Studio can handle a
gui for 100,000 nodes), but I figured it was worth a share.

Cheers,

Jeremy

[-- Attachment #2: Type: text/html, Size: 1877 bytes --]

      parent reply	other threads:[~2022-03-15 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24  8:01 Lloyd Fournier
2022-01-25 16:24 ` [bitcoin-dev] [dlc-dev] " Jonas Nick
2022-01-27  0:45   ` Thibaut Le Guilly
2022-01-28 16:53     ` Jeremy
2022-01-28 17:21 ` [bitcoin-dev] " Jeremy
2022-01-28 19:38   ` Jeremy Rubin
2022-01-28 21:14   ` Alex Schoof
2022-02-06  7:18   ` Lloyd Fournier
2022-02-06 17:56     ` Jeremy Rubin
2022-02-07  2:30       ` Thibaut Le Guilly
2022-03-15 17:28 ` Jeremy Rubin [this message]

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=CAD5xwhiMxGjLAkQAcyb8Fd3H1jBi+1+FmzWNoxD138A-nFC+Lw@mail.gmail.com \
    --to=jeremy.l.rubin@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=dlc-dev@mailmanlists$(echo .)org \
    --cc=lloyd.fourn@gmail$(echo .)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