Humanode Announcements

Humanode incident update: security fixes and recovery The incident has been contained, and all identified security issues have been fixed, including the EVM vulnerability and the unauthorized approval affecting the ChainPort vault. The full investigation continues. We deployed the EVM fix on mainnet at 15:40:48 UTC on 28 October 2026. Verification confirmed that the exploited call paths are blocked. We are sorry for the losses and disruption this incident caused. All eHMND lost as a result of this incident will be reimbursed in full to its owners. We will restore and rebalance the affected eHMND/USDC pool. The confirmed impact was localized to 436 EVM accounts, including the ChainPort vault, with 12,773,243.03 eHMND taken. Native-side HMND balances outside the EVM were not reachable through this vulnerability. The DEX, bridges and LP staking will be frozen for 72 hours from publication of the original announcement to manage the imbalance and allow further audit and investigation. Freeze starts: [20: 21: 00 UTC] Freeze ends: [ 72 hours from Freeze start time] We will share further confirmed findings and the details of reimbursement and pool restoration through official Humanode channels. Full incident report and recovery update: https://blog.humanode.io/humanode-incident-response-and-recovery-update/

Humanode Newsletter Vol. 124 is live! This cycle, Vortex started showing what real governance looks like in practice: 🌀 Three projects in Formation, milestone votes, funding releases, and rejected proposals 🗳 Dev Log #21: a fairer way to calculate Active Governor status 🎮 A refreshed Vortex UI built to feel more like a grand-strategy console 💸 A new transaction-fee model 🎙 OpenServ on agent reliability and SERV Reasoning 🧬 BotBasher Gen. 9 and a fresh biometric cycle 🤖 Who Authorized This? on AI agents, delegation, and responsibility 🌐 HumanodeCon V is going online this year 🎨 Humanode Sticker Pack 2 contest is open Read the full update: https://blog.humanode.io/humanode-newsletter-vol-124/

While you are busy making stickers, here's some food for thought from Vortex

Calling all Humanode artists, meme lords, and AI prompt wizards! The Humanode Sticker Contest is ON! We're building Humanode Sticker Pack 2, and this time, YOU get to decide what Humanode looks like in chats. Vortex? Biomapper? BotBasher? One human, one vote? Or a legendary Humanode GM sticker? Get creative. Get weird. Just keep it Humanode. 10 winners get $20 in HMND each! How to enter: 1. Create an original sticker (PNG/WEBP, transparent background, one side exactly 512px). 2. Share the announcement and your sticker on X with #Humanode #HumanodeStickerContest. 3. Submit your X post link in the Humanode Discord's #humanodes-got-talent channel. Deadline: November 6, 2026, midnight. Use AI, draw by hand, whatever works. Just bring some actual creativity. Full contest details: https://blog.humanode.io/humanode-sticker-contest-2026/ May the best stickers invade our chats!

We are again updating CVM for confidential biometric checks. Please enroll and auth.

Join us on the community call in Discord! https://discord.gg/WheJAwrYy?event=1467927462011994387

We really thought that another update of biometric tech would take us a lot of time, but devs shipped 10x faster than expected! So yeah, every human node has to: 1) update the peer to the latest version, 2) enroll and 3) bioauth again. BotBasher and Biomapper biometric resets will be announced later.

Hey humans, your BotBasher badge called. It wants a refresh. Discord BotBasher is now on Gen. 9, and Telegram has received a fresh update too! That means it's time for users to redo their face scans and server admins to make sure their communities are running on the latest generation. Same private and secure 15-second scan, with more bots getting bashed. We've put together a quick refresher for admins and users on both platforms. Get your human badge back: https://blog.humanode.io/botbasher-got-an-upgrade-your-human-badge-needs-one-too/

Hello human nodes! Enjoying the action? Here's some Vortex wisdom

The Humanode Community Call is happening today! And it’s in 1.5 hours. As always, you can jump on stage, ask the founders questions, and share feedback. Today 14:00 UTC https://discord.gg/rKBwtAtS4?event=1467927462011994387

As part of our regular server reset, the CVMs behind Humanode chain, has been refreshed. Biomapper and BotBasher are scheduled for tomorrow. These resets are done to wipe previously stored biometric-linked data, refresh the system, and start with updated infrastructure and security. They also give everyone a fresh chance to re-link the right account or address where needed. Reminder: If you have not done it yet, please complete the new cycle: today right now: • Enroll Re-authenticate your human node tomorrow: • Biomap on Biomapper • Re-verify on BotBasher

How decentralized is your DAO if one whale can outvote the community?

You ask an AI agent to reduce your cloud costs. It delegates the task to another agent, which deletes an important archive. Who authorized the deletion? As AI agents begin making decisions, spending money, and delegating tasks to other agents, the question of responsibility becomes harder to answer. Tracing which agent performed an action is one thing. Tracing who gave it authority, what limits applied, and whether those limits survived delegation is another. In her latest article, Sasha Shilina explores this growing problem. If an AI agent exceeds its authority, who should be held responsible: the agent's operator, its developer, or the person who gave the original instruction? Read the full article: https://blog.humanode.io/who-authorized-this/

The journey continues, and so do the updates. Although the Vortex was already fairly easy to use, we decided to take it a step further and refine the UI/UX. No matter how comprehensive the format is, if the UI makes you feel like you are at “work,” using a logical but “worklike” and “serious” tool, it is hard to retain those with a more intuitive and creative heart. So, to revitalize the “work hard” but “play hard” spirit, our team tweaked the interface a bit to make our tool that helps shape the future feel more like a “grand strategy console”. Naturally, since this is no game and the Vortex will be shaping our actual future, we are also working on a few more features and tools based on feedback before we move the whole Vortex on-chain, which will be announced soon. If you are on Vortex, go check it out and give us feedback! If you are not on Vortex yet, this is your chance to get involved! https://vortex-simulator.humanode.io

We are changing transaction fees for the Humanode chain. Until now, we have kept fees at a minimum to help subsidise the network’s bootstrap phase. Now, it is time to set fees that will help pay for decentralization. All transaction fees go to human nodes and governors. The more human nodes and governors the network has, the more decentralized it becomes. And decentralization, the core promise of a blockchain, does not come for free. For now, fees will be adjusted based on the HMND token price. This is another step on our path toward a cost-based fee system. https://blog.humanode.io/humanode-transaction-fees-are-changing-a-fee-model-for-a-more-decentralised-humanode/

A Governor should only be judged on votes they actually had a fair chance to cast. Vortex Dev Log # 21 changes how Active Governor status is calculated: • Governors now need to participate in one-third of their eligible Proposal Pool and chamber-vote opportunities, rounded up. • A vote only becomes a participation requirement after the stage has been open for 24 hours. If it closes earlier, missing it does not count against the Governor. • Authors, Formation team members, and others excluded from specific votes no longer have those impossible votes added to their required activity. • And when a milestone or reconsideration opens a new chamber vote, it counts as a separate opportunity with its own eligible voters. Plus, Formation teams also get a clearer application, acceptance, and membership process. Read the full update

A Governor should only be judged on votes they actually had a fair chance to cast. Vortex Dev Log #21 changes how Active Governor status is calculated: • Governors now need to participate in one-third of their eligible Proposal Pool and chamber-vote opportunities, rounded up. • A vote only becomes a participation requirement after the stage has been open for 24 hours. If it closes earlier, missing it does not count against the Governor. • Authors, Formation team members, and others excluded from specific votes no longer have those impossible votes added to their required activity. • And when a milestone or reconsideration opens a new chamber vote, it counts as a separate opportunity with its own eligible voters. Plus, Formation teams also get a clearer application, acceptance, and membership process. Read the full update: https://blog.humanode.io/vortex-dev-log-21-a-fair-chance-to-govern/

2026 is nearing it's end.... and that means HumanodeCon V is on! The 5th assembly of believers in egalitarian decentralization of crypto. Human nodes, friends and partners from the ecosystem. This year we decided to ask you about the format! Check out the poll below.