The mainnet wallet pilot is live. After the testing and integration covered in our recent updates, the new bridge, token indexer and dedicated pilot wallet are now connected to mainnet for controlled testing.
We’re aiming to have private transfers ready to use in the pilot later today, 27 October, as we complete the remaining wallet checks. The full private-transfer path has already passed today’s stagenet rehearsal; the mainnet work now brings that progress into the pilot wallet experience.
Our focus remains making XMR20 tokens easier to use on native Monero, with public transfers, privacy by choice and a foundation for future trading on Monero Market. Alongside the pilot, we have shipped clearer return progress and incoming-XMR information on the website, and continued improving the Chrome extension.
The wallet pilot has reached mainnet
27 October
The pilot now has its mainnet custody program, XMR20 policy, synchronized token indexer and bridge service in place. A dedicated pilot extension connects those services to the wallet, turning the preparation described in Edition 07 into a running mainnet environment.
The first wallet smoke check registered a fresh, empty test account and scanned the mainnet token history successfully. This confirms that the pilot wallet can connect, register and read the new mainnet environment. Access is currently restricted to owner testing while we work through the complete user flows.
We are also refining the pilot wallet’s startup, layout and progress messages: bringing the new token controls closer to the main wallet actions, making longer operations easier to follow and working on opening the wallet in a full tab. These interface refinements are being checked in a separate candidate before installation.
What we checked
The recorded mainnet setup and opening completed on 27 October between approximately 16:26 and 17:00 UTC. The dedicated pilot wallet passed account registration and a mainnet scan with a fresh empty account. This milestone covers the running services and initial wallet connection; the pilot remains experimental and restricted to owner testing.
Private transfers are the next step in the pilot
27 October
We completed another full transfer rehearsal using public Monero stagenet and a local Solana validator. It followed the whole cycle: deposit tokens, receive a public token balance, send publicly, shield tokens, send privately, unshield and redeem through the bridge.
The private send used two Monero transactions, joined into one token transfer. Both are confirmed on stagenet and linked below. The bridge then completed the return after the required confirmations, and a repeated payout request was recognised without paying twice. At the end of the rehearsals, the tokens held in custody matched the outstanding public and shielded balances.
In everyday terms, public sends remain the straightforward default. Shield moves tokens into a private balance, Private send transfers from that balance, and Unshield returns tokens to the public balance. A private send from an already shielded balance uses two Monero transactions; shielding and unshielding are separate actions. The wallet shows the transaction count and network fees before approval.
We also tested the actual extension popup with fresh test accounts. Depositing, sending public tokens and redeeming all completed through the wallet, including the exact receiving balance on the local Solana validator. The private-transfer portion was exercised through the scripted wallet engine; completing the mainnet pilot wallet experience is the current focus.
Our target is to have private transfers ready in the pilot later today, 27 October, subject to the remaining wallet checks. We will report the completed mainnet result once that step is verified.
What we checked
The full scripted rehearsal passed on 27 October using Monero stagenet test coins and a local Solana validator. The actual popup separately passed deposit, public-send and redemption checks. Both private-send transactions were independently found in stagenet block 2,237,816. The explorer links confirm their inclusion on the test network; the recorded wallet and accounting tests establish how they were used in the rehearsal.
A quicker starting point and clearer balances
26–27 October
The website wallet and installed extension now use the XMR20 starting block as the default restore height. For an XMR20 wallet, that gives synchronization a more relevant starting point instead of scanning Monero’s entire history. An earlier height can still be chosen when restoring XMR received before XMR20 began.
Incoming XMR now has its own Receiving display, with the amount and confirmation progress shown separately from spendable funds. The website checks again while the wallet is visible and unlocked, and the extension catches up on recent progress when it is reopened.
Bridge and return screens also show exact token amounts with thousands separators. The full decimal amount stays visible so it is easier to read the value being moved and the amount expected at the destination. These improvements are available in the website wallet and the installed extension build.
What we checked
The website releases for the XMR20-start restore default, Receiving XMR and exact bridge amounts were published after Edition 07. Recorded checks cover restore-height persistence, explicit earlier-height choices, incoming-state display and public-node synchronization. Incoming-payment states were checked with fixtures; the recorded validation does not include a fresh funded incoming-payment test.
Follow a return from Monero to Solana
26–27 October
The return screen now shows four clear steps: the Monero record is published, ten Monero confirmations complete, the Solana approval is made, and the tokens arrive on Solana. A transaction link appears once the Monero record is available, so the on-chain progress can be checked directly.
This progress display is live on the website and included in the installed extension. Animated indicators help show the current stage, with reduced-motion preferences respected.
The latest installed extension build also adds a return-ready notification and an icon badge. The wallet can be closed while Monero confirms; when the return is ready, the notification points back to the wallet to resume. Signing stays in the open, unlocked wallet, with the user in control of continuing the return.
Together, these changes make the waiting period more understandable: you can see which network step is underway, open the Monero transaction and return to the wallet when the next action is ready.
What we checked
The website return-progress release was published on 27 October and passed 60 sampled file checks before and after publication. The installed extension build’s recorded suite passed 569 tests, with seven additional temporary-profile checks of the return watcher, notification badge and cleanup. Extension installation here refers to the local development build.
Evidence & release status
This edition covers work since Edition 07, recorded on 26–27 October. The mainnet wallet pilot is running for restricted owner testing, and its first recorded mainnet wallet check used an empty account. Private transfers in the pilot are targeted for later on 27 October, pending the remaining wallet checks. The completed private-transfer rehearsal used public Monero stagenet and a local Solana validator; the separate popup rehearsal covered deposits, public sends and redemptions. The pilot is experimental and has not undergone independent review. Website wallet changes are live; extension installation refers to local development builds. The linked GitHub research provides background rather than a new code publication today.
| Workstream | Recorded state |
|---|---|
| Mainnet wallet pilot | Live · controlled experimental testing |
| Private transfers | Full rehearsal passed · mainnet target today |
| Everyday wallet | Website live · extension build installed |
| Bridge experience | Progress display live · extension notifications added |
What comes next
The mainnet pilot is running, the complete transfer path has passed another rehearsal, and the everyday wallet is becoming clearer to use. The immediate goal is to finish the pilot wallet checks and verify private transfers on mainnet, then share the result in the next update.
Back to all updates