Spider Vault Architecture & Mainnet Migration

The Spider Vault and the mainnet migration framework are two of the foundational components of the LUXA Ecosystem. The first protects the cryptographic keys that give you control of your funds. The second defines how activity accumulated inside the Telegram Mini App is verified and settled on the native LUXA Network blockchain (Chain ID: luxa-1).

Together, they are built around three principles: client-side security, controlled identity verification, and resistance to large-scale Sybil activity.

1. The Spider Vault Architecture

The Spider Vault is a decentralized, non-custodial custody matrix integrated directly into the LUXA Telegram Mini App. It is designed around a zero-knowledge-oriented model: private secrets stay on the user's device rather than being sent to backend infrastructure or stored as plaintext database records.

Client-Side Key Isolation

Key generation, encryption, decryption and transaction signing all happen locally, inside the sandbox of the user's device — browser or mobile webview. This separates the blockchain interface from the sensitive cryptographic material that controls an account: the backend never needs access to your plaintext private key.

Multi-Vault Mesh

Each Telegram account can initialize and manage up to 10 independent vaults, each with its own native address in Bech32 format using the luxa1... prefix. Different blockchain identities can be kept independent from one another while remaining accessible from the same Mini App.

2. Private-Key Protection

PBKDF2 Key Derivation

Encrypted private-key material is protected with PBKDF2 (Password-Based Key Derivation Function 2). Your locally chosen numerical PIN is combined with a cryptographically generated salt and run through a large number of HMAC-SHA256 iterations, making repeated PIN guesses computationally expensive compared to a simple hash comparison. The overall security depends on the iteration count, salt generation, PIN entropy and implementation.

AES-256-GCM Authenticated Encryption

The resulting encrypted key payload is protected with AES-256-GCM (Galois/Counter Mode), which provides both confidentiality and integrity. Alongside encryption, GCM produces an authentication tag — if the ciphertext is altered, tag verification fails and the payload is not decrypted.

3. From Mined SHARD to Native LUXA

The migration framework bridges activity accumulated inside the Mini App with settlement on the LUXA Network (luxa-1) Layer 1. Conceptually:

The conversion rate is fixed by the protocol: 10,000 SHARD = 1 LUXA (the 10,000:1 Shard parity defined in White Paper v3.0). Eligible SHARD are burned at settlement and the equivalent native LUXA is issued on the LUXA Network (luxa-1). Settlement is processed once the three requirements below are met.

4. The Three Mainnet Migration Requirements

Requirement #1 — 60 Cumulative Validated Mining Days

A participant must accumulate 60 validated mining days. Days count cumulatively; maintaining a continuous daily streak is only necessary to preserve the streak multiplier.

Requirement #2 — Biometric Identity Verification

Migration to mainnet requires identity verification through Sumsub, including 3D liveness and document checks. The goal is to establish a one-person-to-one protocol identity relationship, making large-scale Sybil structures substantially harder to run.

Requirement #3 — 7,000,000 Active Pioneers Milestone

Settlement executes when the network reaches 7,000,000 active pioneer nodes, so that distribution is broad before wider liquidity opens. Certified accounts wait in the verified queue until then. The 8% / 4% protocol withholding and network gas apply at settlement (see Section 5).

The 8% LUXA withholding is directed to the Operational Mining Vault:

luxa1tfu3ct7t32k8ekdl86xraquwkut8j5a893pv59

5. Understanding the Settlement Calculation

With the fixed conversion rate of 10,000 SHARD per 1 LUXA, let S be eligible SHARD, G gross LUXA, F the protocol fee, and N net LUXA after the fee and initial withdrawal gas. Initial LUXA withdrawals incur an 8% withholding and 0.001 LUXA in gas; SHARD withdrawals incur a 4% withholding and 0.0005 LUXA in gas. Subsequent native L1 transfers have near-zero network fees from 0.0002 LUXA (200 uluxa).

A Practical Example

A participant with 100,000 eligible SHARD who has met the migration requirements receives:

• Gross conversion: 100,000 ÷ 10,000 = 10 LUXA
• Protocol withholding (8%): 10 × 0.08 = 0.8 LUXA
• Initial withdrawal gas: 0.001 LUXA
• Net after withholding and gas: 10 − 0.8 − 0.001 = 9.199 LUXA

6. Raqeem Exemption — Citizen Zero

Citizen Zero (#0) holds a protocol-level exemption from the standard 60-day mining requirement and Sumsub KYC. This exception does not waive the standard withholding or network gas.

7. Why the Two-Layer Security Model Matters

LUXA separates two problems that are often treated as one:

• Cryptographic security — the Spider Vault, protecting private-key material client-side with PBKDF2 and AES-256-GCM.
• Identity & Sybil resistance — the migration framework, controlling eligibility for mainnet settlement.

Conclusion

A participant accumulates 60 validated mining days, completes Sumsub identity verification, and waits for the network to reach 7,000,000 active pioneer nodes. Daily continuity is needed only to preserve the streak multiplier. At settlement, SHARD convert at the fixed rate of 10,000 SHARD per LUXA, subject to the standard withholding and applicable network gas. Citizen Zero (#0) is exempt from the 60-day and KYC requirements, but not from withholding or gas. The Spider Vault keeps key material on-device, protected by PBKDF2 and AES-256-GCM.