24 August 2018
These newsletters provide updates on IOHK’s work specifically for cryptocurrency exchanges and on relevant software releases and developments. The previous newsletter can be found here.
IOHK released Cardano SL 1.3.0 and Daedalus 0.11.0 for both Windows and MacOS on August 8, 2018. These updates give considerable improvements in the speed of syncing the blockchain, in the scalability of network relay nodes, and in reducing the amount of disk space for storage of the blockchain by using fewer files. The Daedalus wallet V1 API is now available and supported, with the old V0 API deprecated. A performance problem for exchanges with high disk I/O has been resolved. For more details, see Cardano SL 1.3.0 release and Daedalus 0.11.0 release published on GitHub, or the combined Cardano SL 1.3.0 and Daedalus 0.11.0 release notes published on the Daedalus website.
Although V0 API is deprecated, there are some cases where the V1 API has not yet migrated some useful aspects of V0 API. For example, with global address validation, the DevOps and Wallet API teams advise exchanges to use the V0 API endpoint. By the time the teams decommission V0 API, this will be covered by the latest API.
IOHK developers are working on the next stable release, Cardano SL 1.4.0 and Daedalus 0.12.0. In particular, this version will include the new Cardano wallet implementation and the Cardano Byron testnet.
The new wallet implementation is based on and tested against IOHK’s formal wallet specification, which gives greater confidence in its correctness. It has much improved performance compared with the original wallet. This implementation will form a solid basis for new features, including improved APIs for third parties to integrate with Cardano. Exchanges will benefit from the improved performance and also from the new input selection policies that will provide far better long-term management of the unspent transaction output (UTxO).
We are interested in working with exchanges that would like to try out the new wallet implementation once it is ready, especially those exchanges that have experienced problems with the performance of the existing wallet implementation.
If an exchange has an explicit feature request for the wallet API, or the wallet in general, please, contact us either via a Slack channel or email your suggestion to email@example.com with the subject ‘New Feature Request’. Our engineers, product managers, and business analysts will consider your proposal.