There is a saying that has circulated in government IT procurement for a long time: No one has ever been fired for choosing IBM. Selecting a big brand is always the safest, even if it costs twice as much and is twice as slow; if something goes wrong, there are people in front to take the hit.
@SignOfficial To enter this market, it's not about being cheaper or having more features.
When a government buys a CBDC system from IBM, what they receive is a closed black box. The system runs on IBM-authorized servers, the code is proprietary, and maintenance and upgrades rely entirely on IBM engineers. Theoretically, IBM can at any time say "We're not doing this anymore," or cut off services under political pressure. In peaceful times, this isn't a problem, but after Russia was kicked out of Swift, many Middle Eastern policymakers see not just news, but a future they might be facing.
Sign's solution has prioritized sovereignty from the very beginning.
The underlying protocol code is open, and any engineer can audit it. The government can deploy a complete version on its own servers. Sign, as the service provider, is responsible for initial deployment, technical support, and upgrade maintenance, but control always remains in the hands of the government.
This model is called "open source commercialization" in the traditional software industry, and Red Hat and HashiCorp have walked this path. The difference is that Sign's "enterprise clients" are sovereign nations, and the scale and strategic significance of the contracts far exceed those of ordinary enterprise software.
The case of Sierra Leone is quite typical. The MoU signed by both parties includes technical implementation, a joint investment framework, and profit sharing. This is not a simple transaction of "selling software for service fees"; it is closer to "joint venture factory"—Sign provides technology and operational capabilities, while the government offers policy access and user base, and both parties jointly operate this infrastructure. The government has no motivation to replace Sign because changing partners would mean renegotiation and rebuilding.
Middle Eastern countries have a common characteristic: they are not short of money, but lack reliable technological partners.
The sovereign wealth funds of Gulf countries are measured in trillions of dollars, and what limits digitalization is not the budget but the inability to find a supplier that has both technological capability and is politically acceptable and can truly deliver. Sign's competitiveness in this dimension comes from several overlapping factors—real operational distribution cases, a politically neutral geographical location, the blockchain's inherent auditability, and the influence of YZi Labs in the Middle Eastern crypto circle.
If this model can be successfully replicated in the Middle East, the commercial value will increase geometrically. Government contracts have long cycles, large amounts, and high renewal rates. Once a country's digital currency system operates on Sign's technology, the cost of replacement is extremely high, essentially meaning long-term stable income. This is consistent with the underlying logic of TokenTable's service for crypto projects—establishing deep binding to make migration costs a moat, except this time the moat is not filled with code but with national will.
However, the level of confidence depends on one thing: when will the next truly grounded government cooperation come? Currently, both Kyrgyzstan and Sierra Leone are still in the pilot and signing stages, and the distance between the MoU and the nationwide system going live may be longer than expected. Before that, no matter how appealing this model sounds, it can only be considered as an option value rather than a real valuation.