• 0.13.0
Assets 9

Release announcement

Today we release Cardano 1.5 on the Cardano mainnet. The Cardano 1.5 release is a milestone because it is the last major Cardano release of the Byron development phase, which we have been in since the launch of mainnet.

Cardano 1.5 is important in preparation for moving to the Shelley development phase. This update brings a new consensus protocol, Ouroboros BFT, which is a key step in the transition from Ouroboros Classic, the current consensus protocol running the Cardano network, to Ouroboros Genesis, the protocol for the Shelley era. Ouroboros Genesis is a major upgrade to the protocol that underpins Cardano because it is first proof-of-stake protocol that matches the security guarantees of proof-of-work protocols such as Bitcoin.

Ouroboros BFT will not be immediately activated after deployment of the 1.5 release. It will be activated through a protocol update later, which will be announced separately. This protocol update will deactivate the Ouroboros Classic protocol and activate the Ouroboros BFT consensus protocol. This update is technically a hard fork but will take place in a smooth and automatic way because this is a planned protocol upgrade whereby all parties of the current federated system have agreed to the change.

Daedalus users need to upgrade to Cardano 1.5 by installing Daedalus 0.13.0 by following prompts in Daedalus. Everyone needs to upgrade to version 1.5 in order to make the hard fork.

Please be aware of fraudsters posting fake Daedalus apps online or making attempts through social media or private message to gain access to your wallet. Always download Daedalus only from official sources.

Cryptocurrency exchanges need to migrate from v0 to v1 wallet API before upgrading to this release. The v0 wallet API, which was deprecated in the 1.4 release, is now completely removed in the 1.5 release and can no longer be used.

The Cardano 1.5 release also makes many other improvements. These include performance improvements when rendering lists with a large number of transactions and wallet addresses, the addition of features for detecting insufficient disk space, and a new screen that visualizes the block storage consolidation process.

For more information please see the release notes.

Release notes

English 日本語

Support portal

English 日本語

Cardano versioning

https://iohk.io/blog/how-cardano-releases-are-versioned/

Cardano testnet

https://testnet.iohkdev.io/cardano/

  • 0.12.1
Assets 3

Release announcement

This minor release fixes four small but important issues: problems with blockchain synchronization and network connection, transactions with a large number of inputs failing, and limitations with showing transaction history in Daedalus. For details please read the release notes.

Release notes

English 日本語

Support portal

English 日本語

Cardano versioning

https://iohk.io/blog/how-cardano-releases-are-versioned/

Cardano testnet

https://testnet.iohkdev.io/cardano/

  • 0.11.2
Assets 2

Daedalus 0.11.2 with Cardano 1.3.2

Cardano 1.3.2

Bug fixes and improvements

Epoch boundary block maximum size

Maximum block size for epoch boundary blocks changed to 1.953 MB instead of incorrectly using the maximum block size of regular blocks for epoch boundary blocks.

Installer integrity verification

PGP signatures

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

SHA256 checksums

macOS, daedalus-0.11.2-cardano-sl-1.3.2-mainnet-macos-3541.pkg: a4ea486d298f5a122ddef8eb58cf2d89e8487627c00eeac5c1d556e361325371

Windows, daedalus-0.11.2-cardano-sl-1.3.2-mainnet-windows-10311.exe: 3149ca54b2aced572b917902e0d132da48914a586d2f6af11fc7911b307e08d4

  • 0.11.1
Assets 2

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.

screen shot 2018-10-12 at 11 45 11

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.

gpu-safe-mode

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

  • 0.11.0
Assets 2

Daedalus 0.11.0

Features

Hiding and showing used addresses

A switch for showing and hiding addresses that have been used has been added to the Receive screen.

receive-screen-en

Bug fixes and improvements

Integrity verification for Daedalus installers

From this release, Daedalus installers will be signed with IOHK’s organizational PGP key. Also, on the Daedalus download web page, a checksum will be published for each installer with instructions for verifying their signatures and checksums. This will enable users to verify the integrity of an installer so they can be sure that they are using the genuine, unmodified, software.

Smaller and faster using less memory

The size of the output application bundle built from the source has been reduced by a factor of 10 by not embedding any font, image or other static assets. This reduces the memory usage by the same factor, a change that will be noticeable for users running Daedalus on slower machines with a small amount of memory.

optimisation

Linux kanji characters

The font used in Daedalus has been changed to Google’s Noto Sans. This fixes a problem rendering kanji characters on Linux in preparation for the first Daedalus Linux release.

About dialog changed to overlay

The About dialog is no longer a standalone window and is now in an overlay on the user interface. This reduces the number of rendering processes Daedalus uses and reduces memory use.

about-screen-en

Ada redemption icon removed from the main menu

The Ada redemption feature is rarely used because most people have already redeemed their Ada, so the icon has been removed from the main menu. It is now available from the system menu.

redemption-en

Cardano SL 1.3.0

Features

Cardano wallet API v1 for the exchanges

A subset of endpoints from the Cardano wallet API, used by cryptocurrency exchanges, was moved to the new Cardano REST API v1. The remaining endpoints will move from v0 to v1 in the next release. Cryptocurrency exchanges are encouraged to move to API v1 because the old API is now regarded as deprecated and will be removed in future versions (CBR-101).

Subscription status added to node information

The endpoint that provides information about the node (/api/v1/node-info) has been expanded to include information about the node subscription status, which can be used to check if the Cardano node is connected to the network or not.

Improved error message for missing charset in API calls

The generic message returned from Cardano node endpoint calls when the charset was not specified is replaced with a more descriptive error message to help users of the API troubleshoot the problem.

Support for sending raw data on the network

It is now possible to send raw, CBOR serialized data to the network using the diffusion layer. Previously, the data had to be serialized before sending it to the network, which slowed things down.

Specifications and documentation

Formal specification for new wallet backend

The formal specification of a wallet for Cardano (or any UTXO-based cryptocurrency) is available here: https://cardanodocs.com/technical/formal-specification-for-a-cardano-wallet/.

Bug fixes and improvements

Faster sending and receiving of blocks

Sending and receiving blocks on the network now works better. First, deserialization performance has been improved by optimizing memory use. Next, blocks are now downloaded concurrently without batching. Finally, block traversal is optimized by the introduction of 'forward links', which removes the need for header retrieval and serialization.

Optimised block storage

Block storage is now optimized by consolidating block and undo data in a single file. This change reduces disk use and improves performance when reading and writing blocks. In later Cardano versions, block storage will be improved even more, so this is only an interim solution.

High (and recurrent) I/O traffic in wallet reduced

I/O spikes in traffic were being caused by large logs being flushed. This issue has been fixed. Failure to reconnect to the network Improper handling of DNS failures would sometimes cause the Cardano node to fail to reconnect to the network after an internet connection was interrupted and would need to be restarted. This issue has been fixed.

Time error between user’s computer and the network

The endpoint (/api/settings/time/difference) for calculating the time difference between a user’s computer and Cardano network was returning an incorrect value in some cases. This was because the calculation was not properly handling the time needed to request the current time from NTP servers and to get the response. As a result, some Daedalus users were prevented from using their wallet because Daedalus cannot be used if there is a time difference of more than 15 seconds. This issue has been fixed.

Known issues

A blank screen is shown instead of the user interface

Some graphics card drivers are rendering a white blank screen instead of the user interface.

Incompatibility of QR codes from paper wallet certificates

Some QR code readers are unable to scan QR codes from paper wallet certificates because there is too much error correction data in printed QR codes.

Antivirus software slows down wallet restoration and blockchain synchronization

Some antivirus software, including Windows Defender, which is installed with Windows 10 by default, can slow down wallet restoration and initial blockchain synchronization. All Windows users are warned that antivirus software may reduce wallet restoration performance. This warning is in the form of a prompt shown when wallet restoration begins. Note that Daedalus is not detecting which antivirus software is on the user’s machine and is displaying this warning for all Windows users. The development team will try to solve this issue in future releases.

image

Installer integrity verification

PGP signatures

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

SHA256 checksums

macOS, daedalus-0.11.0-cardano-sl-1.3.0-mainnet-macos-2260.pkg: 6ad90da2053f06f9f0e35c2ae05a8620094b83c6a6a5401c201a1e5abcc22ae4

Windows, daedalus-0.11.0-cardano-sl-1.3.0-mainnet-windows-8183.exe: ce7eb1a1a6e95924d17af78604cb83ccc93e67f794c2ca4b4e91969de9e442b4

  • 0.10.1
Assets 2

Daedalus 0.10.1

Bug fixes and improvements

Paper wallets - PDF printing issue

The issue with printing PDF documents with paper wallet certificates caused by some printers running out of memory was fixed by reducing the complexity of the PDF document.

Limit of 10 wallets in Daedalus

Daedalus had a limit of showing only 10 wallets. Users who created more than 10 wallets were unable to use all of them. This has been changed and Daedalus now supports up to 20 wallets. Also, a check has been introduced which prevents the creation of more than 20 wallets.

Installation issue

The Daedalus installer bug causing corruption of the configuration when it was used to install an update, while Daedalus processes were still running, was fixed.

Missing launcher log files

The issue causing Daedalus launcher not to write log files was fixed.

Cardano 1.2.1

Bug fixes and improvements

Locale issue with the shell script for launching wallet backend

Shell script for launching wallet backend, used mainly by the exchanges, was fixed to work regardless of the locale on the host machine.

  • 0.10.0
Assets 2

Daedalus 0.10.0

New features

Paper wallets

Paper wallets allow users to store their funds securely offline. Paper wallet certificates can now be generated in Daedalus. They contain a 27-word recovery phrase, of which the first 18 words are printed automatically on the certificate and the remaining 9 words the user writes by hand. This improves security because the printed certificate, which could be cached by the printer or compromised in some other way, does not include everything needed to restore the wallet. The wallet from the certificate is initially empty when it is created and users can send funds to it using the wallet address printed on the certificate.

Restoration of paper wallets

Paper wallets can now be restored and brought back online in Daedalus.

Asynchronous wallet restoration

The restoration of Cardano wallets is now a non-blocking, background operation. As soon as wallet restoration is initiated, a user is presented with the wallet in the user interface. The wallet balance is immediately visible and restoration of the transaction history will be running in the background. A progress indicator will show the percentage of restoration that has been completed and a time estimation until the operation is complete. The transaction history is populated as each transaction is recovered from the blockchain.

“Show more transactions” button on the summary screen

The wallet summary screen shows up to five recent transactions. When the wallet has more than five transactions, a “Show more transactions” button appears that links to the transaction history page.

Support page in Settings

Daedalus now has a new support page in Settings. This page includes links for accessing the FAQ with solutions to known issues, access to a form for sending support requests and a link for downloading logs. Clicking the "bug" icon in the sidebar no longer opens the form for sending support requests but takes the user to this page instead.

Support request feature now includes logs by default

An option to include logs with support requests is now on by default.

Wallet Addresses link to Cardano Explorer

Wallet addresses displayed in the Daedalus user interface now link to the address details page in the Cardano Explorer.

Bug fixes and improvements

Spending password is on by default

For improved security, the spending password is on by default when creating or restoring a wallet.

Removed automatic sending of logs to a remote server

An opt-in feature for automatically sending logs to the remote server is now removed because the high volume of logs aggregated through this feature was unmanageable.

UTC timestamp in Daedalus logs

All timestamps appearing in Daedalus logs are now in the UTC time zone, for easier analysis of the log files.

Updated teams on the “About” dialog

The Daedalus “About” dialog now includes an updated list of Daedalus and Cardano team members.

Text selection disabled in parts of the user interface

The selection of some text elements in Daedalus using a mouse is now disabled, which improves the look and feel of the application. Text elements such as addresses and amounts are still selectable and it is possible to copy their values to the clipboard.

Cardano 1.2.0

New features

V1 Wallet API

A new and improved version of the wallet API is now available for cryptocurrency exchanges and other parties. This makes the previous V0 version obsolete. Everyone using this API is encouraged to switch to the new version. Documentation for both versions is available at https://cardanodocs.com/technical/wallet/api

Bug fixes and improvements

Wallet backend performance improvements

Wallet backend performance has been improved, especially for retrieving wallets using the API endpoint.

  • 0.9.1
Assets 2

Daedalus 0.9.1 with Cardano 1.1.1

Bug fixes and improvements

  • A presentation bug has been fixed that caused only five recent transactions to be shown on the transaction list, even though there were more than five transactions in the wallet. (PR 778)

  • An issue has been fixed that stopped copy and paste operations from working when initiated using the right-click context menu. (PR 817)

  • A "Couldn't pack log files” error that masked the real reason for the Cardano node crashing has been fixed.

  • On Windows, the desktop icon was not showing the Daedalus image; this has now been fixed. (PR 837)

  • An error has been fixed that in some cases prevented users creating a wallet with a name containing non-latin characters, like Japanese Kanji or Chinese. (PR 840)

Features

  • New Edit section in system menu with copy & paste and related actions (PR 817)