Lace Mainnet - Known Issues
The following are issues impacting Lace Mainnet, which we already identified. We will be resolving them in one of the next releases. There is no need to log support tickets for any of them.
1. No ROS values displayed
Currently the ROS values are not displayed, it looks like this;
2. Delegating to multiple Stake Pool´s with a single-address wallet
Delegating from a single-address wallet (which was restored in a very early version of Lace prior to multi-address support) a portion of the balance may not be visible (only visual bug), Lace is tracking data from only one address.
Workaround;
Please pair the wallet again, this will trigger address discovery and the issue should not be present once the wallet is restored.
3. Wrong network after changing/injecting a wallet
The network can seem to have changed to a Preprod, but you would continue seeing Mainnet assets, it is only a visual bug and your wallet continues to be on the pre-selected network.
4. Collateral displays "No ADA" state during synchronization
If your Lace wallet synchronizes while you are attempting to add collateral it may for a moment (until it is in sync) not accept the correct password.
Workaround
Ensure your Lace wallet is in sync when initiating the transaction.
5. Onboarding/Restoring wallet - incorrect focus field during entering mnemonic phrase
-
Go through the wallet restoration process and go to entering mnemonic phase
-
Fill 8 words
-
Click Enter
Actual Results:
-
User is focused on 16th word
Expected results
-
User should be focused on 9th word
6. Sometimes sending transaction is not disappearing from list after confirmation
Workaround
Refresh the tab. Bug solved, to be included in the next release.
7. Intermittent issue with Restoring a hardware wallet.
Rarely while restoring a hardware wallet, infinite loading screen and closing Lace does not help;
Workaround
-
Onboard HW wallet
-
Remove wallet
-
Onboard wallet again
-
Retry until the issue is resolved
8. Stake Pools ticker, name and logo not visible
An issue where searching for Stake pools by ID or name does not show their Ticker, Name and logo are not visible.
9. Burning Ada handles, burnt one remains as a visual bug
When you purposefully burn an Ada handle to upgrade it and utilize CIP-68 for customization, the old visually remains in your wallet, this is just a visual bug on the NFTs tab, however if you click on the Receive button, you see only the correct ones and if you check on any blockchain explorer you also see the correct ones.
If your problem is not listed here;
For assistance, please submit a ticket to the IOHK support team from the Settings section in Lace, or by using the submit a request form.