XMR20alphaminingexplorerupdatesdocs
All updates
Edition 02

Wallet progress, a first CLI, and native trading.

Faster wallet reopening, a separate command-line wallet candidate, and a closer look at the native market and historical Mordinals archive.

Welcome to the XMR20 community update for 21 October. Follow the progress across the project, the benefits for the community and the milestones taking shape.

Today’s development centres on the Chrome extension and a new CLI wallet candidate. We also revisit the native market and Mordinals website releases from 20 October, connecting today’s progress with the growing XMR20 ecosystem. Each section includes its release stage and supporting checks.

Keep verified history, spend less time reopening

21 October

The extension records a checked Monero creation height for each newly created account. This gives a new wallet a sensible starting point for scanning. Imported wallets keep their supplied restore height.

Verified native token history is saved alongside the wallet’s private scan checkpoint. The checkpoint is authenticated, versioned and checked against the chain before approvals are enabled, so reopening can reuse verified progress.

In the recorded unfunded browser run for extension 0.1.79, two fresh reopens reached ready in 4.1 and 5.3 seconds by reusing a verified checkpoint from a 1,571-block scan. These fixture-specific measurements show the benefit of retaining verified history; scan times depend on wallet history and network conditions.

The 0.1.80 development build also keeps Send and Max as separate actions during coin checks. Max calculates the available amount, and Send requires an explicit choice from the user. Exact amounts and fee information remain part of the approval flow.

What we checked

The locally installed 0.1.79 development build recorded 527 extension tests, 687 native/service/frontend tests and 17 browser storage checks. The subsequent 0.1.80 development build recorded 537 extension tests and 17 packaged browser checks. Each set belongs to its respective revision.

Next: Advance real-engine and funded wallet acceptance, building on exact amounts, protected token inputs and saved transaction history.

A separate wallet for the terminal

21 October

Our first 0.1.0 command-line wallet candidate brings XMR20 into a terminal workflow for local development review. It has its own package and reuses pinned wallet-engine components, with scanning and signing powered by a private headless Chromium process.

The candidate includes wallet creation and import, hidden password entry, addresses, native-token and XMR balance scanning, exact native amounts and Max, saved send history, transaction-inclusion checks and encrypted backups. Signing requires an explicit review of the recipient, amount and fee.

The first native-send milestone focuses on EXTREMIST with newly created wallets. Imported and restored wallets support scanning and balances; new sends from those wallets remain gated while cross-client pending-transaction handling is developed. This gives the candidate a defined scope for the next round of validation.

A disposable, unfunded public-chain run reached native readiness and reopened in 4.6 seconds. The package was also installed and checked outside the development repository on macOS, adding a practical installation milestone alongside the engine and terminal checks.

What we checked

The local development candidate passed nine unit tests, an actual Rust/WASM browser-journal integration test and nine terminal acceptance checks. Synthetic signing and transaction-history checks complement a read-only public-chain run. macOS installation was checked; funded mainnet sending is a planned validation milestone.

Next: Build toward a public wallet release through funded acceptance and continued validation of saved transaction handling.

Native XMR20 trading against XMR

20 October release · 21 October follow-up

The coordinated native release on 20 October brought the market interface, native services and compatible wallet package together. The public interface displayed the EXTREMIST/XMR pair and its Monero-wallet connection flow.

The native path is designed for Monero-only token sends and whole-lot trades, starting with EXTREMIST. Native recipients use a Monero wallet, and holders choose when to approve conversion of previously bridged holdings. The optional Solana bridge retains its disclosed single-operator trust model.

The website and services were released alongside round-trip validation in an isolated Solana VM and Monero test-chain environment. Settlement requires ten Monero confirmations. Funded mainnet validation is the next acceptance milestone.

Today’s saved-checkpoint work complements the market effort by allowing the wallet to reuse verified scanning progress. Together, the interface and wallet development move the native experience forward.

What we checked

The coordinated release recorded 70 passing live website file checks, plus native status and offer-book availability checks. These verified the published interface and services, alongside the separate test-chain round trip.

Next: Validate funded mainnet sends, conversion, trading and returns, and share the resulting milestones.

Historical Mordinals, back in view

20 October release recap

The historical Mordinals gallery was added to xmr20.org on 20 October. Visitors can explore the archive through the Art view, inspect an inscription’s original transaction and description, and switch back to token records within the same website.

The follow-up work focused on browsing: search focus styling, collection controls, compact visibility controls and a two-column mobile layout. Sensitive previews stay hidden until a visitor explicitly chooses to view them. The archive was added while preserving the existing wallet, market, launchpad, documentation and data routes.

Release checks covered catalog records, an individual inscription, filtering and image integrity, alongside desktop and mobile browsing. The gallery gives the community a direct way to explore Monero inscription history and follow each record back to its original transaction.

What we checked

The initial gallery release passed 117 source tests, followed by 118 for the content-visibility update. Publication checks compared staged and live files and verified catalog, item, filter and media behaviour.

Next: Continue improving discovery and browsing while keeping original transaction references and media integrity at the centre of the archive.

Earned holding points carry forward

20 October release recap

The rewards update retains previously earned holding credit and adds new verified periods. Prices and multipliers apply to new earning periods; intervals with incomplete history remain pending until they can be checked.

Published using the confirmed 19 October snapshot, the update provides a cumulative holding-credit ledger that can carry forward into future reward calculations.

What we checked

The release record reports 99 tests and checks of the published page and data. The public Rewards page explains retained credit and pending periods.

Next: Build on the holding ledger with future verified earning periods and clear credit tracking.

Evidence & release status

This edition brings together dated project records available on 21 October. The table and downloadable editorial summary show each workstream’s release stage and recorded checks, from locally installed development builds to published website features.

WorkstreamRecorded state
Chrome extensionInstalled development build
CLI walletLocal candidate
Native marketMarket interface live
Mordinals archiveLive website
EcosystemLive rewards update

What comes next

We are building a daily record of meaningful progress, with a short community post linking to each edition. Earlier updates remain available in the archive so you can follow the work over time.

Back to all updates