Minor Releases – Holochain 0.5.4 & 0.4.4: We found a bug where the code that ensures zome-call atomicity failed, i.e. if the zome call returned an error a commit might still be added to your chain. This bug has been fixed and is being released in Holochain 0.5.4 and back-ported to Holochain 0.4.4 release. The 0.5.4 release also includes additional debug-logging output that should help us better understand some of the circumstances where WebRTC connections are spontaneously dropped.
HTTP Gateway Update (0.2.0): HTTP Gateway that provides a way to bridge from the web2 world into Holochain has been updated for compatibility with Holochain 0.5. We have updated and released it (https://github.com/holochain/hc-http-gw)
Developer Focus: Our focus is now directly visible on the Roadmap (holochain.org/roadmap), for details see the blog post (https://blog.holochain.org/introducing-the-new-holochain-roadmap/). You will see there that focus has shifted to Holochain 0.6, highlights of which include:
- Conductor State refactors address problems in inconsistent cell state
- Ability for coordinator zome updates
- Extending memproof gating to the network level.
New Dev Hires: Our two new team members are onboarding quickly and will both focus on fleshing out our Wind Tunnel performance testing framework, adding new scenarios, and reporting.
Dev Office Hours: July 9th recap
We were excited to have an inquiry in our Office Hours about use of our Kitsune2 p2p data-synchronization layer in a stand-alone project. This library is ready to be used in other projects, and so despite the fact that we haven’t yet created really good dev documentation for it we were able to provide pointers to the showcase app (https://github.com/holochain/kitsune2/tree/main/crates/kitsune2_showcase) that demonstrates its stand-alone use. We are looking forward to seeing how that goes, and if anyone else is interested in this, please keep us in the loop.
