Monero Activated Its V15 Privacy and Efficiency Upgrade

Monero activated version 15 of its consensus rules at block 2,688,888 on August 13, 2022, completing the principal stage of a network upgrade that changed how the privacy-focused blockchain constructed and processed transactions.

The activation block carries a timestamp of 18:47:38 UTC and the hash beginning `6bd4550a`. Monero’s official repository identifies that height and date with a ring-size increase to 16, Bulletproofs+, view tags and an adjusted dynamic block-weight algorithm. Because activation was tied to block height rather than a fixed clock time, advance estimates of when it would occur were necessarily approximate.

The event mattered because these were consensus-level changes, not optional features available only to particular applications. Nodes and wallets needed compatible software to follow the upgraded network. The project described the hard fork as a coordinated, non-contentious protocol update rather than the creation of a separate cryptocurrency.

A larger ring for every spend

Monero increased its mandatory ring size from 11 to 16. A ring signature combines the output actually being spent with decoy outputs, allowing an outside observer to identify a set of possible signers without determining which member authorized the transaction.

Under the new rule, a ring contained the real output and 15 decoys. The larger set increased the number of plausible sources presented by each input, but it did not make privacy mathematically absolute. Effective protection also depended on decoy selection, user behavior, wallet implementation and information available outside the blockchain. Describing the change as a larger base anonymity set is therefore more precise than claiming that traceability became impossible.

Bulletproofs+ and view tags

The upgrade replaced the previous Bulletproofs construction with Bulletproofs+, the range-proof system used to demonstrate that confidential transaction amounts were valid without publicly revealing those amounts. Before activation, the Monero project estimated that the change would reduce a typical transaction’s size and improve typical verification performance by approximately 5% to 7%.

Those percentages were developer projections, not measurements of all transactions processed on August 13. Actual transaction weight and verification cost could vary with transaction structure and implementation.

View tags addressed a different cost: wallet synchronization. A tag attached to an output lets a wallet quickly reject many outputs that cannot belong to it before performing a more expensive check. The project estimated a 30% to 40% reduction in wallet-scanning time. Again, that was an anticipated typical improvement rather than a universal event-day benchmark.

The associated Fluorine Fermi software also included fee changes, an adjusted dynamic block-weight algorithm and multisignature security work. The software release notes distinguished these operational and wallet changes from the principal consensus additions. Version 0.18.0.0 had been released on July 19, while version 0.18.1.0 arrived on August 11 with compatibility updates for Ledger and Trezor hardware wallets.

Coordination was part of the risk

A hard fork requires infrastructure operators to update. Exchanges could suspend deposits and withdrawals around activation, while outdated nodes or wallets risked becoming incompatible with the accepted chain. The surviving records establish that block 2,688,888 was mined and that the v15 rules activated; they do not provide a complete census of upgraded nodes, wallets, exchanges or mining capacity at that moment.

Monero’s two-stage schedule temporarily allowed the older v14 transaction format to reduce user disruption. Protocol version 16 was scheduled for block 2,689,608 on August 14, when the old format would be prohibited. That second height was a distinct completion step and should not be collapsed into the August 13 activation.

The strict conclusion for August 13 is that Monero executed a coordinated privacy and efficiency upgrade at its predetermined height. Claims about the long-run privacy benefit, measured performance gains or universal service continuity required evidence beyond the activation block itself.