public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Thibaut Le Guilly <thibaut@cryptogarage•co.jp>
To: email@yancy•lol,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Cc: Prayank <prayank@tutanota•de>
Subject: Re: [bitcoin-dev] [Bitcoin Advent Calendar] Derivatives and Options
Date: Mon, 27 Dec 2021 21:05:36 +0900	[thread overview]
Message-ID: <CABPZDUxkjSRzCSh1ueq_ONAyc010QsxAshei4gQNpHO10Y31Lg@mail.gmail.com> (raw)
In-Reply-To: <86b6f138a9dbd2cd1dc4c9166199b319@yancy.lol>

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

Hi all,

Did someone say rust-dlc? Just kidding, but wanted to mention that indeed
it's under active development, supports multi oracle contracts and many
other cool things (pretty much everything you can find in the dlc specs)!

Otherwise nice article Jeremy. Maybe you should drop by our monthly DLC
spec meeting one of these days. I'm sure everybody would be happy to hear
how we could improve the Bitcoin derivatives ecosystem with CTV and what
infrastructures or code could be reused from DLCs.

Cheers,

Thibaut

On Mon, Dec 27, 2021 at 7:39 AM yancy via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> Prayank,
>
> I believe the p2pderivatives DLC application is still under active
> development here (single oracle):
> https://github.com/p2pderivatives/rust-dlc
>
> I was once involved in the project in a galaxy far far away but haven't
> kept up with the project.  Also, I'm a few days behind in the Bitcoin
> Advent Calendar :)
>
> Cheers,
> -Yancy
>
>
> On 2021-12-24 17:42, Prayank via bitcoin-dev wrote:
> > Hi Jeremy,
> >
> >> Wheres the info come from? Well, multiple places. We could get it
> > from a third party (maybe using an attestation chain of some sort?),
> > or there are certain ways it could be self-referential (like for
> > powswap [1]).
> >
> >> Now let’s define a threshold oracle – we wouldn’t want to
> > trust just one lousy oracle, so let’s trust M out of N of them!
> >
> > Similar approach is used in discreet log contracts for multi oracles.
> > There is even a project for P2P derivatives but it was not used for
> > any real trades on mainnet or further developed. What difference would
> > OP_CTV make in this project if its implemented in Bitcoin?
> >
> > https://github.com/p2pderivatives/p2pderivatives-client
> >
> > https://github.com/p2pderivatives/p2pderivatives-server
> >
> > https://github.com/p2pderivatives/p2pderivatives-oracle
> >
> >> Does this NEED CTV?
> >
> > No, not in particular. Most of this stuff could be done with online
> > signer server federation between you and counterparty. CTV makes some
> > stuff nicer though, and opens up new possibilities for opening these
> > contracts unilaterally.
> >
> > Nicer? How would unilateral derivatives work because my understanding
> > was that you always need a peer to take the other side of the trade. I
> > wish we could discuss this topic in a trading community with some
> > Bitcoiners that even had some programming knowledge.
> >
> > Derivatives are interesting and less explored or used in Bitcoin
> > projects. They could be useful in solving lot of problems.
> >
> > --
> >
> > Prayank
> >
> > A3B1 E430 2298 178F
> >
> >
> > Links:
> > ------
> > [1] https://powswap.com
> > _______________________________________________
> > 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
>

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

  reply	other threads:[~2021-12-27 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24 16:42 Prayank
2021-12-24 17:17 ` Jeremy
2021-12-26 20:49 ` email
2021-12-27 12:05   ` Thibaut Le Guilly [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-21  1:17 Jeremy

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=CABPZDUxkjSRzCSh1ueq_ONAyc010QsxAshei4gQNpHO10Y31Lg@mail.gmail.com \
    --to=thibaut@cryptogarage$(echo .)co.jp \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=email@yancy$(echo .)lol \
    --cc=prayank@tutanota$(echo .)de \
    /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