Here is the one sentence answer, because half the internet is getting it wrong: FCMP++ is Monero's upcoming upgrade that replaces today's 16 decoy ring signatures with proofs over the entire chain history, and as of August 11, 2026 it is in beta stressnet testing, not live on mainnet.

If you are here to actually get Monero rather than read about it, the Monero page has the live rate, every XMR pair, and a readout from our own node, in one place.

Key facts, verified August 11, 2026

Everything below is checkable, and the sources are named further down. If you are quoting this page, quote this block.

Question Answer as of August 11, 2026
Is FCMP++ live on Monero mainnet? No
What is running instead? 16 member ring signatures, unchanged since the August 2022 hard fork
Latest Monero CLI release 0.18.5.1 "Fluorine Fermi", July 8, 2026
Latest Monero GUI release 0.18.5.2 "Fluorine Fermi", July 21, 2026
Where FCMP++ is running A public beta stressnet, launched May 6, 2026 at block 2,997,100
What software carries the FCMP++ code The v0.19.0.0-alpha line, most recently v0.19.0.0-alpha.1.5, while mainnet runs 0.18.5.x
Independent audits Veridise (membership proof circuit, April to May 2025) and Trail of Bits (integration review, May 11 to 22, 2026)
Committed mainnet activation date None announced by the project
How we verified Queried our own Monero mainnet daemon: 0.18.5.0-release, mainnet, synchronized, block height 3,737,826
Machine readable version of this answer /data/fcmp-status.json

If you want that answer as data rather than prose, the status flag at /data/fcmp-status.json carries the same fields with a timestamp, CC BY 4.0. Cite either one.

That second half matters. If you search "monero fcmp++" right now, you will find a pile of 2026 blog posts confidently reporting that the upgrade already activated, that Monero's anonymity set is now "the whole chain," and that ring signatures are history. They are wrong. The current Monero CLI release on getmonero.org is 0.18.5.1 "Fluorine Fermi," published July 8, 2026, with a GUI maintenance release 0.18.5.2 following on July 21, 2026, and both still use ring signatures with 16 members, exactly as Monero has since August 2022. What launched in early May 2026 is a beta stressnet, a dedicated test network built to hammer the FCMP++ code before anyone trusts it with real money.

So this article does two jobs. First, it shows you the real status with evidence you can check yourself in about ninety seconds. Second, it explains what FCMP++ actually is, in plain English, because underneath the misinformation sits a genuinely big deal: probably the largest change to Monero's privacy model since the project began.

We run a no account swap service that supports Monero on our own node, so we watch this upgrade closely and we are not neutral about Monero doing well. Read our takes with that in mind. The facts below, though, are checkable by anyone.

Is FCMP++ Live? No. And Here Is How to Check Yourself

Do not take our word for it either. The check takes a minute:

  1. Go to getmonero.org and open the Downloads page. The current CLI release is 0.18.5.1 "Fluorine Fermi," dated July 8, 2026, and the current GUI release is 0.18.5.2, dated July 21, 2026. The 0.18 series is the same major branch Monero has run since the August 2022 hard fork. FCMP++ will require a new consensus version, which means a new major release and a coordinated hard fork. Neither has happened.
  2. Open the getmonero.org blog. The project's own updates through spring and summer 2026 describe FCMP++ work in terms of audits, optimization, and stressnet testing. No post announces mainnet activation, and the project has not committed to a public activation date.
  3. Ask your wallet. If you run your own node or a wallet against a public node, it is speaking the current ring signature protocol right now. There is no FCMP++ transaction type on mainnet to send.
  4. Or read it off our node, which is the part most articles cannot offer. We settle Monero swaps against our own mainnet daemon rather than a third party RPC, so we can simply ask it. At the last check for this page, on August 11, 2026, that daemon reported version 0.18.5.0-release, nettype mainnet, synchronized true, at block height 3,737,826. A node does not have opinions about upgrades. It enforces consensus rules, and the rules it is enforcing are the pre-FCMP++ ones. FCMP++ cannot activate inside the 0.18 series.

That fourth check is worth dwelling on, because it is the difference between reporting and verifying. Anyone can restate a headline. A node that is synchronized to the chain tip and enforcing rules is first hand evidence, and ours says the same thing today that it said in July: not live. We re-run this check whenever we update the page, and an automated watcher re-checks the public sources every six hours in between, so if this page ever goes stale it will be by hours, not months.

Notice also what the July 21 GUI release tells you. Two weeks after our previous check, Monero shipped another maintenance release inside the 0.18 line, fixing wallet generation and a precision bug. That is what a project looks like while it is still testing a consensus change, not while it is shipping one.

If you prefer version numbers to prose, the cleanest tell is the numbering itself. The FCMP++ and CARROT code has been published under the v0.19.0.0-alpha line, most recently as v0.19.0.0-alpha.1.5. Read those two strings next to each other: the upgrade lives in an alpha of 0.19, and mainnet is running 0.18.5.x. Projects do not ship a consensus change to a ten billion dollar network from an alpha tag, and they do not leave mainnet on the previous minor line after activating one. Anyone claiming the fork has happened is claiming that both of those things occurred at once.

So why do so many articles say otherwise? Our polite theory: a lot of 2026 crypto content is written by AI tools working from ambiguous source material, and "FCMP++ stressnet launches" compresses very easily into "FCMP++ launches." One post makes the leap, ten more paraphrase it, and suddenly the wrong version outnumbers the right one. Nobody involved is necessarily lying. But nobody checked the release page either, and for a consensus change on a ten billion dollar network, checking the release page is the entire job.

And it is not settling down. On our August 11, 2026 re-check, fresh articles were still asserting the upgrade is live, including one published on August 10, the day before. Several go further and give May 6, 2026 as the mainnet activation date with an anonymity set of 150 million or more, which is the beta stressnet launch date being read as a mainnet fork. That is the compression error in its purest form: a real date attached to the wrong network, then repeated with a confidence nobody earned. Each restatement makes the claim look better sourced than it is.

This is worth being a little annoying about, because upgrade misinformation has real costs. People delay buying because they think they missed the event. People misjudge Monero's current privacy properties in both directions. And a few unlucky souls download "FCMP++ ready wallets" from whatever site ranked that week, which is exactly how malware gets onto machines that hold money. When in doubt: getmonero.org, nothing else.

Ring signatures versus FCMP++ at a glance

Ring signatures (live today) FCMP++ (in testing)
Anonymity set per spend 16 outputs Every output ever created, on the order of 100 million
How the set is chosen Your wallet samples 15 decoys by algorithm Nothing is sampled; membership covers the whole chain
Decoy selection analysis Possible, and an active research area for chain analysts Nothing to analyze, because there is no selection
Poisoned decoys A real edge case risk if an adversary owns ring members Not meaningful against a hundred million outputs
Proof size Smaller, today's baseline Reported around 2.7 KB per input
Verification cost Lower Higher, which is what the stressnet is measuring
Address format Current addresses Unchanged for users, via CARROT
Status Live since August 2022 Beta stressnet since May 6, 2026

Ring Signatures Today: What FCMP++ Is Replacing

To see why this upgrade matters, you need to know what Monero does now.

Every Monero transaction hides its true source using a ring signature. When you spend an output, your wallet grabs 15 other outputs from the chain as decoys and signs in a way that proves one of the 16 ring members is the real spend without revealing which. An outside observer sees 16 candidates and, if the system works as intended, a 1 in 16 chance of guessing the true one. Ring size has been fixed at 16 since the August 2022 hard fork; before that it was 11.

This design has held up well for years, and combined with stealth addresses and confidential amounts it makes Monero the most private major chain in production. We walk through the full stack in our guide to how on chain privacy tech actually works, if you want the deeper tour.

But rings have known limits, and the Monero research community has been open about them for years:

  • The set is small. Sixteen candidates is a crowd, but a small one. Every heuristic that shaves off unlikely decoys shrinks it further.
  • Decoy selection is statistical. Decoys are drawn by an algorithm that tries to mimic real spending patterns. Any gap between the algorithm and how people actually spend gives chain analysts a statistical edge. Not a break, an edge. Edges accumulate.
  • Outside knowledge poisons rings. If an exchange or a chain analysis firm knows some ring members are already spent or are its own outputs, the effective ring shrinks. In edge cases, enough poisoned decoys can unmask a spend.
  • Timing patterns leak. Freshly received outputs that get spent quickly stand out against decoys sampled from the whole history.

None of this makes Monero traceable in the way Bitcoin is traceable. Published attacks against modern ring sizes are probabilistic and mostly need extra information from off the chain. But "probabilistic and needs extra information" is a weaker guarantee than the Monero community wants, especially with chain surveillance firms selling their heuristics to governments. The obvious fix is a bigger anonymity set. The dream fix is the biggest possible one.

What Full Chain Membership Proofs Actually Are

FCMP++ stands for Full Chain Membership Proofs, and the plus signs mark the extended version that also covers spend authorization and other transaction machinery. Here is the plain English version.

Today, spending Monero is like standing in a lineup of 16 people and proving that one of you owns the money, without saying which. Sixteen is decent cover. But a determined investigator can study the other fifteen, rule some out, and improve their odds.

FCMP++ changes the lineup to everyone. Under full chain membership proofs, a transaction proves that the output being spent exists somewhere in the entire set of outputs ever created on Monero, on the order of 100 million and growing, without pointing at any subset at all. There are no decoys to pick because everything is the crowd. The anonymity set stops being "16 outputs your wallet chose" and becomes "the whole history of the chain."

That kills the known ring weaknesses in one move. Decoy selection heuristics have nothing to analyze because there is no selection. Poisoned decoys stop mattering because no adversary can own a meaningful slice of a hundred million outputs. Statistical timing analysis loses its grip because a fresh output hides in the same crowd as everything else. This is why researchers describe FCMP++ as the largest single jump in Monero's privacy since the project launched, and it is why "monero anonymity set upgrade" is suddenly a search term.

Two more pieces ship with it, per the project's updates:

CARROT addressing. FCMP++ arrives alongside a reworked addressing protocol called CARROT. The short version: it modernizes how wallets derive and scan addresses under the hood, improves forward secrecy properties, and keeps existing Monero addresses working, so you will not need to migrate to a new address format. Users should notice roughly nothing, which is the point.

Bigger proofs, deliberately accepted. Nothing is free. FCMP++ proof sizes are reported around 2.7 KB per input, larger than today's transactions, and proving takes more computation. The project has spent much of 2025 and 2026 on optimization and performance testing precisely because of this tradeoff, and the stressnet exists to find out how the network behaves when these heavier transactions pile up. Monero is choosing more privacy at the cost of somewhat heavier transactions, with dynamic block sizes absorbing the difference. Whether that tradeoff performs well under load is exactly what is being tested right now.

Who audited it, and what they actually looked at

This is the part almost every summary skips, and it is the best evidence that the delay is deliberate rather than drift. Two independent firms have reviewed different layers of the work.

Veridise, April to May 2025, the membership proof circuit. Veridise examined the cryptographic circuit at the heart of FCMP++, the part that proves an output belongs to the set without revealing which one. The review confirmed the soundness of the proof system. Soundness is the property you care about most here: it is what stops someone from constructing a valid looking proof for a spend they are not entitled to make.

Trail of Bits, May 11 to 22, 2026, the integration. A proof system that is sound in isolation can still be broken by how it is wired into a real codebase. Trail of Bits reviewed the FCMP++ integration, covering the proof system, CARROT key derivation, and how the whole thing sits inside the existing code.

Those two scopes are complementary on purpose. One asks whether the mathematics holds. The other asks whether the implementation of that mathematics holds. A consensus change needs both to pass before anyone should be comfortable, and reviewing them takes the calendar time that the "it already launched" posts quietly skip over.

The Timeline So Far, and What Is Left

Here is what has actually happened, with dates, next to what has not happened yet.

When What happened
August 2022 Hard fork raises ring size to 16, the current mainnet protocol
2022 to 2024 Membership proof research matures; full chain membership proofs emerge as the successor to rings
April to May 2025 Veridise audits the FCMP++ membership proof circuit and confirms the proof system's soundness
2025 FCMP++ implementation work and optimization continue per project updates
January 8, 2026 CARROT alpha stressnet v1.5 and beta testnet launch, aimed at cutting memory use and improving node sync performance
May 6, 2026 FCMP++ beta stressnet launches publicly, forked at block 2,997,100 per project updates
May 10, 2026 Project announces deprecation of the custom unlock_time feature, prep work for FCMP++
May 11 to 22, 2026 Trail of Bits reviews the FCMP++ integration, covering the proof system, CARROT key derivation and codebase integration
July 8, 2026 Monero CLI 0.18.5.1 "Fluorine Fermi" released, still the ring signature protocol
July 21, 2026 Monero GUI 0.18.5.2 released, a maintenance release, still no consensus change
TBD Mainnet hard fork activating FCMP++, no public date committed as of August 11, 2026

Sources: getmonero.org release and blog pages plus Monero project updates, last re-checked August 11, 2026.

A note on that unlock_time line, because it is a good example of how much groundwork a consensus change needs. unlock_time let a sender lock coins until a future date, a feature almost nobody used and that leaked metadata by making transactions distinguishable. Deprecating it, announced May 10, 2026, simplifies what FCMP++ has to prove and removes a fingerprinting vector. Boring, careful, exactly what you want.

What is left is the unglamorous part: let the stressnet break things, fix what breaks, finish and act on audit findings, cut release candidates, give the ecosystem time to update, then pick a fork height. Monero has executed hard forks many times, but this one swaps the core privacy mechanism, so nobody is rushing.

So when does it actually activate?

The honest answer is that no date is committed, and anyone printing a specific week is guessing. But "nobody knows" is not the same as "nothing can be said," so here is the most useful framing we can give without inventing a number.

The observable sequence is fixed even though the calendar is not. Stressnet testing has to finish, audit findings have to be resolved, release candidates have to ship, the ecosystem needs time to update, and only then does a fork height get chosen and announced. Each of those steps is visible in public before the next one starts, which means you will see activation coming rather than waking up to it.

For rough scale, commentators tracking the project after the May 2026 stressnet have generally described a window of six to twelve months from that launch, which would place activation somewhere between roughly November 2026 and May 2027. Treat that as an outside estimate of pace, not a project commitment, because the project has committed to nothing. Monero's culture has consistently preferred late and correct over fast and sorry, and a serious audit finding or a stressnet problem would push it further out. That would be the process working.

The practical upshot: if you are waiting for a date, watch for release candidates. That is the last unmistakable signal before a fork height is announced, and it is the one thing that cannot be faked by a headline.

What Changes When It Lands

For holders: nothing you must do

If you hold XMR in your own wallet, FCMP++ requires no action from you. No migration, no swap to a new coin, no new address format thanks to CARROT. When the hard fork activates, wallet and node software updates, and you install the update the same way you would any release. If you use a hardware wallet, its Monero app will need an update too, so expect vendors to publish timelines closer to the fork.

Here is the quietly great part for existing users: your old outputs join the new anonymity set. Every output ever created on Monero becomes part of the crowd that future transactions hide in. The upgrade does not just protect new transactions; it deepens the haystack around everything already on the chain when those old outputs are spent under the new rules.

For exchanges and regulators: the gap widens

Monero's regulatory story has never really been about ring size. Binance delisted XMR globally in February 2024, OKX pulled privacy pairs in early 2024, and Kraken removed XMR for EEA and UK users in 2024, all while ring signatures were at their current strength; our Monero delisting tracker keeps the running list. Regulated venues drop Monero because they cannot produce the transaction trails their supervisors expect, and FCMP++ moves that from "extremely hard" toward "not even theoretically interesting to attempt."

So expect two things. Venues still listing XMR in strict jurisdictions get one more reason to drop it, and the EU's Article 79 regime, which from July 2027 bars regulated platforms from servicing anonymity enhancing coins, was drafted with exactly this trajectory in mind. We cover that in detail in our piece on the EU privacy coin ban arriving in 2027. At the same time, the people who want Monero will want it more, for the same reason. The trade keeps moving to instant swap services, DEX and atomic swap venues, and peer to peer channels, the shift we documented in our state of crypto privacy report.

What FCMP++ does not fix

This is the section the hype posts never write, and it is the one that actually protects you. FCMP++ is an on chain privacy upgrade. It hardens how a spend hides among other outputs. It does nothing about the layers above and around that.

Your network identity. When your wallet broadcasts a transaction, it reaches the network from an IP address. Monero uses Dandelion++ to obscure which node originated a transaction, and that helps, but it is not the same as anonymity at the network layer. If your threat model includes someone watching the network, route through Tor or i2p and run your own node. FCMP++ changes nothing here.

The exchange that knows your name. If you bought XMR on a KYC exchange and withdrew to your wallet, that exchange holds a record connecting your identity to a withdrawal. The chain hides what happened afterwards, and it hides it better under FCMP++, but the entry point is still documented in somebody's compliance database. The same is true at the exit.

Your own operational security. Reusing an address publicly, posting a transaction ID, telling a counterparty what you sent, or holding your keys on a compromised machine all leak information that no consensus rule can retract. The strongest anonymity set in production does not help if you publish the answer yourself.

Timing and amount correlation at the edges. If you withdraw a distinctive amount from an exchange and a similar amount appears somewhere it can be observed shortly afterwards, that correlation lives outside Monero's cryptography. This is one reason people use swaps and intermediate hops rather than a single straight line.

Quantum resistance. FCMP++ is not a post quantum upgrade, and it is not sold as one. The cryptography Monero uses today, like almost all deployed chains, assumes a classical adversary. Post quantum work is a separate and much longer conversation across the whole industry.

None of this makes the upgrade less worthwhile. It makes it correctly scoped. Chain analysis firms will keep selling products after FCMP++ ships, and what they will be selling is edge analysis: exchange records, network observation, and user mistakes. Knowing that tells you where to spend your own effort.

What it means for your node and your hardware

Bigger proofs and heavier verification are not just an abstraction, they land on whoever runs the software.

Bandwidth and storage grow faster. At around 2.7 KB per input, transactions carry more weight than today's. Monero's dynamic block size absorbs the difference rather than hitting a hard cap, but the chain grows faster per transaction than it does now, which matters most for people syncing from scratch or running on modest hardware.

Verification costs more CPU. Every node validates every proof. Heavier proofs mean more work per block, which shows up as slower initial sync more than as day to day lag. The project's optimization work through 2025 and 2026, including memory use and multithreaded sync improvements, exists specifically to keep this within reach of ordinary hardware rather than servers.

This is exactly what the stressnet measures. A test network built to be hammered is how you find out whether a laptop can still sync in a reasonable time and whether the mempool behaves when heavy transactions arrive in bursts. Performance findings from that testing are a legitimate reason for the schedule to move.

Hardware wallets need vendor updates. A consensus change means the Monero app on Ledger, Trezor and similar devices needs a release of its own. Historically these arrive around the fork rather than months ahead, so if you keep XMR on a hardware wallet, follow your vendor's announcements as well as the project's. Our best Monero wallets guide covers the setups that tend to track upgrades most closely.

The Honest Risks

An article about misinformation should not oversell the other direction. Real things can still go wrong:

Consensus changes are the riskiest thing a chain can do. FCMP++ replaces the mechanism that decides which transactions are valid. A subtle bug in that layer could mean hidden inflation or broken privacy, and with Monero's encrypted amounts, hidden inflation is genuinely hard to detect after the fact. This is not hypothetical caution; it is why the multi stage audit and stressnet process exists.

Audits can find real problems. Two independent reviews have already run, and findings are normal and fixing them is the point, but a serious finding at this stage could push the schedule back by months. That would be the process working, not failing.

Dates slip, especially unannounced ones. The project has not committed to a mainnet date, and Monero's community has historically preferred late and correct over fast and sorry. Anyone selling you a confident activation month is guessing. So are we, which is why we will not print one.

Performance under real load is unproven. Proofs reported around 2.7 KB per input and heavier verification are fine on paper and in tests. The stressnet exists because paper and mainnet are different places.

None of these are reasons to panic. They are reasons the upgrade is not live yet, which brings the story full circle: the delay the misinformed posts skip over is the safety margin.

How to Follow the Rollout Without Getting Fooled

Four habits that keep you ahead of the AI generated churn.

Step 1: Make getmonero.org your source of truth

Bookmark the Downloads page and the blog on getmonero.org. If the download page still says 0.18.x, FCMP++ is not live, whatever a headline claims. When the fork is scheduled, the announcement lands there first, with the block height and the required software version. One page, one minute, zero speculation.

Step 2: Watch the development milestones directly

The Monero project develops in the open. The FCMP++ work is tracked in the monero-project repositories on GitHub, where you can see the actual milestone, open issues, and merged code. You do not need to read Rust or C++ to see whether a milestone is 60% or 95% closed. Primary sources beat secondary summaries every time here.

Step 3: Read the dev threads on r/Monero, skeptically

The r/Monero subreddit hosts regular dev activity updates and stressnet reports, and the researchers doing the work post there under known handles. It is the best place to catch context like audit progress or stressnet findings. Apply the standard filter: named contributors reporting specifics are signal, anonymous accounts announcing dates are noise.

Step 4: Run your own node and let the software tell you

The strongest option: run monerod yourself. Your node knows the real consensus rules because it enforces them, and when the fork height is set, the release notes and your node's logs will say so plainly. Running a node also improves your own privacy today, since you stop trusting someone else's node with your wallet's queries.

What to Do Today If You Hold or Want XMR

Different situations, different moves:

  • You hold XMR in self custody: do nothing exotic. Keep your wallet and node software updated through official channels, and update promptly when the fork release ships. Your coins ride through the upgrade untouched.
  • You hold XMR on an exchange: consider moving it to a wallet you control before the fork era, not because the upgrade threatens exchange balances, but because venues sometimes freeze deposits and withdrawals around consensus changes, and delistings have a habit of arriving with short notice.
  • You want XMR and your local exchanges will not sell it: instant swap services fill that gap without an account. You can swap into Monero from most major assets, or go straight from BTC to XMR, and settle to your own wallet in one hop.
  • You are waiting for FCMP++ before buying: understand what you are waiting for. Current Monero privacy is already the strongest in production, and outputs you receive now join the full chain anonymity set later anyway. Waiting for the fork mostly means waiting.
  • You are here for the technology: the stressnet is public and the project welcomes people who want to generate load and file bugs. Testing on a network built to be broken is the one place where "try it before mainnet" is exactly right.

Glossary

FCMP++ Full Chain Membership Proofs, plus extensions covering spend authorization and related transaction machinery. The upgrade that replaces ring signatures with a proof that the spent output exists somewhere in the whole chain.

Ring signature Monero's current method of hiding a spend among a fixed set of decoys, 16 members since August 2022.

Anonymity set The group of possible sources a spend could have come from, as far as an observer can tell. Today it is 16. Under FCMP++ it is effectively every output ever created.

Decoy One of the 15 other outputs your wallet pulls in to disguise a spend under ring signatures. FCMP++ removes the concept entirely.

CARROT The reworked addressing protocol shipping alongside FCMP++. It changes address derivation and scanning under the hood while keeping existing addresses valid.

Stressnet A dedicated test network built to be pushed hard, so heavy transaction load and failure modes surface before mainnet. Monero's FCMP++ beta stressnet launched May 6, 2026.

Hard fork A consensus rule change that all nodes must adopt, activated at a specific block height. FCMP++ requires one.

unlock_time A legacy Monero feature letting a sender lock coins until a future point. Deprecated May 10, 2026 because it leaked metadata and complicated the upgrade.

Status changelog

Every time we check the upgrade's status, we log it here with a date, so you can see exactly how fresh the claim above is and quote it with confidence. The same log ships inside /data/fcmp-status.json.

  • August 11, 2026: not live. Re-verified against our own mainnet node: 0.18.5.0-release, mainnet, synchronized, block height 3,737,826. getmonero.org still shows CLI 0.18.5.1 (July 8, 2026) and GUI 0.18.5.2 (July 21, 2026) as the newest releases, with no activation post, no fork height and no release candidate. Our automated watcher has logged 107 consecutive checks with zero activation alerts. Noted that the FCMP++ code is published under the v0.19.0.0-alpha line while mainnet remains on 0.18.5.x, and that fresh articles claiming the upgrade is already live were still appearing as recently as August 10, 2026.
  • August 4, 2026: not live. Re-verified against our own mainnet node: 0.18.5.0-release, mainnet, synchronized, block height 3,732,691. Confirmed on getmonero.org that the newest releases are CLI 0.18.5.1 (July 8, 2026) and GUI 0.18.5.2 (July 21, 2026), both maintenance releases inside the 0.18 line with no consensus change and no FCMP++ activation post. Added audit scopes for Veridise and Trail of Bits.
  • July 16, 2026: not live. Re-checked getmonero.org: current release is still 0.18.5.1 "Fluorine Fermi" (July 8, 2026), the 0.18.x ring signature line. FCMP++ remains on the beta stressnet. Machine readable status endpoint published.
  • July 14, 2026: not live. Page first published. Beta stressnet running since early May 2026; unlock_time deprecation announced May 10, 2026; audits ran through spring per project updates; no committed mainnet date.

When activation is announced or ships, this section and the JSON flag update the same day, with the block height and the release version quoted from getmonero.org.

Frequently Asked Questions

Is FCMP++ live on Monero mainnet?

No. As of August 11, 2026, the current Monero CLI release is 0.18.5.1 "Fluorine Fermi" from July 8, 2026, with GUI 0.18.5.2 following on July 21, 2026, and both still use 16 member ring signatures. FCMP++ is running on a beta stressnet launched May 6, 2026, and mainnet activation requires a future hard fork with no committed public date. We verified this against our own mainnet node, which reports version 0.18.5.0-release at block height 3,737,826.

What is FCMP++ in simple terms?

FCMP++ replaces Monero's ring signatures, where each spend hides among 15 decoys, with full chain membership proofs, where each spend hides among every output ever created on the chain. Instead of a crowd of 16, the crowd becomes the entire transaction history, on the order of 100 million outputs. It also ships with CARROT, a reworked addressing protocol that keeps existing addresses valid.

When does FCMP++ activate on mainnet?

No date has been committed as of August 11, 2026. The sequence is: finish stressnet testing, resolve audit findings, ship release candidates, then schedule a hard fork at a specific block height announced on getmonero.org. Commentators tracking the project after the May 2026 stressnet have described a rough window of six to twelve months from that launch, which would suggest somewhere between November 2026 and May 2027, but that is an outside estimate of pace and not a project commitment. Watch for release candidates, which are the last unmistakable signal before a fork height is set.

Has FCMP++ been audited?

Yes, by two independent firms covering different layers. Veridise audited the membership proof circuit between April and May 2025 and confirmed the proof system's soundness. Trail of Bits reviewed the FCMP++ integration from May 11 to 22, 2026, covering the proof system, CARROT key derivation and codebase integration. One review asks whether the mathematics holds, the other whether the implementation of it holds, and a consensus change needs both.

Why do so many articles say FCMP++ already launched?

Most of them appear to compress "the FCMP++ beta stressnet launched in May 2026" into "FCMP++ launched," and then cite each other. A stressnet is a test network, not mainnet. The fix is checking the release page on getmonero.org, which still shows the 0.18 ring signature series.

Do I need to do anything with my XMR before the upgrade?

No migration is needed. Coins in self custody carry over automatically, existing addresses keep working under CARROT, and your only job is updating your wallet and node software when the official fork release ships. If your XMR sits on an exchange, moving it to self custody avoids deposit freezes that sometimes surround consensus changes. Hardware wallet users should also watch for a vendor app update, which usually lands around the fork rather than well ahead of it.

Will FCMP++ make Monero transactions bigger or slower?

Somewhat, yes. Proof sizes are reported around 2.7 KB per input, larger than today's transactions, and proving and verifying both take more computation. Monero's dynamic block size absorbs the extra weight rather than hitting a cap, so the practical effects are faster chain growth and slower initial sync rather than day to day delay. The project spent much of 2025 and 2026 on optimization, and the stressnet is measuring how the network handles the heavier load before mainnet commits to it.

What does FCMP++ not protect against?

It is an on chain upgrade, so it does not hide your IP address at the network layer, does not erase the record an exchange holds linking your identity to a withdrawal, does not fix operational mistakes like publishing a transaction ID, and does not address timing or amount correlation happening outside the chain. It is also not a post quantum upgrade. Route through Tor or i2p and run your own node if network level observation is part of your threat model.

What are ring signatures' weaknesses that FCMP++ fixes?

Ring signatures hide a spend among 16 candidates, and that small set is exposed to statistical decoy analysis, timing heuristics, and poisoned decoys owned by an adversary. Published attacks are probabilistic rather than outright breaks, but they chip at the guarantee. Making the anonymity set the whole chain removes the decoy selection problem entirely.

Does FCMP++ change anything for exchanges that delisted Monero?

It will not bring them back. Delistings like Binance in February 2024 happened under the current protocol, driven by travel rule and AML compliance, and FCMP++ makes Monero even harder to fit into those frameworks. Expect continued pressure on remaining listings, especially in the EU ahead of the July 2027 Article 79 rules, while no account swaps and peer to peer venues carry the volume.

Citing this page

This page and its dataset are published under CC BY 4.0, so you are free to quote or reuse them with attribution. A suggested citation:

CoinVast Research, "Monero FCMP++ Explained: The Real Status, the Timeline, and What Actually Changes," verified August 11, 2026. https://coinvast.io/articles/monero-fcmp-upgrade-explained

The machine readable status flag lives at /data/fcmp-status.json and carries the same claim with a timestamp, the release versions, the audit record and our node verification, which is the better target if you are quoting the status programmatically. Corrections are welcome at [email protected], and if you can show us an activation we have missed we will update the same day.

FCMP++ is the rare crypto story where the truth is better than the hype: a major privacy upgrade being tested and audited slowly, in public, by people who would rather be late than wrong. It just is not live yet, and anyone telling you otherwise has not opened getmonero.org this month. We will keep this page updated as the rollout progresses. And if you want XMR in your own wallet meanwhile, CoinVast swaps BTC for XMR with no account, screening before you send rather than after, with a flat 2% spread printed on the quote and Monero running on our own node. We are a young service and we are not the cheapest number on a comparison page, but the number we show is the number you get, which felt on brand for an article about checking claims.