round-based
| Crates.io | round-based |
| lib.rs | round-based |
| version | |
| source | src |
| created_at | 2021-01-24 09:16:35.45202 |
| updated_at | 2024-12-05 11:25:01.518603 |
| description | Driver for MPC protocols |
| homepage | |
| repository | https://github.com/LFDT-Lockness/round-based |
| max_upload_size | |
| id | 345950 |
| Cargo.toml error: | TOML parse error at line 17, column 1 | 17 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
(maurges)
documentation
README
An MPC framework that unifies and simplifies the way of developing and working with multiparty protocols (e.g. threshold signing, random beacons, etc.).
Goals
- 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 abstractionsStreamandSinkto receive and send messages.
Networking
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.
Features
simenables protocol execution simulation, seesimmodulesim-asyncenables protocol execution simulation with tokio runtime, seesim::async_envmodule
state-machineprovides ability to carry out the protocol, defined as async function, via Sync API, seestate_machinemodulederiveis needed to useProtocolMessageproc macroruntime-tokioenables tokio-specific implementation of async runtime
Join us in Discord!
Feel free to reach out to us in Discord!