The Monzero pull request to Cake Wallet, and monero_c
Where it stands
As of 6 November 2026 the pull request is prepared and has not been submitted: nothing has been pushed to GitHub and no fork has been made. Searches on GitHub that day found no issue, pull request or code in cake-tech/cake_wallet that mentions Monzero, and no issue or pull request about it in monero_c. This page describes the change as it is meant to be sent.
The title and the base
The pull request is titled monzero: add Monzero (XMZ) wallet support. It is built on Cake Wallet commit 1772b7624, “Strip EVM chain id from QR scanned into swap receive address”, pull request 3756, merged on 24 October 2026. The six patches have been checked to apply cleanly there and to reproduce the branch exactly.
The six commits
1. Add Monzero (XMZ) wallet support. The integration itself: 134 files and about 23,200 lines, most of them the new cw_monzero package and its word lists. The integration guide has what it adds.
2. Open wallets normally instead of Wownero's deprecation path. The copied Wownero code threw a deprecation error on every open; Monzero now retries the way Monero does, a bounded number of times.
3. Drop duplicate and unused imports from the generated proxy. The generated Monzero glue now analyses with no warnings.
4. Record Dart analysis results and local build notes. A notes file, MONZERO.md, from the build machine. The pull request text offers to drop or trim it.
5. Report the end of sync the way the Monero code does. A reopened wallet no longer stays at “Attempting sync”.
6. Support BIP39 seeds the way the Monero code does. BIP39 create and restore on Monero's path, with nine new tests of the wallet service; the BIP39 guide has what that means.
Our notes also list eleven local commits on top of these six — the Flutter 3.47 fixes, a development bundle id, an iOS Xcode project, notes on an iOS device build and a rebuild on Monzero v1.0.0 among them. They stay on the build machine and are not part of the pull request.
What has to land first: monero_c
Cake Wallet does not build each coin's wallet code itself. It uses monero_c, which builds Monero's wallet library for each Monero-family coin as a C library with Dart bindings, and it pins monero_c to one commit through scripts/prepare_moneroc.sh. The commit it pins has no Monzero in it.
The change that adds Monzero to monero_c — a C wrapper with the MONZERO_ prefix, Monero's series of 21 patches rebased onto Monzero, and the Dart API lib/monzero.dart — is prepared as a separate pull request to monero_c, and has not been submitted either. It has to be merged, or at least open, before this one makes sense. Then two pins in Cake Wallet move to the monero_c commit that has it: the monero override in pubspec_overrides.yaml and MONERO_C_REF in the prepare script. Until they do, cw_monzero cannot find its library.
What else is open before sending
Our notes for the pull request list three things to settle first.
The icons. Placeholders, to be replaced with the official Monzero logo.
The build notes. MONZERO.md is written for our build machine, with its local paths; it is to be dropped or cut down to what matters upstream.
The bundling step. The script and the Xcode build phase that carry Homebrew's libraries into the macOS app exist only because our library was linked against them. Cake Wallet builds monero_c statically, so the maintainers may prefer to drop both; the pull request should say so, or remove them first.
Two more turned up when we checked the public pages on 6 November 2026.
The upstream link. The pull request text links Monzero's repository as Nightglass-Protocol1/monzero, which GitHub showed as archived that day; monzero.org now points to Nightglass-Protocol1/Monzero-source.
The Monzero version. Monzero's v1.0.0 moved its network to hard fork 17 at block 21,000, and the README of its source repository says every node and wallet must run v1.0.0 or later. The tests in the pull request text ran at height 15,704, before that block.
What Cake Wallet's maintainers will decide
Whether Cake Wallet adds a coin is a product decision, not a question of whether the code works: Cake Wallet adds coins selectively. The pull request is written as a proposal, and our notes expect questions about the coin, its node infrastructure and who maintains the integration. Today the patch ships a single default node, node.monzero.org; the nodes guide has what that connection is.
The Monzero pull request to Cake Wallet, and monero_c: questions
Has the Monzero pull request been submitted to Cake Wallet?
Not as of 6 November 2026. The six commits are prepared and checked to apply cleanly on Cake Wallet commit 1772b7624, but nothing has been pushed or forked, and GitHub showed no Monzero issue or pull request in cake-tech/cake_wallet that day.
What is monero_c, and why does the Monzero integration need it?
monero_c is the project Cake Wallet uses to build Monero's wallet code for each Monero-family coin as a C library with Dart bindings. The commit Cake Wallet pins has no Monzero target, so a separate monero_c change, prepared as its own pull request, has to land first.
Will Cake Wallet add Monzero?
That is Cake Wallet's decision to make. It adds coins selectively, and the pull request is written as a proposal; the maintainers can be expected to ask about the coin, its nodes and who maintains the integration.
Source: The Monzero pull request text and our notes for it; GitHub searches of cake-tech/cake_wallet and MrCyjaneK/monero_c checked against the source
More Monzero guides
What the Monzero patch adds to Cake Wallet
A six-commit patch adds Monzero (XMZ) to Cake Wallet as a new wallet type: a copy of the Wownero integration that follows Monero where Wownero falls short.
Monzero BIP39 seeds: one phrase, the same keys as Monero
In Cake Wallet's Monzero patch a BIP39 phrase uses Monero's path, m/44'/128'/0'/0/0, so one phrase gives the same keys on both coins. Why Monzero needs its own.
Building Cake Wallet with Monzero on macOS
Our build of Cake Wallet with the Monzero patch on an M1 Mac: a macOS Release app, Dart analysis, 13 passing tests, an in-app check, and what is not tested.