2 releases

0.2.1 Feb 15, 2024
0.2.0 Nov 23, 2023

#27 in #deriving

Download history 12/week @ 2023-12-22 46/week @ 2024-01-05 91/week @ 2024-01-12 124/week @ 2024-01-19 146/week @ 2024-01-26 143/week @ 2024-02-02 298/week @ 2024-02-09 288/week @ 2024-02-16 164/week @ 2024-02-23 321/week @ 2024-03-01 254/week @ 2024-03-08 227/week @ 2024-03-15 224/week @ 2024-03-22 293/week @ 2024-03-29 134/week @ 2024-04-05

907 downloads per month
Used in 3 crates (via round-based)


152 lines

License: MIT Docs Crates io

An MPC framework that unifies and simplifies the way of developing and working with multiparty protocols (e.g. threshold signing, random beacons, etc.).


  • Async friendly
    Async is the most simple and efficient way of doing networking in Rust
  • Simple, configurable
    Protocol can be carried out in a few lines of code: check out examples.
  • Independent of networking layer
    We use abstractions Stream and Sink to receive and send messages.


In order to run an MPC protocol, transport layer needs to be defined. All you have to do is to implement Delivery trait which is basically a stream and a sink for receiving and sending messages.

Message delivery should meet certain criterias that differ from protocol to protocol (refer to the documentation of the protocol you're using), but usually they are:

  • Messages should be authenticated
    Each message should be signed with identity key of the sender. This implies having Public Key Infrastructure.
  • P2P messages should be encrypted
    Only recipient should be able to learn the content of p2p message
  • Broadcast channel should be reliable
    Some protocols may require broadcast channel to be reliable. Simply saying, when party receives a broadcast message over reliable channel it should be ensured that everybody else received the same message.


  • dev enables development tools such as protocol simulation
  • runtime-tokio enables tokio-specific implementation of async runtime


~33K SLoC