![](\"https://d21buns5ku92am.cloudfront.net/69390/images/585524-ezgif.com-optimize%281%29-99b8ab-original-1744036713.gif\")
Planned Infrastructure Enhancements Coming in Q2As recently announced, the Humm Hive hApp was successfully deployed on a HoloPort running Cloud Nodes on the new Holo Network. This deployment demonstrated immediate performance improvements (on the scale of 5x page load time reduction over Legacy) when the Humm user interface (UI) connected to the hosted workload via Holo’s Web Bridge to make HTTP calls, triggering zome calls in the hApp being hosted on the HoloPort. Notably, both hApps were running the exact same version of Holochain under-the-hood. This successful demonstration validates the effectiveness of the Web Bridge and the advancements of Holo’s Allograph network and Holochain Cloud Nodes. This is a strategic evolution enabling decentralized applications to bridge to traditional web environments, aligning with the original vision of Holo to drive Holochain adoption by making it more compatible with Web2.
Planned Infrastructure Enhancements Coming in Q2The focus for Q2 is on enhancing the Holochain Cloud Nodes infrastructure for scalability, reliability, and security. Key planned improvements include:
These deliveries are aimed at making Holo easier for developers to use, adopting a more standard approach compared to other cloud services, and improving self-service and onboarding flows.
The migration of HoloPorts over to Holo’s new Allograph network remains a priority. New functionality allows collecting inventory information from HoloPorts running the new holo agent, even on the Legacy network. The migration plan involves:
Significant effort is being directed towards the development of the Public API. Progress includes:
The Public API is crucial for empowering developers with enhanced integration capabilities, fostering innovation, and expanding the range of applications that can utilize the platform.
The Dev Team’s current iteration focuses on rate limiting, logging, API usage tracking, CI/CD pipeline reuse, DNS server enhancements, NATS blob store integration, and specific host workload deployment. Legacy network state information is being added to the inventory system.
Regarding HoloFuel, Alistair Ong reiterated in our last Delivery Brief livestream that it has always been intended as a compute-backed currency, and expanding the Holo network to support more compute types will strengthen it. The timeline for HoloFuel to be fully operational remains with Unyt. Mary Camacho added that the current developments in hosting are fundamental for both HOT and HoloFuel.
Mary Camacho addressed concerns about the price drops of the HOT token, stating that HOT matters significantly to Holo, as does HoloFuel. She attributed the current market situation to broader economic chaos and emphasized that delivering a usable hosting network with real customers is crucial for the long-term value of HOT. Regarding listing on US exchanges, Holo is actively working on it, but the timeline is not solely within our control due to the regulatory processes involved.
Nathan, Holo’s community manager, addressed rumors about his identity during the Delivery Brief livestream, confirming his role and genuine presence within the community. (Lumi had her first ever livestream cameo too.)
Alistair Ong clarified that hosts will be able to see a return on their investment when their HoloPort is randomly selected for a customer deployment, underscoring the priority of increasing demand on the network.