> For the complete documentation index, see [llms.txt](https://hyperalpha.gitbook.io/hyperalpha-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperalpha.gitbook.io/hyperalpha-docs/platform-features/account-infrastructure.md). # Account Infrastructure HyperAlpha (hyperalpha.org) implements a cutting-edge "Web3 Sovereign Identity + High-Performance Matching Engine" hybrid account model. This dual-layer architecture guarantees that users retain 100% decentralized ownership of their cryptographic assets while providing the millisecond response speeds and institutional-grade stability required by advanced trading systems. ### 1. Authentication Logic: Connect-to-Sign (Non-Custodial) HyperAlpha completely bypasses cumbersome traditional database registration, utilizing a streamlined cryptographic signature authentication layer: * Decentralized Asset Handshake: Users connect their preferred Web3 wallets (MetaMask, OKX Wallet, etc.) and execute a standard, non-custodial cryptographic signature to instantly generate a unique encrypted account profile. * Granular Settlement Tracking (UID & CLOID): Every authenticated profile is assigned a unique UID (User ID). Concurrently, our proprietary CLOID (Custom Logical Order ID) technology tracks every transaction stream at the microsecond level, ensuring real-time commission clearing and precise order synchronization. * Exclusive Tiered Onboarding: To preserve network bandwidth and guarantee the high quality of the trading ecosystem, HyperAlpha enforces a strict Invitation-Only access barrier. New participants must acquire a valid, exclusive Referral Code from an active member to initialize the trading engine. ### 2. 30-Day Extended Session Architecture To satisfy the grueling demands of professional discretionary traders and asset allocators monitoring markets 24/7/365, HyperAlpha features an optimized JWT (JSON Web Token) session caching layer: * 30-Day Signature Exemption: Once the initial wallet signature authentication succeeds, the secure session token remains active for a continuous 30-day window. * Frictionless Strategy Recalibration: Within this 30-day active envelope, users can modify copy-trading risk margins, toggle leverage metrics, or switch algorithmic models without repeatedly waking wallet extensions for signatures—eliminating latency bottlenecks during high-volatility events. * High-Intensity Expiration Defense: If an account registers zero interactive telemetry for 30 consecutive days, the secure token is automatically invalidated. The user must re-execute a cryptographic wallet signature to guard against local device security breaches. ### 3. High-Performance Referrals: The "14+3" Pruning & Re-Activation Protocol To prevent inactive or algorithmic sybil accounts from wasting premium server bandwidth and hoarding dormant referral slots, HyperAlpha enforces a strict "14+3" Accountability Review. While we restrict our elite infrastructure to serious market participants, we provide a programmatic rehabilitation path for active traders. #### The Accountability Review Every newly generated referral allocation is subject to an automated performance and volume audit exactly 14 days post-issuance. #### Revocation Criteria When the audit window initializes, an account's invitation privileges will be immediately set to 【REVOKED】 if BOTH of the following quantitative conditions are met: 1. Sub-Standard Volume: The account's cumulative on-chain trading volume since registration is below $500,000 USD (failing to breach the baseline V2 Trader tier). 2. Liquidity Stagnation: The aggregate trading activity of the primary account holder and their direct invitees registers zero volume for 3 consecutive days. #### Consequences of Revocation * Existing referral codes assigned to the account become temporarily invalid and cannot be bound by any new users. * The account holder temporarily loses the privilege to onboard new members, establish trading cohorts, or clear multi-tier ecosystem referral bonuses. * *Note: To guarantee absolute asset sovereignty, revocation never interrupts or liquidates active Copy Matrix configurations or ongoing manual Trade executions currently deployed by the user.* #### Programmatic Re-Activation Protocol HyperAlpha rewards genuine contributions to order-book depth. If an account's invitation status is revoked under the pruning protocol, it can be unlocked via our Automated Rehabilitation Gateway: * Trigger Threshold: The moment the account's cumulative transaction metrics (via manual Trade execution or automated Copy Matrix strategies) reaches and surpasses the $500,000 USD volume benchmark, an automated system update is initialized. * Full Re-Activation: Upon crossing the threshold, the system instantly restores the account's full privileges to invite new members, re-enabling referral code generation and granting full access to HyperAlpha's growth ecosystem and multi-tier commission settlements. > ⚙️ System Architecture Objective: HyperAlpha’s high-concurrency clearing infrastructure and millisecond-level proxy routing networks are highly constrained ledger resources. This rigid framework ensures that our technical alpha is continuously reserved for Serious Traders who actively inject liquidity into the $HYPE ecosystem and treat trading with institutional discipline. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://hyperalpha.gitbook.io/hyperalpha-docs/platform-features/account-infrastructure.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.