Last week, the team released Daedalus mainnet 2.3.0. The team is now busy adding support for hardware wallets, focusing on fixing build issues. Once these issues are resolved, the team will be able to start testing Daedalus installers. The team also re-enabled the stake pool saturation indicator and fixed a minor UI issue with the stake pool tooltip. Finally, they updated Electron to the latest v8 release and are in the process of testing to confirm that all features are operational.
Last week, the team released a new version of the wallet, which now supports Ledger and Trezor devices. The team is working on improving this implementation even further.
The team extended benchmarking to sync 100 accounts in one wallet, with no significant differences in performance.
Flexible SMASH selection has now been enabled in the wallet, which should make it easier for the community to run their own SMASH servers. An upcoming improvement will enable the wallet to handle delisting of pools better.
Finally, GraphQL is ready for release, pending the final release of db-sync.
Last week, the team added the DiffusionMode to the Ouroboros network and implemented some changes to P2P functionality in the Ouroboros network cardano-node repository. They also enhanced keep-alive tracers, resolved all outstanding pull requests, and worked on the map for LocalStateQueryClient, which makes cardano-api easier to use.
Last week, the team worked on timelock scripts, which are in the final stage and require the generalization of transactions to define an optimal ‘time-to-start’ and ‘time-to-live’. They also performed many property tests for the multi-asset functionality, and discovered and resolved a bug in the ranking system. Work is ongoing with transaction generalization to define optional fields, adjusting property tests to multi-assets functionality, and some changes to simplify this integration with the consensus.
Last week, the Plutus team completed some refactoring work in the smart contract backend (SCB) that included removing an obsolete type variable from
ChainReport and renaming some test cases. They also worked on Hlint housekeeping so that it is now possible to (optionally) fetch our metadata server from the live system. Additionally, they worked on a simple stablecoin prototype using state machines.
Last week, the team released Daedalus Flight versions 2.3.0-FC1 and 2.3.0-FC2. The automatic update system has been successfully tested within Daedalus Flight, which allowed the team to proceed with the preparation for the Daedalus Mainnet 2.3.0 release. The team have been working on providing support for the hardware wallets, focusing on the multi-device support feature. The third-party dependency updates are now completed and merged. The Byron wallet migration feature has been updated to display the migration leftovers, and finally, the team is now completing the addition of table view to the stake pool display.
Last week, the team worked on the release of flexible SMASH server selection, a feature that will give the end user a dynamic option to select their own SMASH server for their wallet.
The team is also working on the refactoring of the cardano-library to support multisig transactions, and have nearly finished with hardware wallet support on the wallet backend.
Finally, there is ongoing work on multi-account support, they are adding rewards data to Graphql after db-sync release, and have started the release of rosetta v1.0-rc1.
Last week, the team fixed DeltaQ calculations and restarted a range of tests. They also extended MonadAsync in io-sim-classes, rate-limited ‘Warm to Hot’ transition, and worked on cardano-node API. Finally, the team were engaged with Athens University of Economics and Business (AUEB) partners.
Last week, the team tested and deployed version 1.21.1 of the cardano-node. They released the latest version of Daedalus with integrated SMASH functionality, cross-compiled it for hardware wallet support, and integrated the Daedalus wallet backend with 1.21.1 version of the cardano-node to show the saturation level. Finally, the team worked on the Bitte project documentation, which explains how to run clusters of nodes with Nomad and Nix functions.
Last week, the team fixed a performance regression in the set algebra library and added many respective property tests. They also fixed a bug in a wallet-API function and diagnosed some cardano-node issues. The team continued working on the Value Coin abstraction in the new Era framework. They wrote code to detect the transition point from Shelley to the next development eras, and started work on the integration of these eras with the consensus protocol. The team added additional support for multiple credentials, which allows managing many stake pools with a single node, which is required for benchmarking. Finally, they detected and resolved a performance issue in the rewards calculation.
Last week, the Plutus team made some changes to the Haskell code for the migration of the Plutus Playground to use Lambda and webghc. They also fixed a problem with x509 builds on OSX and added a safe version of LedgerBytes.fromHex that returns an
Either value rather than an error. Also, they continued working on environments for the wyohack event in Wyoming.
The Marlowe team concentrated on updates to the Marlowe homepage within the Marlowe Playground. In addition, they made improvements to the text within the Modelling contracts section of the playground.
Last week, the team worked on the preparation for Daedalus Flight 2.3.0-FC1 and 2.3.0-FC2 releases, which will test the newly-built automatic update functionality. The third party dependency updates are now in the final testing and review phases. Finally, the team is working on adding the ‘table view’ feature to the stake pools display.
Last week, the Adrestia team worked on improving wallet performance, with the goal of enhancing the usability of larger wallets. These improvements will go live today. The team will shortly publish a blog post outlining the improvements made and the benchmarks used.
The wallet now has an address validation endpoint. The team has also been working on implementing flexible SMASH server selection, meaning that users can pick whichever SMASH server they prefer without being forced to resync the wallet.
The team has also made great progress on multisig, and its corresponding CIP will be discussed in the upcoming CIP writer group. Some steps have been taken to add multisig functionality to the Cardano-addresses and wallet.
The team expects that work on the multi-accounts for the wallet will start next week. They will publish an updated API specification as soon as possible to facilitate changes for potential users.
Work is currently underway to add historical rewards to data to the GraphQL data model, which will simplify the users' task to find their historical rewards.
Finally, the team expects to release Cardano-Rosetta 1.0.0 early next week, including some final improvements. There are continuous enhancements on the Rosetta framework, so the team is looking to batch-upgrade the new items over the coming weeks.
Last week, the networking team worked on the registerDelay implementation, labeled threads to ensure easy debugging, adjusted block-fetch protocol limits, and conducted respective testing within tx-submission and block-fetch clients. The team also continued working on the P2P governor and the connection manager integration with the node, diagnosing and fixing any occurring issues. They completed the keep-alive tracing feature implementation within the Ouroboros network, whereas it is work in progress in the cardano-node. The team found some bugs in DeltaQ, worked on their resolution, and implemented tests to restart mini protocols. Finally, they worked with metadata and high-level API development for mini protocols in cardano-CLI.
Last week, the team integrated the USB driver with yarn2nix to support hardware wallet development features with Daedalus. They also built and deployed Graphql 2.2.0, and worked on the frontend explorer version 1.2.0, implementing withdrawal and deposit support. Finally, the team helped to integrate the automated update feature into upcoming Daedalus Flight, and investigated performance issues that occurred during rewards calculation.
Last week, the team performed some prototyping and testing in the cardano-CLI to simplify benchmarking on custom clusters. The team resolved CI caching divergences that caused local overbuilding, and are currently working on prototyping the multi-pool capacity in the Ouroboros network. Work is ongoing with the new Era generalization in the ledger code. The team has prepared an overview of multiple properties with algebraic structures for the generalized coin structure, which will help to create a ‘coin’ that can be used as a multi-asset.
Last week, the Plutus team made updates to use de-bruijn indices for scripts. They also fixed the order of elements in the TransactionPartialPay JSON decoding and removed unused code from the Wallet.API. Finally, they were busy preparing environments for the wyohack event in Wyoming.
The Marlowe team concentrated on the migration to Amazon Web Services (AWS) Lambda within the Marlowe Playground. This included using Lambda proxy features, which means that Marlowe analysis can now be performed locally. They also performed a sanity check on all Lambda references to ensure that they are all accurate. Finally, they worked on the cashflows use case for Marlowe Labs.