{Dev Bytes}: February 13th, 2025

Over the past few Delivery Brief livestreams and text communications you have heard us say “next-gen” or “next-generation” Holo network. We are replacing “next-gen” with a new name, Allograph. Why Allograph? The word Allograph means a signature or something written on behalf of another— which we think is fitting for a network designed to host applications for others.

6 HoloPorts are actively running the Allograph host agent and we are working to test and verify other configurations of HoloPorts before we rush to get all HoloPorts on Allograph. 

Our Current development efforts are focused on:

• 1) Authenticating & Orchestration: Ensuring HoloPorts can securely authenticate and interface with our central orchestration service

• 2) Expanding Workload Capabilities: advancing the workload runner to support a broader range of workloads beyond Holochain Applications that can be run on the HoloPorts 

• 3) Network Inventory & Health Checks: Establishing a reliable process for assessing HoloPorts before migration to Allograph and as part of an ongoing network health monitoring routine. 

In terms of the authentication work that’s underway, this is an important prerequisite for all HoloPorts to proceed with the migration update itself. The relevant keys to be authenticated in this case are the same keys generated during the Holo Quickstart process in our registration workflow. This means for any HoloPorts that have not yet generated keys using this method, you’ll need to first complete this step before your HoloPort can upgrade to Allograph.

Once the authentication and inventory work is ready, we’ll proceed with installing the Hosting agent and continue migrating the HoloPorts that are already registered and passing all health checks. This process helps us take care to minimize the impact to hosters and our support team.

Although our team is focused on delivering the Allograph network, as it allows us to host more workloads than Holochain workloads alone, we're still supporting our legacy network and will continue to do that for certain projects inclusive of the Holochain foundation because so much of the reliability testing that is happening by the Holochain team depends on that earlier network model.

Our devs have gotten as far as initiating Hivello device activation by using the new container-based workload mechanism on a HoloPort running legacy HPOS. To proceed beyond activation we will be coordinating with the Hivello team to release a headless version of their software that we will then integrate and test on Allograph. 

We have been diligently working on releasing a public Holo Roadmap which we aim to publish in visual form towards the end of this month. 

Some of the Highlights we can share here are:

• Gossip Nodes (always on hApp nodes) Q1 2025

• Web Gateways Q1 2025

• Static file hosting - for Holochain apps - this is the UIs, but more generally this can be any static file, so look for more generalised options in Q2 2025

• And more later in Q2 2025 (which will be visible when we publish the roadmap)