Daedalus Testnet - Known Issues

Daedalus Shelley Testnet 1.6.0-STN5

Mainnet snapshot balances

Balances for restored mainnet snapshot wallets may be incorrect because mainnet snapshot does not include transaction history which is required for accurate wallet restoration.

Delegating a wallet which only has rewards

Delegating a wallet which only has rewards balances, without any UTXOs, is not implemented yet. An example of this wallet is a wallet with Incentivized Testnet rewards, which was restored on the Shelley testnet. In this case, the delegation wizard will be stuck on the confirmation step with a 'Calculating fees' label printed instead of the actual fees required to confirm the delegation.
This will not be an issue on the mainnet where Daedalus will have a dedicated Incentivized Testnet rewards redemption feature.

Spending from Byron wallets

This version of Daedalus does not support spending from Byron wallets before the upgrade to Shelley is completed.

Delegating to a retiring stake pool

Delegating to a retiring stake pool sometimes fails. When this happens, in the last step, delegation confirmation fails with an ‘An error occurred’ message instead of completing successfully.

Stake pool saturation

Stake pool saturation is correctly used and calculated for stake pool ranking. However, due to ongoing work, we are currently not able to display these correctly in the stake pool details and saturation indicator, so we have temporarily removed this feature from the user interface.

Downloading logs on older versions of Linux

Downloading logs on some older versions of Linux can cause Daedalus to crash. 

If Daedalus crashes with no warning in a file chooser dialog, your system gtk+3 schema is probably too old. As a work around you can backup the current file and run these commands to get a newer version, although it may cause an issue with other applications that depend on the older schema.

An alternative workaround is to open the state directory and manually create an archive from the logs\pub directory.

Incorrect transaction history when spending rewards

When making a transaction in Daedalus that spends rewards, the amount of ada that was moved in transaction details does not include the amount of spent rewards. So the amount of transacted ada presented in the transaction can be lower than the amount of ada that was actually moved. This does not affect the integrity of the transaction and is just a presentation issue.

Example:

If you have questions or experience any issues, please remember that our support team is here to assist. To submit a ticket to IOHK support, you can do so from the Help menu in Daedalus, or by using the submit a request form.