Setu's distributed signing infrastructure enables secure, fault-tolerant transaction validation across chains
Signing Architecture Diagram
Built with defense-in-depth principles to protect against both external attacks and internal compromise
Redundant signing nodes ensure cross-chain transactions proceed even if some nodes are unavailable
Continues operating correctly even in the presence of failures or malicious behavior
Setu employs a state-of-the-art DKG protocol where no single party ever possesses the complete private key material at any point in time. Private keys are generated collaboratively by multiple nodes.
Multiple parties jointly generate key shares without revealing their portions
Key shares are securely distributed to authorized signing nodes
Regular rotation of keys to minimize compromise window
Setu's key management infrastructure guarantees that even if up to threshold-1 participants are compromised, the system's private keys remain secure and unauthorized transactions cannot be signed.
Setu uses a t-of-n threshold signing scheme, where any subset of t participants from the total n can collaborate to produce valid signatures, without ever reconstructing the private key.
Production Environment
70% of signers required for valid transaction
Testing Environment
60% of signers required for valid transaction
Network participants can verify signatures without knowing the key generation process
Multiple validators ensure transactions meet protocol requirements before signing
No single validator can block legitimate transactions from being processed
Setu's threshold design ensures the system remains operational even if some nodes fail. If a node is permanently lost, recovery involves re-sharing the keys among the remaining active nodes.
In the event of a catastrophic failure, encrypted key backups and governance protocols allow for the secure restoration of the signing infrastructure.
Codebase and cryptographic implementations undergo regular security audits by reputable third-party firms.
Critical components of the signing protocol are formally verified to ensure mathematical correctness and security properties.
Strict access controls and role-based permissions limit access to sensitive operations and key material.
Continuous monitoring detects suspicious activity, triggering automated alerts and response protocols.