This week was an important one because of several strategic decisions that help create a healthier long-term outlook for both the project and the ecosystem.

Tokenomics and Long-Term Alignment

Following recent community discussions around the token and tokenomics, we took the opportunity to revisit several open topics and make decisions on items that have remained unresolved for some time.

As Matthijs shared during the recent AMA, we have decided to unlock all remaining presale tokens. While this is not necessarily the easiest decision in the short term, we believe it creates a healthier long-term outlook for the project. Rather than carrying uncertainty around future unlock events, we prefer to address the situation directly and remove the overhang once and for all. While it may create some short-term pressure, it significantly improves transparency and predictability moving forward.

The claim portal is being reworked currently, please wait for a follow up announcement with more information. Until then, the claim portal will remain unchanged.

Helix Mainnet Timing

In the same spirit, we also reviewed the timing of the Helix mainnet rollout.

For Helix to be successful, it needs to be driven by real-world demand and genuine business use cases rather than launching purely for the sake of launching. Once mainnet goes live, node rewards and related token incentives become active, which introduces additional token emissions and potential sell pressure.

Because of that, we believe mainnet should be coupled to tangible customer demand and meaningful utility from day one.

This does not mean Helix is standing still. As shared previously, the vast majority of the core development work has already been completed. The focus now shifts toward aligning launch timing with real customer adoption and stronger market conditions.

We understand the community's desire to see progress, but we believe a demand-driven rollout ultimately creates a much stronger foundation than a launch driven purely by timelines.

Improving the Intelligence Layer

On the technical side, a large part of our effort continues to focus on improving the intelligence layer within Nexus.

As more users interact with the platform and active pilots continue, we gain valuable insights into how people actually work with Nexus. Usage patterns, user feedback, and operational workflows continuously reveal opportunities to improve the experience.

Much of this week's development work focused on strengthening contextual understanding during conversations.

We improved how Nexus maintains and utilizes conversational history, allowing the platform to better understand previous interactions and maintain context throughout longer discussions. This results in more accurate responses, improved continuity, and a more natural user experience.

While these improvements may appear relatively small from the outside, they directly impact usability and adoption. Many of these enhancements touch the core intelligence architecture of Nexus, requiring significant development effort despite appearing as relatively subtle user-facing changes.

The result is a platform that continues to become more accurate, more contextual, and more useful in real-world operational environments.

Google Marketplace Progress

We also continued making strong progress with the Google Marketplace deployment.

At this stage, Nexus has reached what Google refers to as a privately published state. This means the deployment and infrastructure side of the marketplace integration is effectively complete and functioning as intended.

The remaining work primarily revolves around marketplace-specific behavior. For example, customers deploying Nexus through Google Marketplace will be billed directly through Google, meaning certain SaaS subscription components need to behave differently compared to customers using Nexus through our traditional SaaS offering.

To support this, we are implementing a feature-flag framework that allows Nexus to dynamically adjust behavior depending on the deployment environment.

Healthcare Outreach and Early Validation

On the business development side, we officially started engaging with contacts across the healthcare sector following the completion of our healthcare proposition.

This has already resulted in several initial conversations and expressions of interest. While it is still early, the first responses have been encouraging and we are now working toward converting these discussions into product demonstrations and more structured opportunities.

Healthcare remains one of the strongest examples of how operational intelligence can create value by connecting fragmented operational and medical information into a single decision-support environment.

We expect to share more developments in this area over the coming weeks.

Learning from Active Pilots

The existing pilots continue to be actively used and tested by customers.

One particularly interesting insight emerged during a recent feedback session where we learned that Nexus is effectively being evaluated alongside Microsoft Copilot in a real-world environment.

The feedback highlighted an interesting distinction.

Copilot appears to perform strongly when working primarily with unstructured information and document-centric workflows. Nexus, on the other hand, demonstrated stronger performance when working with structured datasets and operational data environments.

This is both encouraging and valuable.

It reinforces the strength of our approach while also helping us better understand where customers place the most value and how decision-making criteria evolve during evaluation processes.

These types of comparisons provide valuable guidance as we continue refining the product and sharpening our positioning around operational intelligence.

Looking Ahead

Whether it was resolving long-standing tokenomic questions, aligning Helix with real-world demand, improving the intelligence layer, advancing Google Marketplace readiness, or validating our healthcare proposition, the common theme remains the same: building sustainable value rather than chasing short-term milestones.

The coming weeks will focus on continuing this momentum while expanding healthcare outreach, progressing active pilots, and further strengthening Nexus as an operational intelligence platform.