MPC tech enhances crypto security
The idOS Network is using Multi-Party Computation (MPC) to enhance private key security, a move praised by social media users as superior to traditional Web2 logins. One user explained the technology splits private keys across multiple nodes, which are only reconstructed when needed, eliminating single points of failure like seed phrases.
- The idOS Network's Multi-Party Computation (MPC) is implemented through a partnership with Partisia Blockchain, which provides a production-grade MPC engine that slices each private key into cryptographic shards. These shards are distributed across independent validator nodes, ensuring no single node holds the complete key. - The key reconstruction process is temporary and happens in-memory for milliseconds only when a user authorizes an action with a standard wallet signature, such as from MetaMask. This design avoids the need for users to manage new passwords or seed phrases. - The cryptographic method used for splitting the keys is Shamir's Secret Sharing, which ensures that individual key shares are undecipherable and useless on their own. An attacker would need to compromise a quorum of nodes simultaneously to reconstruct a key. - Unlike multi-signature (multisig) wallets that require multiple independent private keys to sign a transaction, MPC technology splits a single key. This results in on-chain transactions that appear as if signed by a single key, which can lead to lower transaction fees and enhanced privacy. - The idOS network is a collaborative project involving several key partners besides Partisia Blockchain, including Fractal ID, Aleph Zero, Kwil, NEAR, and Gnosis, with the goal of creating a chain-agnostic identity layer for Web3. - The project is backed by venture capital, having raised $4.5 million in a funding round led by Fabric Ventures with participation from Circle Ventures. - The idOS is designed to be a decentralized storage network for identity data, where users retain control over their encrypted information. This architecture aims to provide a compliant way for dApps to verify user identity without centrally storing personally identifiable information.