From: Antoine Riard <antoine.riard@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Civ Kit: A Peer-to-Peer Electronic Market System
Date: Thu, 13 Apr 2023 15:10:01 +0100 [thread overview]
Message-ID: <CALZpt+G_wqAqXkenDwdojT4EhpweYwe2DiCYZRFfCbMLL8DbVA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2639 bytes --]
Hi list,
We have been working since a while with Nicholas Gregory (Commerce Block),
Ray Youssef (the Built With Bitcoin foundation) and few others on a new
peer-to-peer market system to enable censorship-resistant and
permissionless global trading in all parts of the world. While the design
aims in priority to serve on-ramp/off-ramp trading, it can be extended to
support any kind of trading: goods, services, bitcoin financial derivatives
like discreet log contracts.
The design combines the Nostr architecture of simple relays announcing
trade orders to their clients with Lightning onion routing infrastructure,
therefore granting high-level of confidentiality to the market
participants. The market boards are Nostr relays with a Lightning gateway,
each operating autonomously and in competition. The market boards can be
runned as a federation however there is no "decentralized orderbook" logged
into the blockchain. The trades are escrowed under Bitcoin Script
contracts, relying on moderations and know your peer oracles for
adjudication.
The scoring of trades, counterparties and services operators should be
enabled by the introduction of a Web-of-Stakes, assembled from previous
ideas [0]. From the Bitcoin UTXO set servicing as a trustless source of
truth, an economic weight can be assigned to each market entity. This
reputation paradigm could be composed with state-of-the-art Web-of-Trust
techniques like decentralized identifiers [1].
A consistent incentive framework for service operators is proposed by the
intermediary of privacy-preserving credentials backed by Bitcoin payments,
following the lineaments of IETF's Privacy Pass [2]. Services operators
like market boards and oracles are incentivized to thrive for efficiency,
akin to routing hops on Lightning and miners on the base layer.
The whitepaper goes deep in the architecture of the system [3] (Thanks to
the peer reviewers!).
We'll gradually release code and modules, extensively building on top of
the Lightning Dev Kit [4] and Nostr libraries. All according to the best
Bitcoin open-source and decentralized standards established by Bitcoin Core
and we're looking forward to collaborating with everyone in the community
to standardize libraries and guarantee interoperability between clients
with long-term thinking.
Feedback is very welcome!
Cheers,
Nick, Ray and Antoine
[0]
https://lists.linuxfoundation.org/pipermail/lightning-dev/2020-November/002884.html
[1] https://www.w3.org/TR/2022/REC-did-core-20220719/
[2] https://privacypass.github.io
[3] https://github.com/civkit/paper/blob/main/civ_kit_paper.pdf
[4] https://lightningdevkit.org
[-- Attachment #2: Type: text/html, Size: 3277 bytes --]
next reply other threads:[~2023-04-13 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 14:10 Antoine Riard [this message]
2023-05-01 17:47 ` Antoine Riard
2023-05-09 15:09 ` Chris Stewart
2023-06-30 3:46 ` Antoine Riard
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=CALZpt+G_wqAqXkenDwdojT4EhpweYwe2DiCYZRFfCbMLL8DbVA@mail.gmail.com \
--to=antoine.riard@gmail$(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