July 16, 2021
Status Updates (July, 2021) > July 16, 2021
This week, the team worked on the Electron update, which is in the final QA and testing phase.
The team also made good progress implementing rewards history view while completing the implementation of an ‘Emptying a wallet’ warning and some additional UI/UX improvements.
This week, the team remained focused on Alonzo/Plutus core features.
Specifically, they continued working on streamlining cardano-wallet transaction APIs to enable Alonzo/Plutus features, and also began updating cardano-wallet to the future Alonzo Node (v1.28).
The team also prepared cardano-graphql v5.0 for release and moved it to QA. This version is compatible with db-sync v10.0.x
They're also working on updating cardano-explorer to enable compatibility with GraphQL v5.0, and also updating the cardano-rosetta API to enable compatibility with db-sync v10.0.x).
This week, the team upgraded the P2P switch, worked on network tracers, fixed some tests, and merged the server simulation. They are now in the process of running simulation tests.
This week, the team were busy preparing for the Alonzo White launch. On July 14, the teams successfully forked the Alonzo testnet to the new Alonzo White node. The new network is now producing blocks, and besides the core SPO group, Project Catalyst members and more Plutus partners have joined Alonzo White testnet activities. Meanwhile, IOG quality assurance and other teams continue working on the feature testing.
This week, the team continued working on Cardano to Ethereum token migration within the converter. They investigated different development scenarios and found related solutions to also improve the Ethereum to Cardano migration process. This influenced the decision to deploy all improvements within one release without separating overall functionality. Therefore, the ERC20 converter testnet will require several further weeks of development but will be deployed featuring a greater number of updates and functional features. This will not influence the mainnet release, which is planned for deployment around the dates of the Alonzo mainnet hard fork.
This week, the team worked on the Merkle trees design documentation, finalized Marlowe Run redesign based on user testing results, and continued working on the Marlowe Run infrastructure improvements. They validated the LAM contract against the ACTUS test suite and investigated ActusLabs issues in the Playground, also generating ACTUS examples for Plutus testing.
The team implemented a feature that allows the state machine to produce thread tokens, fixed a handshake connection issue to the Alonzo node, and also changed the time resolution property in Plutus to enable the use of milliseconds.
More work has been done within the Plutus Application Backend (PAB) development. The team worked on PAB documentation, enabled optional permissive CORS policy, and also enhanced chain index operations. Along with that, they produced an example application that waits for a blockchain event, and continued PAB to Alonzo synchronization process.
Finally, the team prepared for the ‘Hosted PAB’ workflow, which will enable the use of textual links with partial transactions, and started working on contract API UX improvements.
The Plutus team worked on PAB amendments to increase waiting times for the uniswap traces, which allows retrieval of state information for contract instances that have stopped. Additionally, they fixed a response timeout used when evaluating contracts in the Plutus Playground.
The Marlowe team implemented a new design for contract cards within the Marlowe Run dashboard and worked on documentation and tool tips.