July 10, 2020
Status Updates (July, 2020) > July 10, 2020
This week the team implemented stake pool ordering based on the delegated amount. The team also integrated support for Trezor hardware wallet and an automatic application update mechanism.
This week the team worked on the TipSample protocol, which will be used to sample the remote node’s tip of the chain. This information will provide long-term insights about which peers are worth being promoted from warm to hot states. The team also made progress testing DeltaQ computations used by the block-fetch protocol.
This week the team tested the hard fork combinator and made faucet improvements to support captcha. They also updated local cluster scripts to support the node version 1.15.
This week the team worked on bug resolutions (#1281 and #1312). The team has now added all the property tests to find possible bugs.
Also, the team constructed a relational algebra code to replace the relation type class, which will provide a greater performance boost. It is a work in progress, but major challenges have been worked out, which enabled the team to start the integration process.
This week the Plutus team worked on JSON updates: in the smart contract backend (SCB), the test JSON file was expanded to include more kinds of events to decode. On the front end, the JsonMap was updated to successfully decode
null as an empty map, and some encoding errors were fixed. Finally, the team added copy-to-clipboard support for the long blockchain IDs to make it easier to copy the full version.
This week the Plutus team made improvements to the Events page in the smart contract backend (SCB). They made improvements to the management of contract instances and reduced the Plutus Playground instance size. Finally, the team updated the GHC package that is in use for Haddock.
The Marlowe team began working on the addition of a new wallet simulation tab in the Marlowe Playground. This tab will enable users to understand what features a wallet needs to be able to run Marlowe contracts and how a contract behaves in relation to multiple wallets.
The team also added a mechanism to send code from the Haskell Editor to Blockly and updated the color scheme used in Blockly.