One identity. One wallet. Multiple decentralized services.
QRX uses the chain as the trust and settlement layer while storage, web, AI and apps form a broader computer around it.
Consensus & value
QUB balances, transactions, staking, delegation, validator state, governance, native assets and finality are consensus-critical.
Service layers
QRX Drive, QRX-Net, advertising and useful compute are separately staged and service-funded rather than adding an automatic new issuance stream.
Local + distributed
Dynamic state such as current AURA provider load, cache contents or local GUI preferences can remain off-chain while still being signed and verified.
Demand-funded services, not hidden inflation.
Storage, compute and advertising use user/advertiser-funded escrow pools. Protocol emission remains separate.
| Layer | Funding source | Primary distribution |
|---|---|---|
| QRX Chain / staking | Protocol subsidy | Validator/staking economics under the chain rules |
| QRX Drive | Client storage contract | 97.5% provider budget · 2% resilience/repair · 0.5% development |
| AURA FastTrack | Job owner compute escrow | 90% provider · 9.5% network/fee pool · 0.5% development |
| Advertising | Advertiser campaign escrow | 55% delivery · 25% publisher · 15% viewer · 4.5% protocol/network · 0.5% development |
Platform status is explicit.
QRX does not treat a roadmap date as a consensus switch. DRIVE_V1, QRX_NET_V1, ADVERTISING_V1 and COMPUTE_POUC_V1 become active only after network readiness/soak criteria pass and governance commits a future activation height.
Read staged activation →