Comparison of Ika, a Sub-Second MPC Network in the Sui Ecosystem, and Privacy Computing Technology

1. Overview and Positioning of the Ika Network

Ika Network is an innovative infrastructure strategically supported by the Sui Foundation, based on multi-party secure computing ( MPC ) technology. Its most notable feature is the sub-second response time, which is unprecedented in MPC solutions. Ika is highly compatible with Sui in underlying design concepts such as parallel processing and decentralized architecture, and will be directly integrated into the Sui development ecosystem in the future, providing plug-and-play cross-chain security modules for Sui Move smart contracts.

Ika is building a new type of security verification layer, serving both as a dedicated signature protocol for the Sui ecosystem and providing standardized cross-chain solutions for the entire industry. Its layered design balances protocol flexibility with development convenience, and is expected to become an important practical case for the large-scale application of MPC technology in multi-chain scenarios.

Core Technology Analysis 1.1

The technical implementation of the Ika network revolves around high-performance distributed signatures, with the main innovations including:

• 2PC-MPC Signature Protocol: An improved two-party MPC scheme is adopted, which decomposes the user's private key signing operation into a process involving both the "user" and the "Ika network".

• Parallel Processing: Utilizing parallel computing to decompose a single signature operation into multiple concurrent subtasks executed simultaneously across nodes.

• Large-scale node network: Supports thousands of nodes participating in signatures, with each node holding only a part of the key shard.

• Cross-chain control and chain abstraction: allows smart contracts on other chains to directly control accounts in the Ika network (dWallet).

1.2 The potential impact of Ika on the Sui ecosystem

After Ika goes live, it may bring the following expansions to Sui:

• Provide cross-chain interoperability, supporting assets such as Bitcoin and Ethereum to connect to the Sui network.
• Provide a decentralized asset custody mechanism
• Simplify cross-chain interaction processes
• Provide multi-party verification mechanisms for AI automation applications

1.3 Challenges faced by Ika

• Market acceptance: needs to compete with existing cross-chain solutions
• Controversies over the security of MPC solutions: The challenge of revoking signing permissions
• Dependence on the stability of the Sui network
• New issues that may arise from DAG consensus

2. Comparison of projects based on FHE, TEE, ZKP, or MPC

2.1 FHE

Zama & Concrete:

• General Compiler Based on MLIR
• "Layered Bootstrapping" strategy
• Mixed Encoding Support
• Key Packaging Mechanism

Fhenix:

• Optimization for Ethereum EVM instruction set
• Encrypted Virtual Register
• Off-chain Oracle Bridge Module

2.2 TEE

Oasis Network:

• Layered Trusted Root Concept
• The ParaTime interface uses Cap'n Proto binary serialization
• Durable Log Module

2.3 ZKP

Aztec:

• Noir Compiler
• Incremental Recursive Technology
• Parallelized Depth-First Search Algorithm
• Light Node Mode

2.4 MPC

Partisia Blockchain:

• Extension based on the SPDZ protocol
• Preprocessing Module
• gRPC communication, TLS 1.3 encrypted channel
• Dynamic Load Balancing

3. Privacy Computing: FHE, TEE, ZKP, and MPC

Overview of Different Privacy Computing Schemes 3.1

• Fully Homomorphic Encryption ( FHE ): Allows arbitrary computations on encrypted data, fully encrypted.
• Trusted Execution Environment ( TEE ): A trusted hardware module provided by the processor to isolate code execution.
• Multiparty Secure Computation ( MPC ): A function output computed jointly by multiple parties without disclosing private inputs.
• Zero-Knowledge Proof ( ZKP ): verifying a statement to be true without disclosing additional information

Adaptation scenarios of 3.2 FHE, TEE, ZKP and MPC

• Cross-chain signature: MPC and TEE are more applicable, FHE is not suitable.
• DeFi multi-signature wallets, etc.: MPC is mainstream, TEE has applications, FHE is mainly used for privacy logic.
• AI and data privacy: FHE has obvious advantages, MPC and TEE can serve as aids.

3.3 Differentiation of different schemes

• Performance and Latency: FHE is the slowest, TEE is the fastest, ZKP and MPC are in the middle.
• Trust Assumptions: FHE and ZKP do not require trust in third parties, TEE relies on hardware, and MPC relies on participants.
• Scalability: ZKP and MPC naturally support horizontal scaling, while FHE and TEE scalability is limited.
• Integration Difficulty: TEE is the lowest, ZKP and FHE require specialized circuits, and MPC requires protocol stack integration.

4. Market View: "Is FHE Superior to TEE, ZKP, or MPC?"

• FHE is not superior to other solutions in all respects.
• Different technologies have different trust models and applicable scenarios.
• Future privacy computing may be the result of the complementarity and integration of various technologies.
• The choice of technology should be based on specific application requirements and performance trade-offs.