@SignOfficial #sign #SignDigitalSovereignInfra $SIGN A lot of digital identity systems sound impressive when they are introduced. The language is always polished. Privacy. Interoperability. Trust. Inclusion. User control. It all reads well. But once you move beyond the framework and start asking whether developers are building real products on top of that infrastructure, the story usually becomes much thinner. That is why Bhutan stands out. SIGN points to 13+ teams building applications integrated with the country’s NDI system, and on the surface that sounds like exactly the kind of signal you want to see. It suggests the platform is no longer just a government project sitting on its own. It suggests something real has started forming around it.
And that matters.
Because when outside teams are willing to build on top of identity infrastructure, it usually means the system has moved beyond theory. It means there is enough confidence, enough utility, and enough momentum for people to put serious time and effort into it. That is never a small thing. A platform with real builders around it always feels more alive than one that survives only through official demos and polished documents.
But the more I sat with that 13+ teams number, the less it felt like a clean flex.
It started to feel like the most revealing part of the entire story.
Bhutan’s NDI has not grown on top of one stable technical base from day one. It started on Hyperledger Indy, then moved to Polygon, and now it is shifting again toward Ethereum. On paper, those changes can be explained very neatly. Technology evolves. Governments make new decisions. Better infrastructure becomes available. Long-term interoperability matters. Security matters. Flexibility matters. All of that may be true.
But from the perspective of the developers building on top of the system, none of those changes are abstract.
They are work.
They are the kind of work that rarely shows up in a polished success story. If you are one of the teams building an app that depends on this infrastructure, every migration underneath you means more than a strategic platform decision. It means checking what changed, updating integrations, retesting flows, fixing assumptions that no longer hold, adjusting timelines, and trying to keep users from feeling the instability under the surface. The more real the application is, the heavier that burden becomes.
That is why I cannot look at those 13+ teams and see only maturity.
I also see a group of builders who may have had to quietly absorb a lot of change.
And that is where the whitepaper starts to feel selective.
It presents the ecosystem as proof that Bhutan’s model is working, which is fair. A national identity system with third-party developers is always a stronger signal than one where everything is still tightly controlled from the center. But it stops just before the obvious follow-up question. If this ecosystem really exists at that scale, what has it had to carry while the platform kept changing underneath it?
That is the part I wish was explored more honestly.
The whitepaper mentions hackathons and developer engagement, and those are good things. They bring people in. They create momentum. They help turn infrastructure into actual use cases. Bhutan’s hackathon activity clearly shows that developers are not just passively watching the system. They are building around it. That is meaningful.
But hackathons are not the same thing as long-term ecosystem support.
A team can build something exciting during a hackathon. Keeping that same product alive through multiple platform transitions is a completely different challenge. That requires another kind of support entirely. It needs migration guidance, stable tooling, updated documentation, testing environments, clear timelines, and some confidence that the platform beneath the application will not keep shifting faster than the team can adapt.
That is the gap I keep noticing.
The public story is strong on innovation. Strong on momentum. Strong on vision. But it feels much weaker on what platform evolution has actually cost the people building on top of it.
And I think that matters, because those costs are often where the real story lives.
It is easy to say a national SSI system works when you are talking about credentials, standards, enrollment numbers, and partnerships. It is much harder to define what “working” really means once developers, institutions, and users are depending on it in production. At that point, success is not just about launching new features or making smart architecture choices. It is about whether the ecosystem around the platform can keep functioning without constantly paying for those choices in silence.
That is why Bhutan’s 13+ teams feel so important to me.
They are not just proof that the system has traction. They are also proof that there are real builders standing in the path of every platform decision. If Bhutan’s NDI ecosystem is still active, still building, and still expanding despite multiple infrastructure shifts, then that says something powerful about the system. It suggests there is real strength here. Real institutional commitment. Real staying power.
But it also suggests the polished version of the story may be leaving something out.
Because ecosystems do not move through repeated transitions for free. Someone always carries that cost. Usually quietly. Usually in engineering hours, delayed rollouts, extra testing, awkward coordination, and all the invisible maintenance work that never makes it into the headline.
That is why I do not see Bhutan’s developer ecosystem as just a maturity signal.
I see it as the most honest test of the whole model.
If those teams are thriving, then Bhutan has done something genuinely impressive. It has built identity infrastructure that people trust enough to build services, products, and public tools around, even while the system itself keeps evolving. But if those teams have been surviving by repeatedly absorbing migration pain that no one talks about, then that deserves attention too. Because that is also part of what maturity looks like. Not the polished version. The real one.
And maybe that is what makes Bhutan’s story more interesting than most.
It is not a simple case of success or failure. It is a country trying to build serious national identity infrastructure in public, with all the ambition, friction, and trade-offs that come with that. The 13+ teams are not just there to make the narrative look stronger. They are probably the clearest window into whether this system is becoming durable public infrastructure or just another evolving platform that keeps asking its builders to adapt faster than the story admits.
That is the part I keep coming back to.
Because once developers are involved, the platform is no longer judged only by what it promises.
It is judged by what it asks other people to carry.