Skip to content

bisq-network/bisq-musig

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

bisq MuSig2 Protocol

This is module inside Bisq2. it implements a new Multisig protocol for Bisq2, this protocol is similar to the protocol used in Bisq1. It enables to buy/sell bitcoin from other peers without needing any trust in the other peer or into any coordinator or any third party. Since there is no intermediary to conduct the exchange, this is as close as its gets to the original bitcoin idea of conducting transaction in a p2p manner secured just by cryptography. Main changes to the Bisq1 protocol are:

  • more private, looks like a normal transaction without script.
  • fewer fees, happy path uses only one transaction
  • uses taproot
  • instead of scripts it uses advance cryptographic schemes like MuSig2 and Adaptor-signatures.
  • protocol is designed to handle unresponsive traders automatically

overview

This project is the handling the cryptographic part of the overall protocol. Even though it is the centerpiece there are more pieces necessary to pull this off. Here is an Overview drawing: modules

docs

To get a more indepth understanding of what this module is doing, please read SingleTxOverview This module's programming language is Rust. Technologies include:

  • bitcoin taproot transactions
  • scriptless scripts (MuSig2, adaptor signatures)
  • Rust
  • gRPC
  • Compact Block Filters (CBF)
  • Bitcoin Development Kit (BDK), especially bdk-wallet
  • crate tokio

If you have any knowledge in one of these areas, you please consider contributing to this project.

contribution

You can contact us at matrix. If you want to get a feeling about this project, check it out and start the testcase tests::test_musig. However, running this needs a working installation of nigiri , please see this section Running Integration Tests. Accepted contributions are eligible for compensation, so you could earn money for your work.

running the tests

to run the test you need a work regtest environment as provided by nigiri. You may need to for whatever reason I nigiri isn't fully operable unless you stop and start it again. Once after start-up I need to run this:

nigiri stop
nigiri start

then to run the tests:

cd protocol
cargo test --package protocol --lib tests -- --test-threads=1 --nocapture

reading the Markdown files

Some of the markdown files have LaTeX included, you can best view them using RustRover. Github sucks at displaying LaTeX. I also keep an html-export of the markdown files in the directory 'renderedForWeb', so you can view them without RustRover.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •