public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: email@yancy.lol
To: Prayank <prayank@tutanota.de>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin Advent Calendar] Derivatives and Options
Date: Sun, 26 Dec 2021 21:49:30 +0100	[thread overview]
Message-ID: <86b6f138a9dbd2cd1dc4c9166199b319@yancy.lol> (raw)
In-Reply-To: <MrhJf_p--3-2@tutanota.de>

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


  parent reply	other threads:[~2021-12-26 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24 16:42 [bitcoin-dev] [Bitcoin Advent Calendar] Derivatives and Options Prayank
2021-12-24 17:17 ` Jeremy
2021-12-26 20:49 ` email [this message]
2021-12-27 12:05   ` Thibaut Le Guilly
  -- 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=86b6f138a9dbd2cd1dc4c9166199b319@yancy.lol \
    --to=email@yancy.lol \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=prayank@tutanota.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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