Skip to content

2. Project Overview

2.1 Project Positioning

Enclave aims to build a privacy-preserving decentralized payment network, achieving the following through zero-knowledge proof technology:

  • Privacy: Complete isolation between allocator and recipient identities
  • Scalability: Support for batch operations, reducing Gas costs
  • Cross-Chain Compatibility: Support for multi-chain asset allocation
  • Decentralization: Node network maintains system security

2.2 Core Features

2.2.1 Enclave Privacy Payment System

  • Deposit Mechanism: Users deposit assets and receive a deposit ID
  • Commitment Submission: Submit allocation commitments through zero-knowledge proofs
  • Privacy Withdrawal: Recipients use zero-knowledge proofs for anonymous withdrawal
  • Batch Operations: Support for batch withdrawals, saving Gas fees
  • Gas Fee Payment: When requesters use the Enclave Privacy system, they need to pay $E tokens as Gas fees, used to cover the costs of zero-knowledge proof generation services

2.2.2 Node Network

  • NFT Identification: Each NFT corresponds to a node identity
  • Zero-Knowledge Proof Generator: Each node must run a zero-knowledge proof generator to generate the zero-knowledge proofs required by the Enclave Privacy system
  • NFT Binding: One node can bind up to 10 NFTs, with multiple NFTs sharing the same node's proof generation service
  • Staking Mechanism: Each NFT locks 2,000 $E
  • Reward Distribution: 80% to NFT holders, 20% to oracle multi-signature nodes
  • Status Management: Active / PendingTermination / Terminated

2.2.3 Token System

  • Mining Mechanism: Fixed mining for the first 6 years, dynamic mining from year 7 onwards
  • Burning Mechanism: Repurchase and burn from Swap, affecting subsequent mining amounts
  • Lock-up Mechanism: Team, SAFT, and node tokens all have lock-up periods

[← Previous: Executive Summary](./01-executive-summary) | [Next: Token Economic Model →](./03-token-economic-model)

Released under the MIT License.