Appendix
A. Technical Specifications
- Smart Contracts: Solidity 0.8.19+
- Zero-Knowledge Proofs: SP1 zkVM
- Hash Algorithm: SHA-256
- Tree Structure: Merkle Tree / Verkle Tree
B. Security Audits
- Smart contracts have undergone third-party security audits
- Zero-knowledge proof circuits have undergone formal verification
- Regular security vulnerability scanning
C. Open Source License and Patent Protection
EnclaveProtocol core code uses open-source licensing, welcoming community contributions and improvements. However, EnclaveProtocol's core technologies are protected by patents.
Patent Protection Statement
EnclaveProtocol's technical solution has been applied for patent protection (Patent Name: A Privacy-Preserving Multi-Recipient Asset Allocation Method and System Based on Zero-Knowledge Proofs). Although source code uses open-source licensing, any commercial deployment or commercial use requires explicit authorization from the patent owner.
Commercial Use Definition
Commercial Systems include but are not limited to the following types:
Fiat Currency Integration Systems
- Systems that directly exchange or settle with traditional fiat currencies (such as USD, CNY, EUR, etc.)
- Systems integrated with traditional payment gateways (such as credit cards, bank transfers, third-party payment platforms)
- Platforms providing fiat deposit/withdrawal services
- Systems involving traditional financial regulatory compliance requirements
Cryptocurrency/Digital Asset Systems
- Systems using cryptocurrencies for value transfer
- Trading systems based on native blockchain tokens
- Stablecoin integration systems
- Tokenized asset trading platforms
- Token circulation systems in decentralized finance (DeFi) applications
- Asset allocation systems related to non-fungible tokens (NFTs)
Hybrid Payment Systems
- Hybrid payment systems supporting both fiat and cryptocurrency tokens
- Asset allocation platforms across asset types
Authorization Requirements
For any commercial deployment, including but not limited to:
- Production environment deployment
- Commercial service offering
- Fee-based services
- Enterprise applications
- Software as a Service (SaaS)
All require:
- Signing a Patent License Agreement with the patent owner
- Obtaining explicit Commercial Use Authorization
- Complying with terms and conditions in the license agreement
Non-Commercial Use
The following uses are generally considered non-commercial and may not require additional authorization (subject to the patent license agreement):
- Academic research and educational purposes
- Personal learning and experimentation
- Open-source community contributions
- Non-profit projects
Authorization Contact
To obtain commercial use authorization, please contact the patent owner for license negotiation.
Important Notice: Unauthorized commercial use may constitute patent infringement, and the patent owner reserves the right to take legal action.
D. Contact Information
- Official Website: [To be added]
- Technical Documentation: [To be added]
- GitHub: [To be added]
- Community: [To be added]
Document Version: v1.0
Last Updated: September 16, 2025
Maintainer: EnclaveProtocol Team