Shelley Incentivized Testnet Development Update - 13 March 2020

In this Shelley Incentivized Testnet Development Update video series, Project Manager Dimitris Poulopoulos will be taking you through the updates on a regular basis.

Full transcript below:

Hi everyone. It is Dimitris again, back for another week to share another quick update on the Shelley Incentivised Testnet progress.

Thanks again for the valuable feedback on these weekly video updates. Please continue to share your thoughts on how we can improve further in order to help us try to bring you more useful information.

Recap
We’ve seen some good improvements in network stability after making that our focus over the past weeks. We’re now running at around 99% uptime, which is a significant improvement.

Last week we had another Node, Wallet BE and Daedalus release that was integrated with the latest Jormungandr version 0.8.13 which should bring further improvements for both ADA holders as well as stake pool operators.

This week

Jormungandr

Last couple of weeks the team worked to bring the network modules and other node internals up to date with the latest Rust async stack, and started also to work on incentives changes now that the network is more stable.

Key changes introduced in the latest Jormungandr version includes:

  • Updating the documentation to make sure we use the --locked `Cargo.lock
  • Resolved some rust compilation issues as rust was throwing up compile errors and failing. Those errors have occurred when compiling jormungandr 0.8.13, jcli 0.8.13 and also jormungandr-0.8.9-stable-alpha6.
  • We added a parent hash for created blocks in leaders logs in order to see the parent hash of any a block that has not been validated. This information could only be found in the node log with INFO log level until now.
  • Added REST API to access the reward distributions. For a full reward distribution dump you will need --rewards-report-all to be set when starting the node. Note: If you are on a small CPU machine or if you don’t need to see all reward history for everyone please do not use as memory/CPU consumption will be increased significantly. This is not necessary for a wallet client or for a stake pool but build more to be used on an explorer or a tool to monitor stake pool rewards or performance.

As always, you may find more information on the Jomungandr repo under https://github.com/input-output-hk/jormungandr/releases/tag/v0.8.14

Daedalus and Wallet BE

Recent Daedalus (2.3.0-ITN1) release introduces new versions of the cardano-wallet and Jormungandr node, which should improve Daedalus connecting and syncing times.

The community response seems positive and all of the recent issues related to wallet restoration including the “wallet already exists” are now mitigated.

MacOS Catalina users are still impacted by the current installation issue around Apple notarization. There has been progress on the certificates creation and our Devops team is now working to build the scripts that will resolve the notarization issue, expected within a matter of days. We appreciate your patience on this. Our aim remains to release another Daedalus version once this issue for MacOS Catatlina users is addressed.

We will let you know as soon as this new Wallet version is available and if you are running your Daedalus rewards wallet you will get notified through Daedalus newsfeed.

Side updates

Support: This week has been quiet on the support side. Our latest Wallet release (2.3) has introduced further improvements in the connectivity, synchronization and wallet restoration areas, which is resulting in lower ticket volumes. The MacOS-related issue still remains active, but we are approaching a solution and hoping to have this resolved in the next few days.

At a glance, we have seen:
New incidents - 248
Resolved incidents - 326
Incident backlog - 479

DevOps: Our Devops team worked on using the latest certificates and have now also restructured the Mac packages a little more to comply with Apple’s code signing structure. Now we have addressed this, we hope this won’t be an issue we’ll see with future releases.

I hope you found this short update useful. I’ll be back next week with the latest on ITN progress. Thank you for watching and stay safe!

1 Like