Lace 2.3 is here.
This one is all about making things feel a little smoother, clearer and more reliable across the wallet.
We’ve made improvements to DApps, staking, governance, hardware wallets, balances, syncing and Midnight, alongside a good collection of smaller fixes and bits of polish.
Here’s a look at what’s new.
Better DApp connections
We’ve made DApp connections more reliable, particularly when Lace’s background process restarts during a request.
Requests can now survive the restart instead of being lost, and if a transaction has already gone through, Lace will recognise it if it’s submitted again rather than treating it as a failure.
We’ve also improved how Lace handles account changes, so connected DApps are correctly notified when the account they’re using changes.
There are a few other DApp fixes in this release too, including better handling of transactions that use your own recent, unconfirmed funds.
A better way to browse staking pools
We’ve added estimated annual rates to the staking pool browser, giving you another useful bit of information when exploring pools.
The pool list has also been updated to use a combined recommendation score when ordering results.
We’ve also tidied up a few things behind the scenes, including how pool rewards are measured and how pools without a ticker are displayed.
Governance gets an update
The DRep browser now uses quality signals when ordering DReps rather than simply ranking them by stake weight.
DReps excluded by policy won’t appear in the main list, but you can still find them by searching for their exact ID.
We’ve also fixed how DRep IDs are displayed in activity details and transaction reviews, so they appear in their current standard form.
More hardware wallet improvements
Lace 2.3 brings improvements across Ledger, Trezor, Keystone and SeedSigner.
Trezor users will now get a clearer message when Trezor Suite can’t be reached, including when Chrome is blocking the local connection. This message also appears earlier during onboarding, rather than waiting until something fails.
We’ve also improved staking and delegation signing. Stake registration and delegation are now sent to your device as separate certificates so compatible devices can display them correctly.
For air-gapped Keystone and SeedSigner wallets, Lace now handles the additional signatures required by script-based wallets more reliably.
Balances and syncing, made clearer
We’ve made some changes to how balances refresh and how syncing is displayed.
Balances now refresh more reliably instead of holding onto an old value. An empty response from the network is also handled correctly as an empty account.
And just to be clear: your funds were always secured on-chain and were unaffected by the previous balance display issue.
Sync progress now shows 0% when syncing is just getting started, rather than appearing blank. Accounts that haven’t synced yet also show a loading state instead of looking like they have no funds.
Midnight improvements
There are a few useful Midnight updates in 2.3 too.
If a Midnight account gets stuck while syncing, you can now reset its sync state directly from the account settings.
The send form now defaults to NIGHT, DUST fees are calculated from spendable DUST, and we’ve fixed an issue that could leave wallet state being written in the background after stopping a wallet.
A few more things you might notice
Your portfolio now sorts tokens by value by default, and Lace remembers the sort order you choose.
We’ve also fixed a number of issues across sending, swapping and receiving.
Lace will no longer build a transaction when no assets have been selected, recent unconfirmed inputs are handled correctly when building transactions, and receiving now works for accounts that haven’t generated an address yet.
Bitcoin transactions also appear as pending as soon as they’re submitted.
Account renaming is now reflected consistently throughout Lace, including Midnight accounts, and sheet forms can now be submitted using the return key.
We’ve also cleaned up a handful of UI issues, including tab bar positioning, hidden currency entries and some graphics card blur artefacts.
And for our multilingual community, there are Japanese terminology corrections and a few Spanish wording fixes.
The full list
There’s quite a bit packed into this release, so if you want to get into the details, here’s the complete list of additions, improvements and fixes included in Lace 2.3.
Added
Staking: The pool browser now shows each pool’s estimated annual rate.
Midnight: You can now reset the sync state for a Midnight account from its account settings if syncing gets stuck.
Accounts: Your Bitcoin account public key is now available from the Your Keys sheet.
Improved
Privacy: Cardano network requests are now routed through the Lace proxy, and the Cardano provider key previously bundled with the extension has been removed.
Staking: The pool list now uses a combined recommendation score, pool rewards are measured against circulating supply net of the treasury cut, and pools without a ticker are labelled using part of their ID.
Governance: The DRep browser uses quality signals when ordering results, and DReps excluded by policy no longer appear in the main list.
Hardware wallets: Trezor users get clearer guidance when Trezor Suite can’t be reached, including when Chrome is blocking the local connection.
Tokens: Your portfolio sorts by fiat value by default and remembers your chosen sort order.
Performance: DApp Explorer logos no longer re-decode while scrolling.
UI: Sheet forms can now be submitted using the return key.
Fixed
DApps: Requests now survive the extension’s background worker restarting mid-call. Safe calls are replayed rather than lost, transactions that have already confirmed are reported as successful if submitted again, and account changes are correctly reported to connected DApps.
DApps: Transactions that spend your own unconfirmed outputs are recognised correctly.
DApps: Stake key registration is answered from the network when it isn’t yet cached.
Governance: DRep IDs now display in their current standard form in activity details and transaction reviews.
Staking: Pending staking transactions now carry their network details, and the delegation success screen no longer reacts to outdated fee calculations.
Hardware wallets: Stake registration and delegation are sent as separate certificates, air-gapped Keystone and SeedSigner devices are asked for the additional signatures required by script-based wallets, and Lace declines cleanly when a Ledger can’t provide them.
Balances: Account balances refresh reliably and empty network responses are handled correctly.
Bitcoin: Submitted transactions now appear as pending immediately.
Midnight: The send form defaults to NIGHT, DUST fees are calculated from spendable DUST, and stopping a wallet no longer leaves state being written in the background.
Send: Lace no longer builds a transaction when no assets have been selected.
Receive: The receive sheet now works for accounts that haven’t generated an address.
Accounts: Account renaming is reflected consistently, including for Midnight accounts.
UI: Fixed tab bar positioning, currency list visibility and graphics card blur artefacts.
Localisation: Japanese terminology and Spanish wording have been updated and corrected.
That’s Lace 2.3.
A little smoother, a little clearer, and with plenty happening under the hood.
Update to the latest version of Lace to get the improvements.