Buy & Swap Verge (XVG)

Five ways to mine one chain

Verge's official repository lists five mining algorithms: scrypt, x17, Lyra2rev2, myr-groestl and blake2s. Each takes a turn securing the same chain, which means miners using quite different hardware can all take part.

The wallet lets a miner pick an algorithm with a single setting (for example algo=x17), and the docs say most pools for all five can be found on public pool lists. Anyone who prefers not to join a pool can mine alone by setting gen=1 in the wallet configuration.^{[1], [2]}

Thirty-second blocks

The repository gives a block time of 30 seconds. That is far shorter than many older proof-of-work chains, so a payment is usually picked up into a block quickly.

A short block time is a design trade-off rather than a guarantee of finality. How many confirmations a receiver waits for is still their own choice, and exchanges set their own rules.^[3]

A supply that is already complete

The README states a total supply of 16,521,951,238 XVG and marks it "Complete". It also publishes the block-reward table that got there: 200,000 coins per block for the first 14,000 blocks, then 100,000, 50,000 and 25,000, and after that halving to 12,500 and 6,250 coins per block across later block ranges.

For a holder, the practical point is simple: the issuance schedule is published in the project's own source, and the project itself describes the supply as finished.

Reading the table end to end tells a clear story. Rewards were very large in the earliest blocks, stepped down quickly, and then followed a halving pattern familiar from other proof-of-work coins. The README lists the schedule as data rather than as a promise, which makes it a useful anchor for anyone checking supply claims made elsewhere. Pairing a published schedule with a short block time and several algorithms is the Verge recipe: quick blocks, a broad base of possible miners, and a total that does not change. Present-day network figures such as hash rate and difficulty sit outside the README; the project links to public dashboards for those, and they move every day.^{[4], [5]}

Messaging inside the wallet

Verge Secure Messaging (SMSG) is described in the repository as paid, encrypted wallet-to-wallet messaging. Two wallets share a chatkey and exchange messages without a separate chat app.

The documentation is deliberate about defaults. The desktop wallet, verge-qt, starts with SMSG on because it is normally used by people. The server daemon, verged, starts with SMSG off as a security measure for pools, exchanges and other infrastructure, and must be switched on with smsg=1.^{[6], [7]}

Open source, community-built

Verge is published under the MIT licence, and the README shows the code targets modern C++ (C++17/20). Wallet builds are released through the project's GitHub releases page.

The project describes itself as 100% open source and asks contributors to send fixes as pull requests on GitHub. The README credits a long list of named contributors and the wider Verge community.^{[8], [9]}

What remains unknown

Current hash rate per algorithm, active node count and how widely SMSG is used are UNKNOWN from the official sources used here; the project links to live dashboards for network figures.