Last week, the team integrated the Daedalus Catalyst version with Daedalus Mainnet along with implementing native tokens UI and SMASH configuration features.
Last week, the Adrestia team worked on finalizing and testing API updates in preparation for the Mary hard fork.
The team focused on the pre-release of the cardano-wallet with multi-asset features, integration and testing with Node v. 1.25.1 and db-sync v. 8.0.0, extended cardano-addresses with support for script templates, and the token locking feature.
Last week, the team tested the connection manager implementation, which led to the discovery and resolution of several issues. They also worked on the connection manager specification, including the update of state machine compatibility parameters.
Last week the team worked on the tokens’ new value representation, improved minimal UTxO calculation, finalized protocol updates generalization, and focused on the integrations required for the upcoming hard forks (Mary and Alonzo). They also made progress preparing the Alonzo specification, worked on the proofs of Allegra and Mary key properties, and began redesigning the logging API and improving the RTView UI.
The team also did a lot of preparation work for the Mary hard fork, which included the completion of system-level performance benchmarks and the addition of new traces to Ouroboros to support regression isolation.
Finally, they completed transaction generator updates, started working on the generator's extra payload functionality, and conducted additional infrastructure performance benchmarking.
Last week, the Plutus team worked on the Plutus Playground refresh and updated the Playground and basic application tutorials to reflect the user interface changes. They also worked on the Plutus Ledger API and made some Nix build updates.
The Marlowe team fixed some front-end issues in the Marlowe Playground. These included an issue that occurred when saving progress while transitioning from home, and a problem using the edit source button in the simulation after a refresh. Additionally, they were busy working on the Marlowe suite design elements.
Last week, the Daedalus team released Daedalus Flight version 3.2.0-FC1. It features a redesigned Delegation center, which shows delegation preference changes and their effect. It is now possible to see which stake pools are currently earning rewards, and which pools will start earning rewards in future epochs. Users can review their previous delegation preferences by checking the stake pool details.
Also, this version allows sending funds to Byron legacy addresses via ledger devices.
Last week, the Adrestia team spent most of their time working on upgrading various APIs in preparation for Mary.
Also, they worked on adding multi-asset features to the wallet, began testing and integration with the new version of the node & DB-Sync, and scoped out a plan for delivering token locking and multisig features.
Last week, the team tested the performance of the connection manager and resolved node performance issues related to memory consumption and high transaction load.
Last week, DevOps enhanced the Catalyst toolset to perform generation of Move Instantaneous Rewards (MIR) certificates to distribute rewards on the mainnet.
They also performed a series of automated tasks: command line automation to enable sending funds to multiple addresses from an account backed by a hardware wallet (or mnemonic), extraction of bulk account keys, changing delegations for up to 100 accounts in a single wallet, and enabling the Rosetta API to fetch UTxOs and generate time to live (TTL) transaction properties.
The team is now preparing different environments for quality assurance testing of the cardano-node version 1.25.
Last week, the team continued reviewing the Alonzo specification and worked on protocol parameters generalization and optimization for the upcoming Mary hard fork. They performed further system-level performance benchmarks.
The team also made progress on infrastructure improvements, updating the transaction generator to support Mary properties, and moving configuration profile machinery from Amazon Web Services (AWS) to the cardano-node local cluster.
There is also ongoing discussion about production-friendly memory profiling.
Last week, the Plutus team improved example simulations in the Plutus Playground and reorganized wallets in the basic game simulation. They also updated the plutus-metatheory documentation and improved emulator logs and the appearance of contract instance log messages in the playground.
The Marlowe team resolved a simulation error when using Blockly in the Marlowe Playground. Additionally, they continued working on their Marlowe design strategy.
Last week, the team released Daedalus v. 3.1.0 and continued implementing new features, including a tile view on the Delegation Center screen, a configurable SMASH URL option, and address verification for hardware wallets.
This week, the Adrestia team focused on final preparations for the upcoming Mary hardfork, which included adding multi-asset features into the wallet, API upgrading, designing multisig with token locking, and preparing for the integration of the wallet with the multisig coordination server.
This week, the team tallied Project Catalyst votes and improved voter tools to support stake keys and voter rewards extraction, which is based on total available rewards and the voting power percentage of the stake address.
Last week, the team reviewed the Alonzo specification (Plutus development) for the new ledger rules, and generalized the protocol parameters update mechanism in preparation for further Voltaire implementations.
Finally, the team optimized some Mary parameters to reduce the minimum ada amount required for UTxO and finalized running Mary property tests.
Last week, the Plutus team refactored the JSON encoding in the Plutus Playground trace and updated the encoding of constants. They spent time investigating emulator performance improvements, updated some error codes, and also upgraded various Nix packages.
The Marlowe team split out the simulator from the Marlowe editor, so that there is greater flexibility to use elements independently, for example, using the simulator directly with Blockly. They also fixed an issue with the Webpack configuration for local development, which is used when opening and saving Gists, and worked on QuickCheck generators for ACTUS.