Split key generation across participants so one service, setup process, or operator never starts with the complete private key. Stoffel gives your team a build path from DKG to the signing or encryption path your product needs.
Where your app should not depend on one key holder
Keep account keys out of one service
Start key control across multiple participants instead of one app service generating the complete private key first.
One aggregate public key for your product
A foundation for compatible threshold workflows
Split control across teams and organizations
Give each team or organization a defined role in key generation.
Keep authority distributed across organizational boundaries
Avoid one trusted source of the complete key
Keep automated services from holding the complete key
Generate key material across separate nodes or execution domains.
Match the curve, signing protocol, and integration to your build path
The key starts distributed
If your setup starts with a dealer, one environment briefly owns the complete private key. Stoffel changes that starting point.
Trusted-dealer setup
One party creates and briefly controls the complete private key before anyone else participates.
The dealer divides the key into shares
Participants depend on the dealer and its environment
The trust boundary exists before the key is used
Distributed generation with Stoffel
Your participants jointly produce a public key and individual shares without one dealer first holding the complete private key.
Participants join your key-generation setup
The protocol verifies the values they receive
Each participant retains its own share
Run participants across services and organizations
Participants can run in separate services, organizations, or execution domains. Progress follows the selected protocol’s documented participation and availability assumptions.
Separate execution domains
Independently operated participants
Protocol-defined participation thresholds
From participants to one aggregate public key
Set your boundary
Choose the participants, threshold, and supported curve around your product architecture.
Run distributed generation
Participants contribute through the Stoffel runtime and verify the aggregate public key.
Connect the key to your product
Use the public key with the signing, encryption, or protocol path your application needs.
MPC case study
Generate your keys without one trusted operator
Use Stoffel when your app should not start with one service holding the complete key.
Read case study
Remove single-keyholder risk from your app
If one service, setup process, or operator can access the complete key, bring that architecture to Stoffel. We’ll help you define where key generation should be split across participants.
FAQ
Bring us the place your app handles the complete key. We’ll help map the participants, supported curve, signing protocol, and integration boundary.
What is MPC key management?
MPC key management distributes key generation and key operations across several participants. Instead of one service holding the complete private key, each participant keeps a share and cooperates under a defined threshold.
Does Stoffel provide threshold signing?
Stoffel provides a distributed key-generation path and tested signing workflows for specific curves and protocols. Support depends on the selected curve, signing protocol, and integration. Confirm the complete workflow with the Stoffel team.
Which curves does Stoffel support?
StoffelVM exposes MPC and AVSS configurations for BLS12-381, BN254, Curve25519, Ed25519, secp256k1, and P-256, also called secp256r1. The documented aggregate-public-key ADKG path uses BLS12-381. Confirm the complete workflow for the selected curve and integration.