|
| 1 | +name: QELVA |
| 2 | +categories: |
| 3 | + - infrastructure |
| 4 | + - applications |
| 5 | + - defi |
| 6 | +usecases: |
| 7 | + - wallets |
| 8 | + - defi |
| 9 | + - infrastructure |
| 10 | + - dapps |
| 11 | + - operating-systems |
| 12 | + - mixing-service |
| 13 | +ecosystem: |
| 14 | + - solana |
| 15 | +description: >- |
| 16 | + Qelva is a privacy-native identity and transaction layer built for Solana. It |
| 17 | + introduces a seedless, multi-persona identity system combined with an |
| 18 | + intent-based execution model to eliminate the exposure of a user’s real wallet |
| 19 | + on-chain. |
| 20 | +
|
| 21 | + All cryptographic keys are generated and stored locally, while the |
| 22 | + architecture separates identity, intent, and execution to ensure strong |
| 23 | + metadata minimization. |
| 24 | +
|
| 25 | +
|
| 26 | + Qelva uses a relayer-based private execution pipeline, where user intents are |
| 27 | + validated off-chain and executed on-chain by a relayer, breaking the direct |
| 28 | + link between users and their transactions. The system incorporates Split & |
| 29 | + Delay obfuscation, persona-scoped wallets, and non-custodial authentication |
| 30 | + (username + PIN) to provide lightweight but practical privacy for everyday |
| 31 | + Solana usage. |
| 32 | +
|
| 33 | +
|
| 34 | + Qelva is designed for users and developers who want private transfers, persona |
| 35 | + separation, on-chain activity obfuscation, and a secure identity layer without |
| 36 | + seed phrase exposure or centralized trust. It serves as a foundation for |
| 37 | + privacy-preserving wallets, dApps, and automated systems on Solana. |
| 38 | +product_launch_day: 2026-01-07T17:00:00.000Z |
| 39 | +sunset: false |
| 40 | +assets_used: |
| 41 | + - sol |
| 42 | +have_token: true |
| 43 | +tokens: |
| 44 | + - symbol: QELVA |
| 45 | + name: QELVA |
| 46 | + contract_address: B4QGLZt7gqEj5dUcpBE4vb4MzrGQZmjmU2NVaGCdpump |
| 47 | + token_link: https://pump.fun/coin/B4QGLZt7gqEj5dUcpBE4vb4MzrGQZmjmU2NVaGCdpump |
| 48 | +links: |
| 49 | + web: https://www.qelva.io/ |
| 50 | + blog: "" |
| 51 | + github: https://github.com/QelvaLabs |
| 52 | + forum: "" |
| 53 | + docs: https://docs.qelva.io/ |
| 54 | + whitepaper: "" |
| 55 | + block_explorer: https://solscan.io/token/B4QGLZt7gqEj5dUcpBE4vb4MzrGQZmjmU2NVaGCdpump |
| 56 | + governance: "" |
| 57 | + twitter: https://x.com/QelvaPrivacy |
| 58 | + discord: "" |
| 59 | + telegram: "" |
| 60 | + lens: "" |
| 61 | + farcaster: "" |
| 62 | +project_phase: beta |
| 63 | +project_status: |
| 64 | + live_status: true |
| 65 | + mainnet: false |
| 66 | + testnet: false |
| 67 | + version: beta |
| 68 | +blockchain_features: |
| 69 | + opensource: true |
| 70 | + upgradability: |
| 71 | + enabled: false |
| 72 | + asset_custody_type: non-custody |
| 73 | + encryption: Local key generation, Ed25519 signatures, AES-GCM encryption, Argon2 |
| 74 | + key stretching, persona-scoped derivation, intent-signing, TLS-secured |
| 75 | + communication, and Split & Delay transaction obfuscation. |
| 76 | +storage: {} |
| 77 | +privacy_policy: |
| 78 | + defined: true |
| 79 | + link: https://www.qelva.io/privacy-policy |
| 80 | + data_usage: Used only for realtime request processing. No storage, no analytics, |
| 81 | + no resale, and no third-party sharing. All identities and keys remain |
| 82 | + on-device. |
| 83 | +compliance: GDPR-aligned data minimization, user-consent driven processing, |
| 84 | + non-custodial key handling, and zero-knowledge user profiling. |
| 85 | +tracebility: |
| 86 | + kyc: false |
| 87 | + tracked_data: None. No personal data, no identifiers, no IP logs, no analytics, |
| 88 | + no wallet tracking. |
| 89 | + sign_in_type_requirments: [] |
| 90 | +default_privacy: false |
| 91 | +audits: [] |
| 92 | +third_party_dependency: > |
| 93 | + Minimal third-party dependency. Qelva relies only on Solana RPC providers for |
| 94 | + on-chain execution. |
| 95 | +
|
| 96 | + All identity, keys, and user logic run fully client-side with no reliance on |
| 97 | + custodial or centralized services. |
| 98 | +social_trust: > |
| 99 | + No treasury or admin key exposure. Qelva uses a non-custodial model where |
| 100 | + users control their own keys. |
| 101 | +
|
| 102 | + Backend infrastructure is stateless and performs no sensitive operations. No |
| 103 | + multisig or privileged wallet required. |
| 104 | +technical_spof: > |
| 105 | + Failure of Solana RPC infrastructure may temporarily affect relayer |
| 106 | + execution. |
| 107 | +
|
| 108 | + No user keys or identities are at risk because all encryption and signing |
| 109 | + occur locally on the device. |
| 110 | +team: |
| 111 | + anonymous: true |
| 112 | + teammembers: [] |
| 113 | +funding: [] |
| 114 | +history: [] |
| 115 | +id: qelva |
0 commit comments