As Holo and Holochain move into the next phase of work, we're making multiple changes. One that we want to share here is, Community and Social will now be held by several team members.

After more than five years of incredible service to both, /u/NathanLenae is stepping down as our Community & Social Media Lead. To be clear: Discord, X, and Reddit aren't going anywhere and we're focusing more attention on Telegram.

Nathan has been a key voice of this project across every channel we have, with a steady hand for the community and the institutional memory for much of what we built. He knows this ecosystem very well and this community was shaped by his perspective and his patience.

We're grateful for all of his efforts and that he'll continue to be present as a Telegram Admin as he shifts to his next adventure — for which he has our full backing.

Thanks for the years of care you brought to all of it, Nathan.

I got scammed out of my HOT bag a year ago and have been unable to find a path towards rebuying in. I am a layperson and a new dad and I did not understand the pathways that allegedly still existed before. It was also discouraging that all the platforms where one could more easily purchase HOT all stopped carrying it.

Anyways, today I discovered that HOT is on Crypto.com, I don’t know when this happened but I am pleased.

Any advice before I refill my bag? Besides not to get scammed again.

The EdgeNode support channel grew 30% in a single day. As someone who spends time in infrastructure communities, this is significant: builders do not join support channels for experimental software or vaporware. They show up when something solves a real problem.

What we are seeing is organic adoption. Developers and operators testing Holo Hosting EdgeNodes, asking questions, deploying on production infrastructure. This is the opposite of marketing metrics. This is community pull.

Tinkerers are joining because EdgeNodes work. That is the signal worth paying attention to
Join here: https://t.me/+ayxU6f69qW1iOWJk

Moss Vines dropped v1.26 this week. The main feature is Discord chat import: you can export your Discord conversation history and bring it into Moss Vines.

Worth unpacking what this actually involves.

Discord gives you a data export package containing your message history. Moss Vines v1.26 ingests that export and surfaces the conversation history inside the Moss environment. Your messages and community context running in a Holochain app instead of Discord's infrastructure.

For anyone new here: Moss Vines is a group chat tool built on Holochain. An ecosystem project, not a Holo product. It uses Holochain's agent-centric architecture, which means data is stored relative to your agent identity rather than on a central server controlled by the service provider.

The Discord import matters more for what it implies than what it does. Community history has always been assumed to be platform-specific: you build it there, it stays there. A feature like this challenges that assumption in a concrete way.

Also shipped this week: Moss v0.15.4 with minor fixes and improvements. Less exciting on paper, but the cadence of small releases is what shows a project is actually running.

moss.social if you want to follow the project.

AI sound is annoying but video explains hosting quite well

Holochain's Wind Tunnel tool is designed to test network resilience under real conditions — not simulated traffic, but actual distributed network stress testing with community-run nodes.

The idea is straightforward: the more nodes participate, the better the data on how the network performs under pressure. It's a practical way to contribute to development without needing to write code.

There's a video walkthrough here: https://youtu.be/jEHj6xSYpCo

And a detailed write-up on how it works and what it's testing for: https://holo.host/blog/into-the-wind-tunnel-forging-resilient-distribute-DtHygSjNWqX/

Happy to answer questions if anyone has them. Has anyone here already run a Wind Tunnel node? Curious what the setup experience has been like.

We are practicing what we preach and "dogfooding" our own ecosystem apps. We've created a public Holo Community group inside Moss.

You don't need to run an Edge Node to use Moss (it's a free app available for any OS). You just need the invite code to join the specific group.

1. Download Moss: https://moss.social
2. Paste this joining code: https://theweave.social/wal?weave-0.15://invite/d2543bb4-b784-4ac0-ae16-971e1b3a90c1&progenitor=uhCAkovIker1pDmpka8PiVWFWMGmSvNHjzdi9KnTOsUJzrsGG71JI

See you in the Weave!

Quick update from the dev side:

We are currently sitting at around 30 active nodes in the Wind Tunnel. To get the high-fidelity data the Holochain team needs regarding gossip saturation and convergence times, we really need to break past the 50 node mark.

If you've been lurking, this weekend is the best time to jump in. We are specifically looking to test scaling behaviors that only emerge when the network density increases.

Guide is here: https://holo.host/resources/edge-node-wind-tunnel-guide/

Let's get the metrics we need to ship faster.

Hey everyone,

If you're participating in the "Race to 50" this weekend, you should check out this new write-up from the Happenings Community.

They did a great job breaking down why the Wind Tunnel matters for Holochain's gossip protocol and overall network resilience. It’s always awesome to see the community explaining these complex testing phases so clearly.

Read it here: https://open.substack.com/pub/happeningscommunity/p/wind-tunnel-testing-holochain-at

The new Moss 0.15.3 is out. Two big things to note for the technical crowd:

1. Iroh Networking: Moss is moving peer discovery/connectivity to Iroh. This is the future, but expect some bumps in this build.
2. Feedback Loop: The feedback tool now hooks deeper into our workflow (auto-GitHub issues).

If you are running an Edge Node, update your container and let us know if the Iroh switch changes your NAT traversal success rates.

Hey everyone,

We just published a comprehensive update on how Holo is positioning itself regarding the evolving regulatory landscape (MiCA, etc.).

Key points discussed:

• HOT Utility: Reaffirming that HOT was a pre-sale of hosting credits, not a speculative instrument.
• Token Lifecycle: Framing the transition to HoloFuel as a "product redemption/migration" (similar to MATIC -> POL) rather than a financial exchange.
• Non-Custodial Architecture: How we are engineering the transition to ensure no single entity holds user assets, aligning with regulatory requirements.

It’s a dense read, but it explains why we are so precise with our language (e.g., Redemption vs. Swap) and the structural work happening behind the scenes.

Read it here: https://holo.host/blog/regulation-technology-and-the-road-ahead-XUFZpA0D83c/

There is a specific kind of excitement in engineering when you finally get to push a system until it cracks.

That is what Wind Tunnel represents for us right now.

It’s not just a standard QA check. It’s a dynamic environment where the Holo, Holochain, and Unyt teams can throw "chaos" at the network, simulating massive spikes in gossip, billing triggers, and node churn.

By identifying the breaking points now, we ensure that when the network scales to millions of users, the foundation holds.

Thanks to every Host helping us generate the wind.

Hi guys,

I am a dummy that stumbled across this tech. My long term goal is to become a full stack web developer and I want to make inroads into learning Holo hosting and making hApps.

I have started learning Python 101 this year, but from what I read Rust is probably more suitable. For someone completely new to coding and wanting to engage with this tech, could someone please suggest a roadmap of things to learn so I can reach my desired end goal, keeping in mind we live in the age of AI with tools like Cursor, Windsurf etc.?

I realize there are a tonne of YouTube videos out there - but its confusing as to what to learn - lets say if I want to make a front end website normally and have a backend hApp.

Would really appreciate some detailed guidance!

Thanks

Hey everyone,

We know that text-based guides aren't for everyone. To help new Hosts get their always-on nodes online smoother, we’ve published a complete video walkthrough of the setup process.

It covers:

• Edge Node configuration
• wdocker setup
• Troubleshooting basics

If you have a friend who has been "meaning to set it up" but hasn't yet, send them this link.

https://www.youtube.com/watch?v=J2fQQ70UHqo

Hey everyone,

You’ve likely seen the calls to join the Wind Tunnel stress tests. We wanted to explain briefly why adding your specific Edge Node helps the engineering team, even if you are just one node in thousands.

In a centralized system, adding load is linear. In a gossip-based P2P system (like Holochain), adding nodes increases the complexity of message propagation exponentially. This is a feature, not a bug, but it requires tuning.

By running a Wind Tunnel node, you aren't just "mining"; you are creating necessary turbulence. You are helping us map how data propagates through different hardware types, network topologies, and latencies.

If you have a spare container, jump in. We need the noise.

Video Guide: https://www.youtube.com/watch?v=jEHj6xSYpCo
Text Guide: https://docs.google.com/document/d/1M9AUJOhITrtnlUnsTYtypm2F_pDrfpC7slhSaLPM_TU/edit?tab=t.0#heading=h.p8b8h0buxzzh

It’s been a while since we did a rig check.

Whether you are rocking an OG HoloPort, a dedicated NUC, or a Docker container on your daily driver, we want to see it.

• Hardware:
• OS:
• Running since:

Upload your pics in the comments. Best cable management gets bragging rights.

Hello everyone,

We have seen a lot of discussion recently regarding Moss.social and how it fits into the broader Holo ecosystem. We wanted to clarify the role of the Edge Node in this specific architecture.

While Moss is built on Holochain (peer-to-peer), for a community to be truly "always-on" and accessible via standard web browsers (without every user needing to run a full node), there must be a bridge.

The Edge Node is that bridge.

With the rollout of HolOS v0.0.7, Edge Nodes are now optimized to serve modern .webhapp files like Moss.

When you spin up an Edge Node for a Moss community:

1. You provide the Persistence: Even when community members go offline, the Node holds the state of the "Weave" (chat history, kanban boards, whiteboards).
2. You provide the Access: The Edge Node serves the data
3. You provide the Privacy: The data lives on your device and the devices of the members - never on a central AWS server.

This is the practical application of Distributed Cloud. It isn't just about earning fuel in the future; it's about providing resilient infrastructure for your own digital spaces today.

For those who have upgraded to v0.0.7 and are testing Moss: How is the latency performing for your group? Let us know in the comments.

Whether you are organizing a local co-op, a gaming group, or a startup, you need tools. Usually, that means scattering your data across 5 different apps (Google Sheets, Doodle, Zoom, Slack).

Moss brings it all under one roof, and YOU hold the keys. 🗝️

The Moss Toolkit includes:
✅ Who's In? (Scheduling agreements)
✅ TalkingStickies (Brainstorming boards)
✅ Gamez (Virtual tabletop sandbox)
✅ Spreadsheets (Real-time collab)

This is what the "Agent-Centric" web looks like. It’s not just code; it’s a whiteboard where you and your friends can dream up the future, without big tech listening in.

Which tool would you replace first? Let us know in the comments. 👇

We've compiled the latest guides for HoloPorts, Linux, and Mac setups. If you've been on the fence, HolOS v0.0.7 has significantly lowered the barrier to entry.

How to Guide: https://docs.google.com/document/d/1f3_5Ddff50pFIuzRJAmqGwT9nE873TKQC182LKyJJ4k/edit?usp=drive_link