From: Chris Stewart <chris@suredbits•com>
To: Christian Decker via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin-s 1.8 released with DLCs negotiation via Tor
Date: Mon, 18 Oct 2021 14:09:14 -0500 [thread overview]
Message-ID: <CAFQwNuzXYSDsGihP8KD5+jB0dYM3KLnDSAry--gy+hvNVDeWpw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Hi all,
We released 1.8 today of bitcoin-s. This includes support for opening DLCs
over tor. This makes the UX much simpler to enter into a DLC with your
counterparty.
As part of this release, we wrote two detailed examples of entering into
1. A wallet election example
<https://bitcoin-s.org/docs/next/wallet/wallet-election-example>
2. A wallet price example
<https://bitcoin-s.org/docs/next/wallet/wallet-price-example>
These are meant to complement the existing oracle examples we have
1. An election oracle example
<https://bitcoin-s.org/docs/next/oracle/oracle-election-example>
2. A price oracle example
<https://bitcoin-s.org/docs/next/oracle/oracle-price-example>
*This is alpha software, please do not use it for large amounts of money.*
You need a github account to access the downloads, the artifacts are at the
very bottom of the release notes.
https://github.com/bitcoin-s/bitcoin-s/releases/tag/1.8.0
You can find a demonstration video for using the wallet to enter into a DLC
over tor here:
https://www.youtube.com/watch?v=oR0I0aHxNMM
You can find the dlc spec here:
https://github.com/discreetlogcontracts/dlcspecs
-Chris
[-- Attachment #2: Type: text/html, Size: 1786 bytes --]
reply other threads:[~2021-10-18 19:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFQwNuzXYSDsGihP8KD5+jB0dYM3KLnDSAry--gy+hvNVDeWpw@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