GeroWallet 2.7 Is Live: Everything in Our Biggest Release

GeroWallet 2.7 is the largest release in the wallet's history: the source code is public, the entire interface has been rebuilt on a new design language, Midnight arrives on mainnet, and a deep security-hardening pass backed by two external audit rounds lands alongside them. It also introduces the Gero Companion assistant, Gero's own swap aggregator, cross-device signing, Sign in with Google, and an early preview of Bitcoin support. This article walks through what is in the release and, just as importantly, what is still limited.

TL;DR

GeroWallet 2.7.0 shipped on 19 August 2026. The full source is open on GitHub under Apache 2.0, the interface was rebuilt from scratch, Midnight is on mainnet with DUST generation inside the wallet, swaps run on Gero's own aggregator, and two external audit rounds landed with Argon2id key encryption. Most headline features roll out gradually behind feature flags, so not every wallet sees everything on day one.

Where GeroWallet fits: update the extension from the Chrome Web Store and check the release notes for the full list, or install GeroWallet if you are new.

First, the honest framing

We would rather be boring and accurate than exciting and wrong, so read this section before the rest.

2.7 is released. Version 2.7.0 was published on 19 August 2026, and the full wallet source is public at github.com/Gero-Labs/gerowallet.

Features roll out in stages. Most of the headline items are controlled by remote feature flags, which means they switch on gradually rather than all at once. Having 2.7 in your extension does not automatically mean seeing every feature in it on day one.

Bitcoin is testnet-only. It is in the release, but it is not somewhere to hold or spend real BTC yet.

The wallet's source code is public

This is the item that is genuinely live, and it is the one we think matters most.

The complete wallet, a Vue and TypeScript Chrome extension, is published on GitHub. Anyone can read how keys are stored, how transactions are built, and what the extension sends over the network. The repository ships a SECURITY.md with a responsible disclosure process including an email fallback, a code of conduct, contributing guidelines, and issue and pull request templates. The continuous integration workflows were hardened for public exposure, with fork pull request guards and GitHub Actions pinned to specific commit hashes.

One precision worth stating plainly: the licence is Apache 2.0, copyright A.D. Labs. That is a genuine OSI-approved open source licence, not a look-but-do-not-touch arrangement. You get full read and audit rights, and you can fork, modify and build on the code within the terms of the licence.

For a non-custodial wallet, that read access is the point. "Your keys never leave your device" stops being a claim and becomes something you can check.

A complete visual rebuild

The interface has been rebuilt on a single design-token layer rather than patched. Four "liquid-glass" surface materials, self-hosted fonts, and a unified type ramp replace the previous mix, and every dashboard table and widget was moved across and tuned for readability against automated contrast checks.

The most useful change is chain-accent theming. One accent colour re-themes the whole application depending on which chain you are on: Cardano cyan, Apex teal and red, Bitcoin orange, Midnight violet. When a wallet spans four chains, knowing at a glance which one you are operating on is a safety feature rather than a decorative one.

Onboarding was rebuilt too. Create, Restore and Pair now live inline in a single welcome card with a two-step selector, blockchain first and then network. New wallets no longer open into a blank screen either: there is a guided first-deposit path, a market-first view, and a clear sense of where to start.

Midnight on mainnet

Midnight joins the wallet on mainnet as well as the test networks, with full cross-chain dashboard parity. The substantive change is that DUST generation moves inside the wallet, so there is no more bouncing out to an external portal.

You will be able to generate DUST from native NIGHT on Midnight and from cNIGHT held on your Cardano wallets, with on-chain registration, deregistration and destination-migration flows handled inline. Gero-sponsored collateral covers wallets that lack a pure-ADA UTxO, which is a common dead end during registration. Duplicate registrations, which quietly split your DUST generation, are detected automatically with a guided path to consolidate them, and the DUST battery reflects both native and cNIGHT-backed generation rather than half the picture.

The part we are most pleased with is the choice of where zero-knowledge proofs are generated: Gero Cloud, a local proof server on your own machine, or Arkhia zkPaaS with your own key, switchable from the dashboard and the side panel. Cross-Device Proving goes further, letting your own desktop generate the proofs for your phone's Midnight sends over an end-to-end encrypted channel, where Gero's infrastructure only ever handles ciphertext.

Midnight is an independent privacy chain that we integrate. We did not build it and we do not own it.

Gero Companion

The Companion is an in-wallet assistant available in the side panel and the dashboard. It answers questions about your portfolio, staking, or a specific token, grounded in your actual wallet data rather than generic information, with inline charts when a token comes up.

Agentic mode means it acts rather than just answers. Ask it in plain language to chart a token, start a swap, or set up staking, and it routes you into the relevant flow. There is also a proactive feed that flags when your tokens or watchlist move, with tunable tone and categories, and in-wallet chat support that connects you to the Gero team directly from the Companion dock, non-custodial throughout, with no keys leaving the wallet.

Two caveats we want stated clearly. The proactive feed produces observations, never financial advice. And the Companion is rolling out gradually behind feature flags.

Swap moves to Gero's own aggregator

Swap now runs on Gero's own aggregator through the embedded swap widget, replacing the previous third-party integration across all five swap surfaces: the page, the dialog, the dashboard, the side panel and token detail. It works with every wallet type, including password, PassKey, Ledger, Trezor and Keystone.

The widget also defines limit, stop and OCO order types alongside market orders. Those sit behind a server flag that is off by default, so treat advanced order types as coming rather than as a day-one feature.

Sign in with Google

You will be able to create a recoverable Cardano wallet using a Google account, with no seed phrase to manage day to day.

The custody design is worth understanding. It uses self-hosted MPC: the key is split into three Shamir shares, one on your device, one tied to login and one for recovery, with a two-of-three threshold. The backend holds only one share, which means it can never sign for you and can never lock you out. The 24-word mnemonic remains exportable as the ultimate escape hatch.

This is rolling out progressively during the 2.7 cycle, like the other flag-gated features, so it may not appear in your wallet the moment you update.

Cross-device signing

The desktop wallet is ready to pair with the upcoming Gero iOS app, which is currently in TestFlight beta rather than on the App Store. Pairing works by QR scan with wallet-control proof and a short-authentication-string confirmation, producing a wallet-verified pair badge.

Once paired, you can choose "Sign on another device" from the Send flow, with trusted-device management, a per-device signing policy, replay and expiry protection, and wake-up support for offline signers. It is an approval step, not multisig.

Bitcoin, on testnet

Bitcoin ecosystem support arrives with a Mempool widget, routed through Gero Sync real-time push, available via the onboarding network selector. It is testnet-only to start, with mainnet to follow. Bitcoin is not something to hold or spend in the wallet today.

Trading, staking and pool operators

In-wallet perpetuals reach parity with the Strike Finance dApp, with deposit, withdrawal settled in USDM, and account connection without a CIP-30 hop. Order previews show entry price, required margin, fees, liquidation price and slippage, and position tables carry live mark-price PnL and distance to liquidation. TWAP orders and order batching over a live WebSocket are included.

On the staking side, delegation now shows a pending state while the transaction is unconfirmed, so there is no more wondering whether it went through. A new Stake Pool Operator dashboard adds a guided pool-setup wizard for Ledger and software keys, pool-update flows with side-panel Bluetooth signing, and safety guards against fund loss on retries. You can read more about delegation on the staking page.

There is also a new privacy toggle, an eye icon that masks every monetary value across the dashboard and side panel and persists per wallet.

Security hardening

Two external audit rounds plus an internal pre-open-source review landed in this release.

The critical item: mnemonic, two-factor and MPC encryption move from a weak key-derivation scheme to Argon2id, a memory-hard function chosen to make brute-force attacks expensive. The migration is backward compatible and existing wallets migrate transparently. The legacy crypto-ts library was removed entirely, including its weak wrapper around root-key, Bitcoin and Midnight key encryption, with regression tests guarding the legacy decrypt path.

Alongside that, dApp signTx now trusts only the relay-set request origin, so a malicious page cannot spoof its origin. CIP-30 reads validate frame sources against a server-side whitelist. OAuth flows moved to a cryptographically secure random number generator, and API keys are no longer baked into the client bundle. Changing your spending password now invalidates the old one immediately in-session without forcing a re-login.

Details on the wallet's security model are on the security page.

What we are not claiming

Short list, in the interest of not overselling a release we are genuinely proud of.

Not every feature on day one. Most headline items sit behind remote feature flags and roll out in stages.

Bitcoin is testnet-only.

Sign in with Google is rolling out progressively, not switched on for everyone at once.

Limit, stop and OCO orders are flag-gated off by default.

Sponsored collateral applies to trusted dApps, not to anything that asks.

Frequently asked questions

Is GeroWallet 2.7 available now?

Yes. Version 2.7.0 was released on 19 August 2026. Individual features inside it still roll out in stages behind feature flags, so the release being available and every feature being switched on for you are two different things.

Is GeroWallet open source?

Yes. The full source is public on GitHub under the Apache 2.0 licence, which is OSI-approved. You can read it, audit it, fork it and build on it within the licence terms.

Will I get every 2.7 feature as soon as I update?

Not necessarily. Most headline features are controlled by remote feature flags and roll out in stages.

Can I use Bitcoin on mainnet?

Not yet. Bitcoin support in 2.7 is testnet-only, with mainnet to follow, so it is not somewhere to hold or spend real BTC today. Sign in with Google is a separate feature and is rolling out progressively during the 2.7 cycle.

What is the biggest change in 2.7?

Depends what you value. For transparency, the public source code. For privacy, Midnight on mainnet with in-wallet DUST generation and a choice of where proofs run. For security, the Argon2id migration and two external audit rounds.

Get ready for 2.7

The best way to be ready for the release is to already be running the wallet. GeroWallet is a non-custodial Cardano browser extension with ADA staking, governance and DRep delegation, swap, an NFT gallery, Cardano Shield scam detection, and support for Ledger, Trezor and Keystone.

Install GeroWallet, browse the full feature set at gerowallet.io/features, or go read the code at github.com/Gero-Labs/gerowallet.