Public launch: Qwertycoin starts at network height 0 with a fresh genesis, no premine and no imported balances from earlier chains.Download information updated: 14 September 2026.Hello Bitcointalk,
I'm Alex (nnian). Some of you will remember me from Qwertycoin's earlier years. I'm bringing the project back with a new codebase, a new network and a reworked implementation of EPoSe.
Qwertycoin combines private payments and open CPU mining with rewards for providing verifiable network service. The new core builds on Monero 0.18.x, uses RandomX proof of work and adds EPoSe: a service-node reward system with on-chain registration, signed service evidence and deterministic payment rules.
The Web Wallet, Qwertycoin GUI 2.0.4, Core v2.0.4 command-line tools and explorer are available. The current software is offered for public testing; direct downloads and verification information are listed below.
Questions from former QWC users, miners, node operators and developers are welcome.
The public network starts exactly at height 0. It has a fresh genesis and does not continue the legacy Qwertycoin blockchain.Old-chain balances and transaction history are not carried over. Restoring a legacy wallet's keys does not transfer its coins to the new network. Previous development and rehearsal chains, including all of their mining rewards, are discarded for the public launch.
There will be no swap of legacy QWC wallet balances into the new network.If you participated in the 2025 token swap, please contact me by private message here on Bitcointalk so we can review your situation and work together on a solution.Use the current Qwertycoin software and separate data directories. Keep backups of legacy wallets and keys. Historical download links and exchange markets must not be assumed to support this network.
- A Monero-based core. The implementation builds on Monero's transaction and privacy mechanisms. Upstream authorship and license notices are retained.
- EPoSe service rewards. Operators can earn a protocol-defined allocation by meeting admission and service-qualification rules.
- RandomX proof of work. Mining produces blocks and determines chain selection. RandomX is designed around general-purpose CPUs.
- No central Sentinel deciding payments. Validators derive service-node eligibility and scheduled payments from canonical chain data.
- Fresh network identity. The new chain has its own genesis, network identity, address prefixes and data directories. QWC HF17 rules activate from genesis.
The original EPoSe vision and whitepaper came from Xecute. The current implementation develops that service-reward idea into rules that validators can check from the blockchain.
EPoSe means
Egalitarian Proof of Service. It adds service qualification and reward allocation to the proof-of-work chain.
- Register and qualify for admission. An operator registers a service identity, reward destination and endpoint binding, and completes the required RandomX admission work.
- Provide service evidence. Deterministically selected verifiers perform protocol-defined service challenges. Authenticated responses and signed receipts provide the evidence.
- Settle qualification. Evidence included in the canonical chain determines which nodes qualify for the relevant epoch.
- Receive scheduled rewards. A later payout epoch uses the settled qualified set to select recipients. Validators check the required service allocation in each block.
Proof of work remains responsible for block production and chain selection. EPoSe does not require staking QWC and does not replace mining.Epochs contain 720 blocks, approximately 24 hours at the target interval. Epoch 0 is enrollment, epoch 1 is the first service period, and height 1,440 is the earliest possible service payout. Payment still requires a qualified recipient. These are block-height rules; actual elapsed time depends on mining.
The target verifier committee size is nine. The quorum is two thirds of the actual committee, rounded up: six signatures for a full nine-member committee. Smaller committees therefore operate with fewer verifiers during network bootstrap.
Service evidence covers the challenges defined by the protocol. It does not certify every aspect of an operator's infrastructure or prove that each service identity belongs to a different person.
EPoSe consensus rules in compact formThe website publishes the following mathematical summary of quorum, qualification, recipient rotation and service-reward allocation:
q_E = ceil(2 * min(9, N_E - 1) / 3)
a_(s,r) = |A_(s,r) intersect C_(s,r)|
s in Q_E iff sum_(r=0..2) 1[a_(s,r) >= q_E] >= 2
pi_(E+1)(h) = rank_H(Q_E)[(h - start(E+1)) mod |Q_E|]
R_EPoSe(h) = floor(subsidy(h) * 1000 / 10000)
N_E is the frozen member count; C_(s,r) is the verifier committee excluding the subject node; A_(s,r) contains unique valid signed attestations. A registered node needs quorum in at least two of three service rounds to enter the qualified set Q_E. The protocol orders this set using its domain-separated consensus hash H and rotates recipients using a zero-based index within the payout epoch.
The quorum expression assumes N_E >= 1; recipient rotation requires a non-empty qualified set. The subsidy calculation uses atomic units and excludes transaction fees. Warm-up and the other admission and validation rules still apply.
View the original EPoSe formula graphicEPoSe overview |
Protocol documentation
These values describe the Core v2.0.4 network configuration. The parameter manifest for this release is linked below.
| Ticker | QWC |
| Network start | Fresh genesis at block 0 |
| Premine | None |
| Legacy balance swap | None |
| Mining | RandomX proof of work |
| Target block interval | 120 seconds |
| Decimal places | 8 |
| Emission supply constant | 184,467,440.73709551 QWC |
| Tail emission | 0.3 QWC per target minute; 0.6 QWC per target block |
| Service allocation | 10% of block subsidy when a qualified payee exists |
| Miner allocation | Remaining subsidy plus 100% of transaction fees |
| No qualified service payee | Full subsidy and transaction fees go to the miner |
| EPoSe epoch | 720 blocks |
| Earliest service payout | Height 1,440, subject to qualification |
The emission supply constant is not a maximum supply cap. Tail emission continues after the declining emission schedule reaches its floor. The service allocation divides the block subsidy; it does not add a second subsidy. Transaction fees are existing coins transferred to the miner.
No premine. No private mining period before public participation. No imported snapshot balances. The public network starts at height 0. Earlier rehearsal blocks and their rewards are excluded from the new chain.
Core v2.0.4 network parameter manifest
The core inherits Monero's approach to private transactions: one-time destination outputs, ring signatures and confidential transaction amounts.
EPoSe also needs publicly verifiable service identities, qualification evidence and reward assignments. Those service records should not be treated as private wallet activity.
The EPoSe payment design uses scoped payment proofs and normal one-time reward outputs. It does not require publishing the reward wallet's private view key. Independent review of the new proof and its integration remains part of release validation.
Use a dedicated reward wallet when operating a service node. Keep wallet seeds and private spend/view keys private; service-node identity keys are separate operational credentials.
Desktop wallet — Qwertycoin GUI 2.0.4Download the graphical wallet for your platform:
GUI SHA256SUMS |
GUI release notesCore command-line tools — v2.0.4These packages contain qwertycoind, qwertycoin-wallet-cli and qwertycoin-wallet-rpc, together with the required portable libraries and release documentation.
Core SHA256SUMS |
Core release notesPlatform requirements- macOS: Apple Silicon, macOS 15 or newer. The linked macOS packages are ARM64 builds.
- Linux: x86_64. The release states a GLIBC 2.35 compatibility ceiling; Core additionally specifies GLIBCXX 3.4.30.
- Windows: x86_64. The GUI includes a portable Qt 5 runtime. The Core release was tested on the Windows Server 2025 build runner; broader compatibility with older Windows versions is not claimed.
Verify your downloadDownload the SHA256SUMS file from the same repository and release as your archive, then compare its SHA-256 checksum before extracting it. GUI and Core have separate checksum files.
Signing status: Linux and Windows packages are unsigned. macOS binaries are ad-hoc signed, without Developer ID signing or notarization. SHA-256 checksums verify file integrity; they do not authenticate the publisher.
Web Walletwallet.qwertycoin.orgUse the browser wallet to create a new 25-word wallet, restore a current-network seed, import a private spend key or open a watch-only wallet. Restoration does not transfer legacy or discarded rehearsal-chain balances into the new network.
Web Wallet source |
Self-hosting informationPublic testing and release statusThe website lists these builds for the first public test phase. The Core release notes still mark the EPoSe audit/readiness gate as "no-go", with further evidence and independent reviews outstanding. This is an audit status, not a switch that disables EPoSe in the running software.
Core release status |
Current validation record
MinersQWC uses RandomX proof of work. Follow the current mining information and make sure your software targets the new network. Mining pools will be identified when their compatibility with this network is confirmed.
Mining overviewService-node operatorsUse the EPoSe operator guide for admission, endpoint configuration, identity persistence and reward-wallet setup. A Service Node requires an unpruned, synchronized daemon and a reachable public service endpoint. Starting a daemon alone does not guarantee qualification or rewards.
Operator guide for Core v2.0.4 |
Latest operator documentationDevelopers and reviewersReview the source, reproduce builds and test EPoSe state transitions and wallet behavior. Reproducible bug reports should identify the commit, platform, network and steps to reproduce the issue. Never include wallet secrets.
Report issues and contributeReturning community membersJoin the discussion here. If you took part in the 2025 token swap, send me a private message so we can work on a solution. There is no swap of legacy wallet balances.
WebsiteWeb WalletBlock ExplorerDesktop wallet downloads — GUI 2.0.4Core and CLI downloads — v2.0.4Core repository — main branchWeb Wallet repositoryQwertycoin on XQwertycoin on TelegramDiscordHistorical exchange and price-tracker entries do not establish support for the current network. Confirmed integrations will identify the network they support. There are no exchange-listing promises in this announcement.
Thank you to everyone who contributed to Qwertycoin over the years, and to the upstream developers whose work this codebase builds on.
If you want to help build and test the next Qwertycoin network, join the discussion here.
Alex / nnian 
