This week, the team worked on adding support for hardware wallets on non-public testnets, updated the wallet settings screen by adding an unpair option for hardware devices, and also updated Trezor connection dependencies. The team also amended the Japanese application content and fixed an issue related to the connection of a USB device to Daedalus.
Finally, they started implementing a dedicated native tokens screen and continued improving the cardano-node startup property.
This week, the team continued working on diffusion simulations and pruning tests. They also worked on resolving outstanding issues and made progress on the implementation of IPv6 support for the P2P node.
This week, the team continued benchmarking activities for the node v.1.30.0 release and collated Plutus payload benchmarks. They also worked on resolving the missing transaction witness issue within the transaction generator, and reviewed the trace-dispatcher and trace-forward queue management properties.
The team continued working on porting RTView on top of the cardano-tracer, moved some hash improvements into the ledger, and worked on the completion of the chainsync benchmarking infrastructure.
This week, the Plutus team added Swagger support for the web-server API in the Plutus Application Backend (PAB). They also worked on an implementation of Secret types with SecretArguments for endpoints and started working on a new version of the ledger interface. The team performed a clean-up of the node client and did some housekeeping for the wallet backend integration. Additionally, they worked on improvements to the ChainIndex configuration handling and prepared materials for the Cardano Summit.
The Marlowe team worked on the Marlowe website and wallet cards within the Marlowe Run demo. They also worked on supporting documentation for Marlowe Run, continued work on the LAX contract, and investigated some applicability issues and relevant testing. Finally, they prepared materials for the Summit.
This week, the team released Daedalus v.4.3.1 for mainnet, testnet, and Flight. It brings Alonzo support and includes such features as improved UI, enhanced transaction management, and support for the upcoming Trezor firmware update.
This week, the team rebased P2P master branches on top of the node v.1.29. They continued working on designing pruning tests, improved simulation validation, and also on diffusion simulations.
This week, the team started working on node v.1.30.0-rc1 benchmarking, inspected transaction generator performance properties, and worked on resolving outstanding issues. They also reviewed trace-dispatcher functionality in terms of live reconfiguration and implemented the trace-forward queue management update, which is now in review.
The team continued working on the benchmarking infrastructure and implemented extensions to accommodate the chainsync benchmark including cluster and mainnet preset mechanisms. They also worked on general improvements of the genesis cache entry versioning by generalizing the node type mechanism and proxy nodes.
Finally, the team worked on optional datums in the CLI, fixed calculation of the required minimum UTXO and some other CI issues, updated the minting documentation, and improved some redeemer properties.
This week, the Plutus team released the Alonzo protocol upgrade, which brings exciting and highly anticipated capabilities through the integration of Plutus scripts onto Cardano. Scripts facilitate the implementation of smart contracts on Cardano and enable a range of new use cases for decentralized applications (DApps) for the very first time.
This included some fixes, supporting documentation, performance improvements, and a clean-up of the node client.
The Marlowe team worked on some documentation updates to the tutorials. They also fixed the Zero Coupon Bond contract issue, validated annuity (ANN) results, refactored ACTUS implementation, and started working on the LAX contract. Finally, they resolved several issues that occurred when connecting the Marlowe Run demo to the Plutus Application Backend (PAB).
This week, the team focused on fixing hardware wallet issues in preparation for the Alonzo-ready Daedalus release.
This week, the team resolved an issue that occurred when submitting a transaction in Daedalus using a hardware wallet. An update for cardano-wallet including this fix has been released. They also released an update for the metadata tools to support Plutus scripts.
Finally, the team is now working on changes required for smart contracts and PAB integration.
This week, the team made progress in testing the connection pruning. They also fixed several network issues within the simulation environment and expanded trace validation of inbound governor tests. The team is now preparing to rebase the P2P branch on top of master before the Alonzo mainnet hard fork.
This week, the team submitted the Alonzo hard fork update proposal, which will take effect at 21:44:51 UTC on September 12th, bringing Alonzo to mainnet.
The team also resumed working on flakes for the GraphQL stack, integrated newly released ERC20 converter versions, and continued some other infrastructure provisioning.
This week, the team worked on Alonzo benchmarking activities. They delivered benchmarks for node v.1.29, which proved no significant performance regression since node v.1.27. In addition, hard fork simulations showed no resource usage regressions. The team discussed relevant Plutus workload activities.
The team also enhanced trace generator performance, found a UTXO missing witness issue that is now being resolved, and also made some internal cleanups.
The team progressed on the node logging infrastructure rewrite and started the trace-dispatcher review and testing. They tested multi-threaded traces and runtime reconfiguration, refactored and simplified the Cardano tracer based on review suggestions, and started implementing the initialization case for trace-forward queue management.
Work is ongoing within the RTView, which the team started porting to the Cardano tracer.
Finally, they began working on the analysis improvements within the benchmarking infrastructure to enhance block boundary resource usage statistics in Marlowe Run and connection to the PAB.
This week, the Plutus team resolved some synchronization problems and updated the chain index with more enhancements. They also analyzed the costing and sizing of Plutus scripts and made some general performance improvements. Finally, they updated the Plutus documentation and tutorials.
The Marlowe team continued working on annuity (ANN) implementation, validated negative amortizer (NAM) properties, and made some refactorings. They also reviewed Marlowe documentation, recorded videos for the Marlowe website, and automated some staging deployments. Finally, the team set up analytics for the Marlowe Run website.
This week, the team released Daedalus v.4.3.0 for the Alonzo testnet. They improved the stake pool ranking feature using the desirability parameter, which is now in the QA testing phase.
Finally, the team continued working on the custom browser protocol implementation.
This week, the team released the Adrestia components (cardano-wallet, GraphQL, Rosetta API, cardano-explorer-app) ready for the Alonzo hard fork on the testnet. They also updated and tested the metadata tools to support Plutus scripts minting native tokens, and added Catalyst voting support to cardano-rosetta.
The team is now working on changes required for smart contracts, including collaterals, the coin selection update, fee calculation, etc., and are also implementing some fixes and optimizations.
This week, the team resolved different issues related to the acceptance of existing network connections, enhanced connectivity with the node, and investigated a ‘query tip’ bug found in Alonzo.
This week, the team deployed the Alonzo testnet upgrade to the ledger and were busy preparing for the mainnet hard fork. They also updated the ERC20 converter to work with the node v.1.29.0 and the latest version of the wallet. Finally, they worked on ipxed to serve NixOS images on the network.
This week, the team completed the final testing of the internal ERC20 converter. They tested it against the latest node deployed after the Alonzo testnet hard fork this week. The team has now provided the code to SingularityNET for final assessments and production readiness in their environment prior to testnet deployment. Stay tuned for more announcements coming soon.
This week, the team started performing Alonzo testnet benchmarking activities. They made progress on automatic profile statement insertion, fixed some compiler and let-floater issues, and added new documentation for cost model parameters.
The team also continued working on Hydra development, fixing various issues in the coordinated Head protocol, and running benchmarking load tests for a cluster of three local Hydra nodes.
This week, the Plutus team worked on the Plutus Application Backend (PAB) and updates to the chain index. They also added missing helpers to plutus-tx, plutus-ledger, and plutus-ledger-api and fixed some synchronization problems.
The Marlowe team worked on cards within the Marlowe Run client and on error handling for Marlowe contracts. They also updated the Marlowe tutorial and documentation.