RandomX PoW
Miners produce blocks, secure ordering, and keep QWC permissionless.
QWC Mainnet. Privacy-focused. RandomX-powered. Built around decentralized Proof of Service (EPoSe).
Mainnet live now. Wallet, source, and ecosystem releases follow in controlled stages.
Miners produce blocks, secure ordering, and keep QWC permissionless.
Registered Service Nodes prove useful network service and enter consensus-enforced reward rotation.
About Qwertycoin
Qwertycoin is a new mainnet chain derived from the Monero v0.18.5.1 codebase, with QWC parameters, HF17-era privacy technology, RandomX proof of work, and EPoSe from genesis.
The current QWC chain is mainnet. Active operators, miners, and Service Nodes are hardening the live network.
QWC starts from Monero v0.18.5.1 with HF17-era privacy technology and QWC-specific parameters from genesis.
RandomX miners produce blocks, secure ordering, and keep chain security separate from service-node reward eligibility.
Registered Service Nodes prove useful network service through deterministic attestations before they can enter reward rotation.
Service Nodes do not lock stake, produce blocks, or vote on chain history. RandomX proof of work remains responsible for consensus ordering.
The website is the first public mainnet component. Web wallet beta, public source release, and broader tooling follow in staged releases.
EPoSe v2
No central Sentinel decides which Service Nodes receive rewards. Chain state and EPoSe rules determine qualification, payee selection, and reward validity.
Registered Service Nodes provide useful QWC network service during each epoch.
Deterministically assigned verifier committees check service activity and create signed attestations.
Qualification is finalized before deterministic payee selection can affect service rewards.
EPoSe origin
The original EPoSe vision and Qwertycoin service-layer whitepaper work came from Xecute, a historical honorary member of the Qwertycoin project. QWC finally carries that plan forward as a decentralized chain-state implementation.
Service Nodes
A normal node validates, syncs, and relays. A Service Node adds a registered identity, public service commitment, proof/attestation flow, qualification, and reward eligibility.
| Normal node | Service Node |
|---|---|
| Synchronizes the blockchain, validates blocks, relays transactions, and contributes peer capacity. | Does everything a normal node does, plus registers a service identity and participates in the EPoSe service-reward protocol. |
| No reward path beyond mining if the operator also mines blocks. | Can become qualified for deterministic service rewards after registration and attestations. |
| No stake or validator-council role. | Also not a proof-of-stake validator. RandomX miners still produce blocks. |
Synchronizes the blockchain, validates blocks, relays transactions, and contributes peer capacity.
Does everything a normal node does, plus registers a service identity and participates in the EPoSe service-reward protocol.
No reward path beyond mining if the operator also mines blocks.
Can become qualified for deterministic service rewards after registration and attestations.
No stake or validator-council role.
Also not a proof-of-stake validator. RandomX miners still produce blocks.
Mining
Old CryptoNight and old mining pool instructions are legacy material. QWC uses RandomX proof of work with a 120 second block target.
Mining is open to anyone who can run compatible RandomX mining software against a QWC node or pool. Active pool documentation will be linked only after it is verified for v2.
QWC is not proof of stake. Service Nodes receive service rewards only through the EPoSe layer; they do not replace proof-of-work block production.
Releases
Mainnet release communication is staged: website first, web wallet beta next, public QWC source after that, then broader wallet and ecosystem tooling.
The browser wallet beta is the active wallet path for the current QWC mainnet. Early beta - use with care.
Desktop wallets remain planned and should ship only after the v2 transaction path is hardened.
QWC source publication follows the website and wallet rollout. The public legacy repository is not linked as the v2 core build path.
Mainnet
Live observer metrics for the current QWC mainnet.
EPoSe FAQ
No. RandomX miners still produce blocks and secure the chain. EPoSe adds a service-reward layer for registered infrastructure.
An epoch is a fixed block period used by EPoSe to measure and finalize service activity. The current QWC parameter is 720 blocks, roughly 24 hours.
Qualified means a registered Service Node has enough valid attestations in the relevant epoch to become reward-eligible.
No central server. Qualification is derived deterministically from QWC chain state and valid EPoSe registration and attestation data.
No QWC staking role is defined in the current EPoSe core. Service Nodes register a service identity and admission proof; they are not proof-of-stake validators.
The protocol can represent multiple Service Node identities. Admission proof makes cheap identity creation harder, but it is not a promise that one human equals one node.
Service Nodes do not lock stake, produce blocks, or vote on chain history. RandomX proof of work remains responsible for block production and ordering.
Roadmap
Current product and release milestones for the QWC mainnet, without artificial quarter dates.
New QWC chain, modern Monero-derived base, RandomX, HF17 from genesis, QWC parameters and branding.
Service-node registration, RandomX-bound admission, attestations, qualification, deterministic reward rotation, and consensus-enforced service rewards.
EPoSe qualification, service-node validation, explorer, CI/release hardening, long-running network observation, multi-node validation, and security review preparation.
Web/PWA wallet development, desktop GUI planning, developer APIs, service-node tooling, mining documentation, and operator guides.
Public QWC source release, reproducible builds, developer documentation, SDK/API access, and broader community tooling.
Additional decentralized services, light-wallet infrastructure, archival services, and encrypted distributed object storage.
History
The legacy Qwertycoin ecosystem matters, but it must not be confused with Qwertycoin.
QWC began as a CryptoNote-based community privacy coin with early wallet, explorer, community, and infrastructure efforts.
The project explored fair mining, service rewards, wallets, nodes, infrastructure, and voting concepts. Xecute's EPoSe work remains part of that origin story.
The legacy chain and ecosystem diverged from what QWC needs today. Exchange, price, wallet, and old source claims from that era are not reused as current facts.
Qwertycoin returns as a new mainnet chain with RandomX, modern privacy technology, QWC HF17 rules, and EPoSe v2.
Developers
Public QWC source publication follows the website and wallet rollout. Until then, legacy public repositories are not the QWC core build path.
Public release in preparation. The release will include source access, reproducible build notes, developer documentation, and operator guidance.
Older public repositories may remain available for history, but they must not be treated as the current QWC core source.
Service-node registration, attestation, qualification, and reward tooling will be documented with the public QWC source release.
Community
Only active and controlled resources are linked from this mainnet website. Legacy docs and old wallet/download/exchange links remain excluded until they are updated or clearly archived.