Tech Overview

RADIUM serves as an advanced multi-signature wallet incorporating a consensus layer. It functions as an intermediary layer positioned between a beacon node and a validator client. From the user's standpoint, RADIUM is a seamless plug-and-play component that efficiently manages all tasks on their behalf. The key elements of an RADIUM configuration include:

Distributed Key Generation

This process involves the collaborative generation of a shared public and private key set by RADIUM instance operators. Each operator possesses a distinct portion of the private key, ensuring that no single operator can unilaterally control or influence the entire private key.

Shamir Secret Sharing

Utilized for reconstructing a validator key using a predefined threshold of KeyShares. Individual KeyShares lack the capability to sign duties independently; however, not all KeyShares are necessary if some are faulty, as indicated by the equation n≥3f+1.

RADIUM capitalizes on BLS signatures, enabling multiple signatures to be combined to regenerate a validator key signature. Through the fusion of Shamir and BLS techniques, keys are disassembled for distribution and reassembled when a duty is assigned.

Multi-Party Computation

Secure Multi-Party Computation (MPC) is applied to distribute RADIUM KeyShares securely among operators and to facilitate decentralized computation of validator duties without centralizing the reconstruction of the validator key on a single device.

Istanbul Byzantine Fault Tolerance Consensus

Bringing everything together, RADIUM consensus layer relies on the Istanbul Byzantine Fault Tolerance (IBFT) algorithm. This algorithm randomly selects a validator node (KeyShare) responsible for block proposal and shares this information with other participants. Once the predefined threshold of KeyShares deems the block valid, it is added to the chain. Consequently, consensus can be achieved even in the presence of some faulty or temporarily offline operators, within the defined threshold.