We’ve spent the last few pieces unpacking PoBU step by step.
This one pulls the camera back and answers the biggest question of all:
Why is PoBU being proposed for consensus in the first place?
If you want the big picture in simple language, here it is: blog.humanode.io/why-pobu-is-...
And yet across the world, more and more people are living through the same feeling: the machinery is still running, but it no longer answers to them.
unpacked that failure, and what may come after it, here: blog.humanode.io/world-still-...
There is a funny ritual modern politics still performs with a straight face.
People vote. Governments win. Flags stay raised. Parliaments open. Courts issue rulings, and the news anchors keep calling it a democracy.
We hope everyone had a great weekend, and yes, it is time to say Happy Monday!
As team prepares the Vortex Simulator for launch this week, the Community Call focused on the Humanode Roadmap (roadmap.humanode.io), going over how to read it, and each pillar of the development that supports Humanode.
As the internet fills with agents that act, transact, and scale, 1 question starts to matter more: what still counts as human participation?
This article by Sasha Shilina looks at why that distinction matters, and why Humanode’s focus on unique human presence is essential for the agentic internet.
Humanode is now on Substack.
A place for deeper writing on identity, Sybil resistance, governance, and the future of the internet.
If you enjoy reading ideas explored properly, here: blog.humanode.io/humanode-on-...
In the last piece, we covered why PoBU is probabilistic.
Now comes the next natural question:
Even if the rule is clearly defined, what can still go wrong in a real system?
That's what the threat model in the paper describes. Read it here: blog.humanode.io/what-can-go-...
Another week, another Community Call. @everyone
The last Community Call was focused on testing and bug fixing the proto-Vortex.
If you have missed the fun, fret not we have got you covered. Read the recap here: x.com/humanode_io/...
So the question is simple: where do those bounds come from? Or how strict the rule is?
read it here: x.com/humanode_io/...
In the last piece, we covered the eligibility interface. It explains how the chain tracks who is allowed to take part over time.
Now comes a point that the PoBU makes directly. PoBU aims for “one eligible account per human,” but it treats that claim as probabilistic, with quantified bounds.
As much as scholars and blockchain developers enjoyed the Humanode PoBU white paper, it is easy to get lost in the concepts and data.
Thus, here is Proof of Biometric Uniqueness in simple terms, just in case you want to explain it to your children, or your parents: x.com/humanode_io/...
For those of you who were not able to join last Saturday's community call, here's a brief recap on what was discussed: x.com/humanode_io/...
Internal deployment is ready, and we’re on the finish line for the public release.
Full dev log: x.com/humanode_io/...
At the same time, the governing threshold model is now real and era-based, so “active governor” isn’t a vague label anymore, it’s derived from your actual voting opportunities and it kicks in deterministically from era E to E+1. And factions v1 is here too, as something that exists in the sim.
Vortex Dev Sim Log 6 is out, and yeah, this one is a major update.
We finally have Proposal Engine v1 in place, so proposal creation starts feeling predictable, with proper guardrails on the server side and a clean boundary between project proposals and system-executable changes.
Eligible for what? And how does the chain know?
Read it here: x.com/humanode_io/...
In the last piece, we looked at how PoBU approaches decentralization as something you can measure using public chain data: validator activity, churn, and block-author concentration.
That naturally raises the next question: what does PoBU treat as “eligibility” in the first place?
Humanode Biomapper C2 is now live on MegaETH mainnet.
This is for teams building on MegaETH who want “one human = one wallet” without turning their dApp into a KYC desk.
Congrats to the MegaETH team on mainnet day. Glad to be part of what ships on top of it.
Details: x.com/humanode_io/...
if you weren't able to join the 3rd Community call last Saturday, here's a recap on what we talked about: x.com/humanode_io/...
It also brings CM surfaces to life. You can now see contribution totals, breakdowns, and history across profiles, governance, and chambers. Plus a first pass on feeds, activity, and profiles that feels more grounded.
If you’ve been following along, the latest update is here: lnkd.in/dQrsmCTE
ortex Dev Log 5 is out. This one tightens the edges.
Failure paths are now explicit. Proposals that miss quorum or vote windows actually end. Feeds reflect why things failed. Lists stay honest about state.
Proof-of-Biometric-Uniqueness (PoBU) treats decentralization as a system property that can be measured. Not at the level of nodes or keys, but at the level of real humans.
How, you ask? Read here: x.com/humanode_io/...
Decentralization is often treated as an intuitive property: more nodes, more validators, more participants. In practice, however, most systems lack a precise way to measure:
Who is actually participating, and how independent are they?
This call is about hearing from the community. What you think the core principles of Vortex should be, what matters most, and what should guide how it evolves.
🗓️ Saturday, January 31st
🕐 1:00 PM UTC
📍Humanode Discord Radio: discord.gg/humanode-819...
After the community polls on day and time, we’re locking in the next Humanode community call.
It’s happening this Saturday, 31st January at 13:00 UTC, in the slot most people voted for.
The theme this time is Foundational Imperatives of Vortex.
If this sounds like something your dApp needs, you can explore it here:
Biomapper App: biomapper.hmnd.app
Biomapper Docs: link.humanode.io/docs/biomapper
Biomapper SDK: link.humanode.io/docs/biomapp...
Integration Guide: link.humanode.io/docs/biomapp...
Once you integrate it, the user flow is simple:
Biomap → Bridge to Polygon → Verify, all without sharing any personal data. No KYC, No PIII.
Once verified, that wallet can be treated as a unique human backed by your dApp.
For builders on Polygon, they can use it for:
• Sybil-resistant airdrops and rewards
• One-person-one-vote governance
• Fair mints and whitelists
• Any logic that needs uniqueness, without relying on KYC or trust-based systems.
