What is ChainGuard Identity?

ChainGuard Identity is a unified Web3 identity system that creates a cryptographically verifiable link between your KYC-verified ChainGuard account, your physical ChainGuard mobile app (airgapped 2FA device), and your wallet addresses. This three-way binding ensures that vault operations require proof of ownership from both your wallet and your ChainGuard app, providing enterprise-grade security for Web3 asset management.

How does ChainGuard Identity work?

ChainGuard Identity combines four key components: 1) KYC verification through third-party providers (Sumsub, Onfido, Jumio) linked to your ChainGuard account, 2) Vault creation using factory/clone pattern (EIP-1167) for cost-efficient deployment, 3) Wallet binding through dual signature verification (wallet signature + ChainGuard app signature), 4) On-chain validation that records all identity linkages immutably on the blockchain. This creates a unified identity that works across all ChainGuard products and dApps.

What is KYC verification and why do I need it?

KYC (Know Your Customer) verification is a compliance process that verifies your identity through document checks. ChainGuard integrates with leading KYC providers (Sumsub, Onfido, Jumio) at a cost of $1.50-$5.00 per user (average $2.50). KYC provides the foundation for enterprise-grade security and compliance, creating a trusted identity that works across all ChainGuard products and can be used for compliant transactions, regulatory reporting, and enterprise integrations.

How does vault creation work?

ChainGuard uses the EIP-1167 minimal proxy pattern to deploy vaults efficiently. A factory contract is deployed once per blockchain network, and each user's vault is created as a minimal proxy clone pointing to the implementation contract. This dramatically reduces deployment costs (Base: ~$1.00, Multi-chain: ~$7.50 vs. $200+ for full deployments) while maintaining full security and functionality. The vault is initialized with your three-address configuration (Primary, 2FA, Secondary) and linked to your KYC-verified ChainGuard account identity.

What is wallet binding?

Wallet binding creates a cryptographically verifiable link between your wallet address and your ChainGuard account. This process requires signatures from both your wallet (MetaMask, etc.) and your ChainGuard mobile app, proving that you own both devices. The binding process: 1) System generates QR code with unique nonce, 2) You sign binding message with your wallet, 3) You scan QR code with ChainGuard app which signs the message, 4) Both signatures are verified on-chain using ECDSA recovery, 5) Wallet is linked to your ChainGuard identity in your user profile.

Why do I need to bind my wallet?

Wallet binding is the critical link that connects your verified ChainGuard identity to your wallet addresses. This creates a three-way binding: your KYC-verified account, your ChainGuard app (2FA device), and your wallet. This binding is essential for vault operations and provides enterprise-grade security by ensuring that vault operations require validated wallet binding, preventing unauthorized access. It also creates a unified identity that works across all ChainGuard products and dApps.

What is on-chain validation?

On-chain validation ensures that all identity linkages are cryptographically verified and permanently recorded on the blockchain. The process includes: 1) Message construction with action type, sessionId, timestamp, nonce, and wallet address, 2) Signature recovery using ECDSA to verify both wallet and ChainGuard app signatures, 3) Session validation to ensure active authenticated session exists, 4) Profile update storing wallet binding in user profile, 5) Vault linkage requiring validated wallet binding for all vault operations. This creates an immutable audit trail that cannot be tampered with.

How secure is ChainGuard Identity?

ChainGuard Identity provides enterprise-grade security through multiple layers: 1) KYC verification ensures verified identity foundation, 2) Dual signature requirement (wallet + ChainGuard app) proves ownership of both devices, 3) On-chain validation creates immutable cryptographic proof of identity linkage, 4) Three-address protocol requires multiple approvals for vault operations, 5) Airgapped mobile app operates offline for maximum security, 6) All validations recorded on blockchain preventing tampering. This combination provides institutional-level security for Web3 asset management.

Can I use ChainGuard Identity with multiple wallets?

Yes! You can bind multiple wallets to your ChainGuard Identity. Each wallet binding follows the same dual signature verification process (wallet signature + ChainGuard app signature). You can designate one wallet as your primary address and others as fallback addresses. All bound wallets are linked to your KYC-verified ChainGuard account identity and can be used for vault operations. This allows you to manage multiple wallets while maintaining a unified identity across all of them.

What happens if I lose access to my ChainGuard mobile app?

If you lose access to your ChainGuard mobile app, you can recover access through the three-address recovery system. Any two of your three addresses (Primary wallet, ChainGuard app address, Secondary address) can recover the third after a security cooldown period (24 hours). This ensures you never lose access to your assets while maintaining maximum security. The recovery process requires on-chain validation and follows the same security protocols as regular operations.

How does ChainGuard Identity work with other ChainGuard products?

ChainGuard Identity is the foundation that connects all ChainGuard products: 1) ChainGuard Vault uses your identity for multi-signature protection, 2) ChainGuard OAuth uses your identity for dApp authentication, 3) ChainGuard Mobile App uses your identity for 2FA signatures, 4) All products share the same KYC-verified account and wallet bindings. This creates a seamless, secure experience across the entire ChainGuard ecosystem - one verified identity works everywhere.

Is my identity information stored on the blockchain?

KYC verification data is processed by third-party providers (Sumsub, Onfido, Jumio) and linked to your ChainGuard account. The blockchain stores: 1) Cryptographic proof of identity linkage (signatures, addresses), 2) Wallet binding records, 3) Vault deployment addresses, 4) Transaction history. Personal KYC documents are not stored on-chain - only the verification status and cryptographic proofs are recorded. This provides privacy while maintaining the security benefits of on-chain validation.

How long does the identity setup process take?

The ChainGuard Identity setup process typically takes 15-30 minutes: 1) Account creation and setup fee payment (5 minutes), 2) KYC verification (10-20 minutes depending on provider response time), 3) Vault deployment (automatic, 1-2 minutes), 4) Wallet binding (5-10 minutes including QR code scanning and signatures). The entire process is guided and can be completed in one session. KYC verification may take longer if additional documentation is required.

Can I use ChainGuard Identity for enterprise compliance?

Yes! ChainGuard Identity is designed for enterprise compliance: 1) KYC verification meets regulatory requirements for institutional use, 2) On-chain validation provides immutable audit trail for compliance and auditing, 3) Complete transaction history with full traceability, 4) Transparent actions that are verifiable and traceable, 5) Real-time compliance monitoring and reporting. The system meets regulatory standards for institutional use and provides the foundation for compliant Web3 operations.

What is the factory/clone pattern and why does it matter?

The factory/clone pattern (EIP-1167) is a smart contract deployment optimization. Instead of deploying a full vault contract for each user (costing $50-$200+), a factory contract is deployed once per network, and each user's vault is created as a minimal proxy clone. This reduces deployment costs by 70-90% (Base: ~$1.00 vs. $50+, Multi-chain: ~$7.50 vs. $200+) while maintaining identical security and functionality. The pattern is industry-standard and used by major DeFi protocols for cost-efficient contract deployment.

How does dual signature verification work?

Dual signature verification requires signatures from both your wallet and ChainGuard app to prove ownership of both devices. The process: 1) System creates binding message with unique nonce, 2) You sign message with your wallet (proves wallet ownership), 3) You scan QR code with ChainGuard app which signs the same message (proves app ownership), 4) Both signatures are verified on-chain using ECDSA recovery, 5) System confirms both signatures recover to correct addresses. This cryptographic proof cannot be forged - you must physically control both devices to complete the binding.

What happens if my wallet binding fails?

If wallet binding fails, the system will provide specific error messages: 1) Signature mismatch - signatures don't recover to expected addresses (check wallet connection and ChainGuard app), 2) Session expired - binding session timed out (restart binding process), 3) Invalid session - session not found or not authenticated (ensure you're logged in), 4) Network error - blockchain interaction failed (retry transaction). Most issues can be resolved by restarting the binding process. Support is available if problems persist.

Can I unbind a wallet from my ChainGuard Identity?

Yes, you can unbind wallets from your ChainGuard Identity through the dashboard. However, unbinding a wallet that is used as a primary address for vault operations may require additional security verification. The unbinding process follows the same security protocols as binding - requiring confirmation from your ChainGuard app. Unbinding a wallet does not affect your KYC-verified account identity or other bound wallets.

How does ChainGuard Identity compare to other Web3 identity solutions?

ChainGuard Identity is unique in combining: 1) KYC verification with on-chain validation (most solutions offer one or the other), 2) Unified identity across vault, OAuth, and mobile app (most solutions are fragmented), 3) Factory/clone pattern for cost-efficient vault deployment (most solutions require expensive full deployments), 4) Dual signature wallet binding with on-chain proof (most solutions use simple wallet connections), 5) Enterprise compliance features with immutable audit trail. This creates a complete identity system rather than just wallet management.

What is the cost of setting up ChainGuard Identity?

The first three steps of ChainGuard Identity setup are completely free: 1) Download app and create account (FREE), 2) Wallet binding and profile (FREE), 3) Choose your path (FREE). The setup fee is only required in step 4 when you're ready to complete setup. The one-time setup fee includes: Base Chain Setup ($8.75-$22.50 with launch discount) or Extended Multi-Chain Setup ($22.50-$56.25 with launch discount). This includes: 1) KYC verification ($1.50-$5.00), 2) Vault deployment (Base: ~$1.00, Multi-chain: ~$7.50), 3) Account setup and onboarding, 4) First year free access to all ChainGuard products. There are no additional fees for identity setup - it's all included in the initial setup fee.

Can I use ChainGuard Identity for free?

Yes! You can use ChainGuard Identity for free in the first three steps: 1) Download the app and create your account (FREE), 2) Connect the app to your profile for wallet binding (FREE), 3) Choose your path - stick around for free and join the community, or proceed to complete setup (FREE). The setup fee is only required in step 4 when you're ready to unlock premium features like KYC verification, vault deployment, and full access to all ChainGuard modules. You can explore and participate in the community for free until you're ready to complete your setup.

What can I do with ChainGuard Identity before paying?

Before paying the setup fee, you can: 1) Download the ChainGuard mobile app, 2) Create your profile with username and email, 3) Connect the app to your profile (wallet binding), 4) Explore your dashboard and see all available features, 5) Join our community and participate in community activities, 6) Learn about Web3 security and ChainGuard features. All of this is available at no cost. The setup fee is only required when you're ready to unlock premium features like KYC verification, vault deployment, and full access to all ChainGuard modules.

What personal information is collected during KYC verification?

During KYC verification, ChainGuard collects: Full legal name, Government-issued ID number, Proof of address document, Biometric data (if required by jurisdiction), and Date of birth. This information is submitted through the ChainGuard interface and verified by third-party KYC providers (Sumsub, Onfido, or Jumio). All data is immediately encrypted before storage, and no raw PII (Personally Identifiable Information) is ever stored in plaintext.

How does ChainGuard protect my KYC data?

ChainGuard protects your KYC data through multiple security layers: 1) Immediate encryption - All PII is encrypted using AES-256-GCM encryption before storage, 2) Hashing - KYC ID is hashed with a unique salt using keccak256(sha256(kycId || uniqueSalt)), ensuring no two users have the same hash even with identical KYC IDs, 3) Off-chain storage - Encrypted PII is stored in ChainGuard's secure off-chain database with strict access controls, 4) Audit logs - All access attempts are logged with timestamp, user ID, and purpose, 5) Compliance - Data handling is compliant with GDPR, CCPA, and other data protection regulations. No raw PII is stored on the blockchain.

What happens to my KYC data after verification?

After KYC verification: 1) Raw PII is encrypted with AES-256-GCM and stored off-chain in a secure database, 2) KYC ID is hashed with a unique salt and the hash is used for on-chain operations, 3) Only encrypted data is stored with role-based access control (RBAC), 4) Access is controlled with audit logs tracking all access attempts, 5) No raw PII is stored on the blockchain - only cryptographic proofs. Your encrypted data remains accessible for compliance and audit purposes, but cannot be accessed without proper authorization and is never shared with dApps or third parties.

What encryption algorithm does ChainGuard use for KYC data?

ChainGuard uses AES-256-GCM (Advanced Encryption Standard with 256-bit key and Galois/Counter Mode) for encrypting all personally identifiable information. This is the same encryption standard used by banks and government agencies. The KYC identifier is hashed using a two-step process: first SHA-256, then Keccak256, with a unique salt per user. The formula is: keccak256(sha256(kycId || uniqueSalt)). This ensures no two users have the same hash even with identical KYC IDs, and the hash cannot be reversed to reveal the original KYC ID.

How does the KYC ID hashing process work?

The KYC ID hashing process uses a two-step cryptographic hash: 1) First, the KYC ID is combined with a unique salt (generated per user) and hashed using SHA-256, 2) Then, the SHA-256 result is hashed again using Keccak256 (the same hash function used by Ethereum). The formula is: keccak256(sha256(kycId || uniqueSalt)). The salt is generated per user and stored securely. This double-hashing with salt ensures: No two users have the same hash even with identical KYC IDs, the hash cannot be reversed to reveal the original KYC ID, and the process is cryptographically secure and irreversible.

Where is my encrypted KYC data stored?

Your encrypted KYC data is stored in ChainGuard's secure off-chain database with: 1) Encrypted database with role-based access control (RBAC) ensuring only authorized personnel can access data, 2) Audit logs tracking all access attempts with timestamp, user ID, and purpose, 3) Compliance with GDPR, CCPA, and other data protection regulations, 4) Data encrypted at rest and in transit, 5) Access controlled with strict security protocols. No raw PII is stored on the blockchain - only encrypted data is stored off-chain, and only cryptographic proofs (hashes) are stored on-chain for verification purposes.

Can I access my stored KYC data?

Yes, you can access your KYC verification status and related information through your ChainGuard dashboard. However, for security and privacy reasons, raw PII (Personally Identifiable Information) is not displayed directly. You can view: 1) KYC verification status and level, 2) Verification date and expiration, 3) KYC ID hash (cryptographic proof), 4) Linked wallet addresses, 5) Vault addresses associated with your identity. If you need to update your KYC information or request data deletion, you can contact support. All data access is logged for audit purposes.

What is a combined hash in ChainGuard Identity?

A combined hash is a cryptographic proof that links your verified identity to your wallet address. It's computed by concatenating multiple identifiers: your hashed KYC ID, user wallet address, ChainGuard account address, vault ID, a unique nonce, and timestamp. The formula is: keccak256(kycIdHash || userAddress || chainGuardAddr || vaultId || nonce || timestamp). This creates a unique, immutable link between your verified identity and wallet address. The nonce prevents replay attacks, and the timestamp ensures freshness. This combined hash is then signed by the Guardian service to create an attestation.

What is Guardian Attestation and how does it work?

Guardian Attestation is a cryptographic proof that ChainGuard has verified your KYC and attests to the linkage between your identity and wallet. The process: 1) A combined hash is computed from your KYC ID hash, wallet address, ChainGuard address, vault ID, nonce, and timestamp, 2) The Guardian service (running on secure infrastructure) signs the combined hash using its private key stored in a Hardware Security Module (HSM), 3) The signature uses ECDSA with secp256k1 curve following EIP-191 standard, 4) The signature proves that ChainGuard has verified your KYC and attests to the identity-wallet linkage, 5) The signature can be verified on-chain using the Guardian's public key. The private key never leaves the HSM, ensuring maximum security.

What data is stored on-chain vs off-chain?

On-chain data (stored on blockchain): Combined hash (cryptographic proof linking identity to wallet), Guardian signature (ECDSA signature proving KYC verification), Timestamp (when attestation was created), Nonce (prevents replay attacks), and Vault ID (associated vault address). Off-chain data (stored in secure database): Encrypted PII (all personal information encrypted with AES-256-GCM), KYC documents (original verification documents), Access logs (audit trail of data access), and User profile data (account settings, preferences). This separation ensures: Privacy (no PII on public blockchain), Security (encrypted data in controlled environment), Auditability (on-chain proofs are immutable), and Compliance (meets data protection regulations).

How does ChainGuard Identity integrate with the vault?

ChainGuard Identity integrates with the vault through on-chain attestation: 1) The vault smart contract verifies the attestation before allowing sensitive operations, 2) It checks that the Guardian signature is valid using the Guardian's public key, 3) It verifies that the attestation links the correct wallet to the verified identity, 4) It ensures the attestation is not expired, 5) Operations require both wallet signature and valid attestation proof. This enables: Regulatory compliance (MiCA, Travel Rule), Identity verification for DeFi protocols, KYC requirements for exchanges, and Secure operations requiring both wallet signature and valid attestation proof. The vault uses the attestation hash to verify operations, creating a secure link between your identity and vault activities.

What are the use cases for ChainGuard Identity attestation?

ChainGuard Identity attestation enables: 1) Regulatory compliance - Meets MiCA (Markets in Crypto-Assets) and Travel Rule requirements for identity verification, 2) Travel Rule compliance - Provides verified identity for cross-border transactions, 3) Identity verification for DeFi protocols - dApps can verify your KYC status without accessing your personal data, 4) KYC requirements for exchanges - Exchanges can verify your identity status through ChainGuard attestation, 5) Enterprise integrations - Businesses can verify user identity for compliant operations, 6) Audit and reporting - Immutable on-chain records for compliance and auditing. The attestation provides proof of identity without revealing personal information, creating a privacy-preserving compliance solution.

How long is my KYC verification valid?

Your KYC verification is valid for one year from the date of verification. When you finalize your ChainGuard account, KYC verification is included in your one-time setup fee and remains valid for one year. After one year, you'll need to renew your KYC verification to maintain full access to all features. The renewal process is similar to the initial verification and may have reduced fees. Your ChainGuard Identity, wallet bindings, and vault remain active during the renewal process. You'll receive notifications before your KYC expires to ensure continuous service.

Can I view my attestation on the blockchain?

Yes! All attestations are stored on-chain and can be viewed on blockchain explorers. When an attestation is created, you receive a transaction hash that can be viewed on: Basescan.org (for Base network), Etherscan.io (for Ethereum mainnet), or the appropriate explorer for your network. The on-chain record shows: Combined hash, Guardian signature, Timestamp, Nonce, and Vault ID. This provides complete transparency and auditability. You can also view your attestation status in your ChainGuard dashboard, which provides a user-friendly interface to all your identity and attestation information.

What is ChainGuard Identity?

ChainGuard Identity is a unified Web3 identity system that creates a cryptographically verifiable link between your KYC-verified ChainGuard account, your physical ChainGuard mobile app (airgapped 2FA device), and your wallet addresses. This three-way binding ensures that vault operations require proof of ownership from both your wallet and your ChainGuard app, providing enterprise-grade security for Web3 asset management.

How does ChainGuard Identity work?

ChainGuard Identity combines four key components: 1) KYC verification through third-party providers (Sumsub, Onfido, Jumio) linked to your ChainGuard account, 2) Vault creation using factory/clone pattern (EIP-1167) for cost-efficient deployment, 3) Wallet binding through dual signature verification (wallet signature + ChainGuard app signature), 4) On-chain validation that records all identity linkages immutably on the blockchain. This creates a unified identity that works across all ChainGuard products and dApps.

What is KYC verification and why do I need it?

KYC (Know Your Customer) verification is a compliance process that verifies your identity through document checks. ChainGuard integrates with leading KYC providers (Sumsub, Onfido, Jumio) at a cost of $1.50-$5.00 per user (average $2.50). KYC provides the foundation for enterprise-grade security and compliance, creating a trusted identity that works across all ChainGuard products and can be used for compliant transactions, regulatory reporting, and enterprise integrations.

How does vault creation work?

ChainGuard uses the EIP-1167 minimal proxy pattern to deploy vaults efficiently. A factory contract is deployed once per blockchain network, and each user's vault is created as a minimal proxy clone pointing to the implementation contract. This dramatically reduces deployment costs (Base: ~$1.00, Multi-chain: ~$7.50 vs. $200+ for full deployments) while maintaining full security and functionality. The vault is initialized with your three-address configuration (Primary, 2FA, Secondary) and linked to your KYC-verified ChainGuard account identity.

What is wallet binding?

Wallet binding creates a cryptographically verifiable link between your wallet address and your ChainGuard account. This process requires signatures from both your wallet (MetaMask, etc.) and your ChainGuard mobile app, proving that you own both devices. The binding process: 1) System generates QR code with unique nonce, 2) You sign binding message with your wallet, 3) You scan QR code with ChainGuard app which signs the message, 4) Both signatures are verified on-chain using ECDSA recovery, 5) Wallet is linked to your ChainGuard identity in your user profile.

Why do I need to bind my wallet?

Wallet binding is the critical link that connects your verified ChainGuard identity to your wallet addresses. This creates a three-way binding: your KYC-verified account, your ChainGuard app (2FA device), and your wallet. This binding is essential for vault operations and provides enterprise-grade security by ensuring that vault operations require validated wallet binding, preventing unauthorized access. It also creates a unified identity that works across all ChainGuard products and dApps.

What is on-chain validation?

On-chain validation ensures that all identity linkages are cryptographically verified and permanently recorded on the blockchain. The process includes: 1) Message construction with action type, sessionId, timestamp, nonce, and wallet address, 2) Signature recovery using ECDSA to verify both wallet and ChainGuard app signatures, 3) Session validation to ensure active authenticated session exists, 4) Profile update storing wallet binding in user profile, 5) Vault linkage requiring validated wallet binding for all vault operations. This creates an immutable audit trail that cannot be tampered with.

How secure is ChainGuard Identity?

ChainGuard Identity provides enterprise-grade security through multiple layers: 1) KYC verification ensures verified identity foundation, 2) Dual signature requirement (wallet + ChainGuard app) proves ownership of both devices, 3) On-chain validation creates immutable cryptographic proof of identity linkage, 4) Three-address protocol requires multiple approvals for vault operations, 5) Airgapped mobile app operates offline for maximum security, 6) All validations recorded on blockchain preventing tampering. This combination provides institutional-level security for Web3 asset management.

Can I use ChainGuard Identity with multiple wallets?

Yes! You can bind multiple wallets to your ChainGuard Identity. Each wallet binding follows the same dual signature verification process (wallet signature + ChainGuard app signature). You can designate one wallet as your primary address and others as fallback addresses. All bound wallets are linked to your KYC-verified ChainGuard account identity and can be used for vault operations. This allows you to manage multiple wallets while maintaining a unified identity across all of them.

What happens if I lose access to my ChainGuard mobile app?

If you lose access to your ChainGuard mobile app, you can recover access through the three-address recovery system. Any two of your three addresses (Primary wallet, ChainGuard app address, Secondary address) can recover the third after a security cooldown period (24 hours). This ensures you never lose access to your assets while maintaining maximum security. The recovery process requires on-chain validation and follows the same security protocols as regular operations.

How does ChainGuard Identity work with other ChainGuard products?

ChainGuard Identity is the foundation that connects all ChainGuard products: 1) ChainGuard Vault uses your identity for multi-signature protection, 2) ChainGuard OAuth uses your identity for dApp authentication, 3) ChainGuard Mobile App uses your identity for 2FA signatures, 4) All products share the same KYC-verified account and wallet bindings. This creates a seamless, secure experience across the entire ChainGuard ecosystem - one verified identity works everywhere.

Is my identity information stored on the blockchain?

KYC verification data is processed by third-party providers (Sumsub, Onfido, Jumio) and linked to your ChainGuard account. The blockchain stores: 1) Cryptographic proof of identity linkage (signatures, addresses), 2) Wallet binding records, 3) Vault deployment addresses, 4) Transaction history. Personal KYC documents are not stored on-chain - only the verification status and cryptographic proofs are recorded. This provides privacy while maintaining the security benefits of on-chain validation.

How long does the identity setup process take?

The ChainGuard Identity setup process typically takes 15-30 minutes: 1) Account creation and setup fee payment (5 minutes), 2) KYC verification (10-20 minutes depending on provider response time), 3) Vault deployment (automatic, 1-2 minutes), 4) Wallet binding (5-10 minutes including QR code scanning and signatures). The entire process is guided and can be completed in one session. KYC verification may take longer if additional documentation is required.

Can I use ChainGuard Identity for enterprise compliance?

Yes! ChainGuard Identity is designed for enterprise compliance: 1) KYC verification meets regulatory requirements for institutional use, 2) On-chain validation provides immutable audit trail for compliance and auditing, 3) Complete transaction history with full traceability, 4) Transparent actions that are verifiable and traceable, 5) Real-time compliance monitoring and reporting. The system meets regulatory standards for institutional use and provides the foundation for compliant Web3 operations.

What is the factory/clone pattern and why does it matter?

The factory/clone pattern (EIP-1167) is a smart contract deployment optimization. Instead of deploying a full vault contract for each user (costing $50-$200+), a factory contract is deployed once per network, and each user's vault is created as a minimal proxy clone. This reduces deployment costs by 70-90% (Base: ~$1.00 vs. $50+, Multi-chain: ~$7.50 vs. $200+) while maintaining identical security and functionality. The pattern is industry-standard and used by major DeFi protocols for cost-efficient contract deployment.

ChainGuard Identity

تحقق KYC، إنشاء خزنة، وربط المحافظ مع التحقق على السلسلة

توفر ChainGuard Identity رابطاً يمكن التحقق منه تشفيرياً بين حسابك الذي اجتاز KYC وتطبيق ChainGuard المحمول (جهاز 2FA معزول) وعناوين محفظتك. عند إتمام إعداد حساب ChainGuard، يكون التحقق KYC مشمولاً في رسوم الإعداد لمرة واحدة ويظل صالحاً لمدة عام. هذا الربط الثلاثي يفرض أن جميع عمليات الخزنة تتطلب دليلاً على الملكية من محفظتك وتطبيق ChainGuard، ما يقدم أماناً بمستوى الشركات لإدارة أصول Web3.

على عكس حلول الهوية التقليدية في Web3 التي تعتمد على خدمات منفصلة، توحد ChainGuard Identity التحقق KYC ونشر الخزنة وربط المحفظة في نظام واحد سلس. يتم التحقق من كل مكون على السلسلة، مما ينشئ إثباتاً غير قابل للتغيير لربط الهوية يعمل عبر جميع منتجات ودApps ChainGuard.

ابدأ الآن اعرف المزيد

التقطني

تطبيق ChainGuard

99.9%

ضمان التوافر

3-Way

ربط أمني ثلاثي

On-Chain

إثبات غير قابل للتغيير

1 Year

صلاحية KYC لمدة عام

الأمان والامتثال

معايير أمان على مستوى المؤسسات والتزام تنظيمي كامل

تكامل KYC

تحقق هوية من مزودين خارجيين مدمج مباشرة في حساب ChainGuard الخاص بك

كيف يعمل KYC

عند إتمام حساب ChainGuard الخاص بك، يتم تضمين التحقق KYC في رسوم الإعداد لمرة واحدة. نتكامل مع كبار مزودي KYC مثل Sumsub وOnfido وJumio لإجراء تحقق مستندي وفحوصات امتثال. يرتبط هذا التحقق بحسابك لمدة 12 شهراً، ما يخلق أساس هوية موثق لجميع تفاعلاتك على Web3.

تحقق من مزودين خارجيين (Sumsub، Onfido، Jumio)

تحقق من المستندات وفحوصات الامتثال

مشمولة في رسوم الإعداد – بدون تكلفة إضافية (تكلفة KYC بين 1.50 و5 دولارات لكل مستخدم، المتوسط 2.50 دولار)

صالحة لمدة عام كامل من تاريخ الإعداد

مرتبطة بهوية حساب ChainGuard

جاهزة للامتثال المؤسسي

أهمية KYC

تشكل KYC الركيزة الأساسية للأمان والامتثال. ربط هوية موثقة بحسابك يمنحك هوية موحدة تعمل مع جميع منتجات ChainGuard، وتلبي متطلبات التقارير التنظيمية والتكاملات المؤسسية.

هوية مثبتة

هوية موثقة مرتبطة بحسابك

امتثال مؤسسي

تلبية متطلبات الجهات الرقابية للمؤسسات

هوية موحدة

هوية واحدة تعمل مع كل منتجات ChainGuard

إنشاء الخزنة ونشرها

نشر خزائن على السلسلة باستخدام نمط factory/clone لتقليل التكاليف وزيادة الأمان

نمط Factory/Clone (EIP-1167)

نعتمد نمط الوكيل المصغر EIP-1167 لنشر الخزائن بكفاءة. يتم نشر عقد Factory واحد لكل شبكة، ويُنشأ لكل مستخدم خزنة كوكيل مصغر يشير إلى عقد التنفيذ، ما يخفض التكلفة بنسبة تصل إلى 90% مع الحفاظ على الأمان الكامل.

نشر على السلسلة

يتم نشر الخزنة عبر عقد VaultFactory

عقد متعدد التوقيع

بروتوكول ثلاثي العناوين مدمج في كل خزنة

بروتوكول ثلاثي

عنوان أساسي + عنوان 2FA + عنوان ثانوي للحماية القصوى

نشر منخفض التكلفة

تخفيض تكلفة النشر بنسبة 70-90% مقارنة بالعقود الكاملة

خطوات إنشاء الخزنة

1
نشر عقد Factory
يُنشَر VaultFactory مرة واحدة لكل شبكة (يشمل التكلفة ضمن البنية التحتية)
2
إنشاء وكيل مصغر
تُنشأ خزنة المستخدم كنسخة وكيل مصغر تشير لعقد التنفيذ
3
إعداد العناوين الثلاثة
تهيئة الخزنة بعنوان أساسي، وعنوان 2FA (تطبيق ChainGuard)، وعنوان ثانوي
4
ربط الهوية
يتم ربط عنوان الخزنة بهويتك الموثقة في ملف المستخدم

ربط المحافظ والتحقق من الملكية

أثبت أنك تمتلك تطبيق ChainGuard والمحفظة عبر تحقق توقيع مزدوج

كيفية ربط المحفظة

ينشئ الربط رابطاً موثقاً على السلسلة بين عنوان محفظتك وحساب ChainGuard. يتطلب توقيعاً من محفظتك (مثل MetaMask) وتوقيعاً من تطبيق ChainGuard، مما يؤكد أنك تملك كلا الجهازين. بعد ذلك يتم التحقق على السلسلة لإنشاء سجل غير قابل للتلاعب.

1. توليد رمز QR

ينشئ النظام جلسة ربط مع قيمة nonce فريدة ويعرض رمز QR يحتوي على بيانات الطلب.

2. توقيع المحفظة

توقع رسالة الربط من خلال محفظتك لإثبات ملكية العنوان.

3. توقيع تطبيق ChainGuard

تمسح رمز QR عبر التطبيق المحمول ليوقع الرسالة بمفتاح حسابك الخاص.

4. تحقق مزدوج

يتم التحقق من التوقيعين على السلسلة باستخدام ECDSA للتأكد من مطابقتهما للعناوين المتوقعة.

5. إكمال الربط

تُخزن المحفظة كعنوان أساسي أو احتياطي، وتصبح كل أوامر الخزنة مقترنة بهذا الربط.

لماذا الربط مهم

الربط هو الحلقة التي تصل هوية ChainGuard الموثقة بمحافظك، لتكوين رباط ثلاثي: الحساب الموثق + تطبيق ChainGuard + المحفظة. وهذا الشرط ضروري لعمليات الخزنة ويقدم حماية بمستوى المؤسسات.

إثبات ملكية

التوقيعان يثبتان أنك تملك التطبيق والجهاز معاً

أمان على السلسلة

كل عمليات التحقق محفوظة على البلوكتشين كسجل غير قابل للتغيير

هوية موحدة

هوية KYC واحدة تعمل عبر منتجات ChainGuard والدApps

أمان الخزنة

لا تُنفّذ أي أوامر خزنة دون تحقق من الربط، ما يمنع الاختراق

عملية التحقق على السلسلة

يتم التحقق من كل رابط هوية وتسجيله على البلوكتشين لضمان النزاهة

كيف تتم العملية

نُنشئ هيكل رسالة يحتوي نوع الإجراء ومعرّف الجلسة والطابع الزمني والـ nonce والعنوان، ثم نحصل على توقيع المحفظة والتطبيق ونستعيد المفاتيح العامة للتحقق من صحة العملية. تُحدّث الهوية في ملفك ويرتبط العنوان بالخزنة لضمان تتبع كامل.

إعداد الرسالة

صياغة JSON يتضمن نوع الحدث، sessionId، الطابع الزمني، nonce والعنوان.

استرجاع التوقيع

استخدام ECDSA لاسترجاع العناوين والتأكد من تطابقها.

التحقق من الجلسة

ضمان أن الطلب يأتي من جلسة مصادق عليها داخل حسابك.

تحديث الملف

تسجيل الربط كعنوان أساسي أو احتياطي مرتبط بالهوية KYC.

ربط الخزنة

تتطلب وظائف الخزنة الآن عنواناً مرتبطاً وتوقيع التطبيق قبل التنفيذ.

أهمية التحقق على السلسلة

يسمح التحقق على السلسلة بوجود سجل غير قابل للتلاعب لكل عملية ربط، ما يضمن الشفافية والامتثال ويمنع التزوير، ويمنح المؤسسات أدوات تدقيق موثوقة.

سجل غير قابل للتغيير

كل الروابط محفوظة بشكل دائم على البلوكتشين

إثبات تشفيري

التواقيع المستردة تثبت أصالة كل عملية

إمكانية تدقيق كاملة

سجل زمني كامل للأحداث لدعم المتطلبات الرقابية

مقاوم للتلاعب

لا يمكن تعديل البيانات أو تزوير الروابط بعد تسجيلها

ChainGuard مقارنة بالحلول التقليدية

تعرف كيف تتفوق ChainGuard Identity في إدارة الهوية على Web3

الميزة	الحلول التقليدية	ChainGuard Identity
التحقق من الهوية	خدمات منقسمة	منصة موحدة
التحقق على السلسلة	قليل أو معدوم	تحقق كامل على السلسلة
ربط ثلاثي	غير متاح	KYC + تطبيق + محفظة
تكامل الخزنة	يتطلب إعداداً منفصلاً	مضمن في الإعداد
دعم متعدد المنصات	مرتبط بمنصة محددة	يعمل في كل مكان
كفاءة التكلفة	رسوم متعددة	إعداد لمرة واحدة

مخطط الربط الثلاثي

رؤية مرئية لكيفية ترابط الهوية، التطبيق، والمحفظة

حساب KYC

هوية موثقة

تطبيق ChainGuard

جهاز 2FA

عنوان المحفظة

ربط على السلسلة

جميع المكونات الثلاثة مرتبطة تشفيرياً، ولا يمكن تنفيذ أي عملية خزنة دون موافقة التطبيق والمحفظة معاً.

خطوات إعداد بسيطة

أكمل إعداد ChainGuard Identity في أربع خطوات

حالات الاستخدام

طرق استخدام ChainGuard Identity عبر القطاعات

الامتثال المؤسسي

تلبي متطلبات التداول المؤسسي والعمليات العابرة للحدود مع سجلات تدقيق متاحة وKYC موثق.

وصول إلى منصات DeFi

ادخل بروتوكولات DeFi عالية القيمة بهوية موثقة، واسمح للمنصات بطلب أذونات على أساس ما توافق عليه.

أسواق NFT

اجرِ صفقات NFT عالية القيمة وأنت متحكم بالبيانات التي تشاركها مع السوق.

لماذا ChainGuard Identity مهم

طبقة الهوية التي تجمع الأمن والامتثال في Web3

مستقبل الاتصال في Web3 يقوم على التفاوض على الأذونات

النموذج الحالي حيث يطلب المستخدم وتمنح المنصة الوصول يختفي تدريجياً. الأطر التنظيمية مثل MiCA وقاعدة السفر تجعل مشاركة البيانات عملية ثنائية الاتجاه.

المنصات تحتاج بيانات موثوقة لتبقى قانونية، والمستخدمون يحتاجون رؤية كاملة حول من يطلب ماذا ولماذا. يجب أن تكون الأذونات قابلة للتدقيق ومحددة بالسياق.

ChainGuard Identity يدير هذه المعادلة: نحن نتفاوض مع المنصة، وأنت توافق ضمن بيئة ChainGuard الآمنة، دون أي موافقات محفظة خارجية أو نوافذ منبثقة غير ضرورية.

أمان بمستوى الشركات

الربط الثلاثي يضمن أن كل عملية خزنة تتطلب وجود المحفظة والتطبيق معاً، مع سجل تشفيري كامل لكل حدث.

جاهزية تنظيمية

كل العمليات مسجلة على السلسلة، ما يوفر سجلاً غير قابل للتلاعب للجهات الرقابية والتدقيقات الداخلية.

هوية موحدة في Web3

لا حاجة لإدارة هويات أو عمليات دخول متعددة. هوية ChainGuard تعمل عبر تطبيقاتنا وكل دApps المتكاملة.

سجل تدقيق غير قابل للتغيير

تتبع شفاف لجميع عمليات الهوية والربط والتصاريح، متوفر عند الطلب للمراجعة والامتثال.

آراء المستخدمين

ثقة المستخدمين والمؤسسات حول العالم

الغوص التقني العميق

تعرف على التفاصيل الهندسية خلف ChainGuard Identity

التحقق باستخدام ECDSA

كيفية التحقق من ملكية التطبيق والمحفظة بشكل مشفر

نمط Factory/Clone

نشر خزائن بكلفة منخفضة مع أمان كامل

معمارية Zero-Knowledge

حماية الخصوصية دون المساس بالامتثال

جاهز لتأمين هويتك على Web3؟

انضم إلى آلاف المستخدمين الذين يثقون بـ ChainGuard Identity للأمان والامتثال والاتصال السلس.

رسوم إعداد لمرة واحدة تشمل KYC + السنة الأولى مجاناً

الخطة الأساسية 8.75$ • الخطة الموسعة 22.50$ • خصم 75% لأول 10,000 مستخدم

ابدأ الإعداد الآن

هل ترغب بمعرفة المزيد؟

اطّلع على توثيقنا الشامل لاكتشاف التفاصيل التقنية، معمارية الأمان ودلائل التكامل.

زيارة التوثيق

ChainGuard Identity

تحقق KYC، إنشاء خزنة، وربط المحافظ مع التحقق على السلسلة

الأمان والامتثال

تكامل KYC

كيف يعمل KYC

أهمية KYC

هوية مثبتة

امتثال مؤسسي

هوية موحدة

إنشاء الخزنة ونشرها

نمط Factory/Clone (EIP-1167)

نشر على السلسلة

عقد متعدد التوقيع

بروتوكول ثلاثي

نشر منخفض التكلفة

خطوات إنشاء الخزنة

نشر عقد Factory

إنشاء وكيل مصغر

إعداد العناوين الثلاثة

ربط الهوية

ربط المحافظ والتحقق من الملكية

كيفية ربط المحفظة

1. توليد رمز QR

2. توقيع المحفظة

3. توقيع تطبيق ChainGuard

4. تحقق مزدوج

5. إكمال الربط

لماذا الربط مهم

إثبات ملكية

أمان على السلسلة

هوية موحدة

أمان الخزنة

عملية التحقق على السلسلة

كيف تتم العملية

إعداد الرسالة

استرجاع التوقيع

التحقق من الجلسة

تحديث الملف

ربط الخزنة

أهمية التحقق على السلسلة

سجل غير قابل للتغيير

إثبات تشفيري

إمكانية تدقيق كاملة

مقاوم للتلاعب

ChainGuard مقارنة بالحلول التقليدية

مخطط الربط الثلاثي

حساب KYC

تطبيق ChainGuard

عنوان المحفظة

خطوات إعداد بسيطة

تحميل التطبيق وإنشاء الحساب

ربط المحفظة وتحديث الملف

اختر مسارك

إكمال الإعداد

حالات الاستخدام

الامتثال المؤسسي

وصول إلى منصات DeFi

أسواق NFT

لماذا ChainGuard Identity مهم

مستقبل الاتصال في Web3 يقوم على التفاوض على الأذونات

أمان بمستوى الشركات

جاهزية تنظيمية

هوية موحدة في Web3

سجل تدقيق غير قابل للتغيير

آراء المستخدمين

الغوص التقني العميق

التحقق باستخدام ECDSA

نمط Factory/Clone

معمارية Zero-Knowledge

جاهز لتأمين هويتك على Web3؟

هل ترغب بمعرفة المزيد؟