been sitting with the bhutan NDI migration history for a few days and i keep coming back to the same question — what does it actually cost to get the infrastructure layer wrong the first time?
bhutan launched its national digital identity system on hyperledger indy. then moved to polygon in 2024. now targeting ethereum with a Q1 2026 goal. three platforms in roughly two years on a live system holding identity records for 750,000 people.
the whitepaper calls it pragmatic iteration. and honestly that's not wrong — indy had real scalability limits, polygon offered better tooling, ethereum offers deeper decentralization. the reasoning at each step makes sense in isolation.
what it doesn't fully reckon with is what migration means at the identity layer specifically. you're not moving a content database. you're moving the cryptographic anchors that verifiers use to confirm a government-issued credential is real. every issuer DID needs re-anchoring. every integration built against the old trust registry needs rebuilding. every revocation list needs to stay continuously accessible through the move.
the W3C VC and DID standards commitment helps — theoretically the credentials in citizen wallets are portable. but theoretically portable and operationally confirmed are two different things. and when the system is live and 750,000 people depend on it, that gap matters.
this is the problem @SignOfficial is building against. not just launching sovereign identity infrastructure but building it on a foundation stable enough that governments don't end up in a three-platform migration cycle on a live national system.
the middle east is moving fast on digital economic infrastructure right now. the countries that get the foundation right the first time are going to have a significant advantage over the ones that launch fast and iterate through the pain later.
$SIGN is making a case for being that foundation. whether it holds up is the question worth tracking.