IOHK is pleased to announce the release of Daedalus 0.11.1 and Cardano 1.3.1.

Daedalus 0.11.1 has a couple of fixes to known issues, two of which are fixes for significant bugs that are affecting a substantial number of users. These two issues are causing users to be stuck on the loading screen with "Connecting to network" message.

Up until this release, Windows users who had non-Latin characters in their Windows usernames were unable to use Daedalus. The first fix will ensure that these users will now be able to use Daedalus in Windows.

The second fix detects when users launch Daedalus improperly using a Windows icon created by pinning Daedalus to Windows taskbar. The fix includes Daedalus detecting improperly launched software in this instance and providing users with a warning message and instructions to launch it properly.

This update also includes other fixes to minor issues.

Team IOHK

Daedalus 0.11.1 with Cardano 1.3.1 - release notes

Daedalus 0.11.0

Bug fixes and improvements

Warning when Daedalus is launched improperly after pinning to Windows taskbar

Some Windows users have been creating shortcuts for launching Daedalus from the daedalus.exe file. They usually do this by right-clicking on the Daedalus icon in the taskbar while it is running, and selecting ‘Pin this program to taskbar’ option. This is an improper way of launching Daedalus. It should be launched from cardano-launcher.exe, which configures daedalus.exe and launches a Cardano node in the background. People who were using the incorrect technique were stuck on the blue loading screen with a ‘Connecting to network’ message. An update has been made so that Daedalus now detects this situation and displays an error message with instructions to launch from the Windows start menu or from the desktop icon created by the Daedalus installer.

A blank screen is shown instead of the user interface

Some graphics card drivers were rendering a blank white screen instead of the user interface. There is now an option to restart Daedalus in safe mode without graphics acceleration, which fixes this issue. Safe mode can be activated using the ‘GPU safe mode’ option in the Daedalus system menu.

QR codes from paper wallet certificates were sometimes unreadable

Some QR code readers were unable to scan QR codes from paper wallet certificates because there was too much error correction data in printed QR codes. This issue is now fixed.

Internet disruption was causing blockchain synchronization to stop

In some cases, after an internet connection was lost, blockchain synchronization did not continue when the link was re-established. Users who experienced this were seeing a ‘Connecting to network’ message on the loading screen. This issue has been fixed.

Users with non-Latin characters in their Windows username were unable to use Daedalus for Windows

All users who have non-Latin characters (Latin characters are: a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z) in their Windows username were unable to use Daedalus. For these users, Daedalus was stuck on the blue loading screen with the “Cannot connect to network” message. This issue was affecting all previous versions of Daedalus and is now fixed.

Address discrimination

Protocol magic number used to differentiate between networks was not taken into account when validating destination addresses for transactions. This would allow transactions to be accepted on one network that include destination addresses from a different network. The issue has been fixed. Any such transactions will be invalid and will be rejected by the network.

Known issues

Update installations sometimes fail

Sometimes, after clicking on ‘Update and restart’ Daedalus will shut down, but the installation of the update will not start. If the user then tries to launch Daedalus within 60 seconds of Daedalus shutting down, the update will fail.
The way around this problem is to wait for a minute after Daedalus shuts down and then start Daedalus manually. This will begin the installation process and avoid the problem.
Alternatively, the update can be made by downloading the latest installer from the Daedalus website and installing the new version of Daedalus manually. This will cure the problem.

Installer integrity verification

PGP signatures

Installers are signed with IOHK's organisational PGP key with this fingerprint: D32587D4090FE461CAEE0FF4966E5CB9CBFAA9BA.

SHA256 checksums

macOS, daedalus-0.11.1-cardano-sl-1.3.1-mainnet-macos-2887.pkg:
51f8783822a1690663c2b349c58c68165fdde5ce72065bb9d419a21335497c5e

Windows, daedalus-0.11.1-cardano-sl-1.3.1-mainnet-windows-9228.exe:
5773dc2c5d95e2d3d0ebfc2156e14216f6c16a88b2fa01f49bf6c768f672c2cd