use stoffel_rust_sdk::prelude::*;

async fn submit_computation() -> Result<i64> {
    // Connect to MPC network
    let client = StoffelClient::builder()
        .with_servers(&["mpc1.example.com:9000", "mpc2.example.com:9000"])
        .client_id(12345)
        .connect()
        .await?;

    // Submit inputs and get result
    let result = client.run(&[42, 100]).await?;

    Ok(result)
}

Why use SDKs instead of just encrypting things?

Because encryption still means someone has the keys. With MPC, your app splits data into shares before it leaves the client, computes across a network that can't reconstruct inputs, and rebuilds only the final answer locally.

Split before it leaves

Turn inputs into shares on the client. The original value never hits your network.

Compute without seeing

The MPC network processes shares it can't reverse-engineer, even if nodes collude.

Rebuild only the answer

Get result shares back. Combine them locally. Intermediate steps? Gone.

Available SDKs

Rust SDK

Production-ready

Build MPC applications with a mature, fully-functional SDK. Includes MPCaaS architecture separating app developers from infrastructure operators, QUIC networking, and comprehensive error handling.

Python SDK

In development

Clean high-level interface currently under active development. Not production-ready—use Rust SDK for production work today.

Solidity SDK

Production-ready

Integrate MPC into smart contracts for on-chain privacy. Coordinate computations, manage access control, and handle inputs from blockchain applications.