I once spent an entire afternoon yelling at a scanner because it refused to accept that I was, in fact, the person standing in front of it. I needed to verify my identity for a freelance contract, and the platform wanted a notarized copy of my passport, uploaded as a PDF, but not too large, and not too small, and definitely not the one I had just scanned three times. By the time I gave up, I had printed sixteen pages, signed four forms, and still had no idea if the client on the other end would ever actually see my work.
That experience stuck with me. Not because it was unusual—we have all been there—but because it felt so deeply broken. I had the passport. I had the contract. I had every right to be there. Yet proving that simple truth had turned into a bureaucratic obstacle course that took hours and solved nothing.
Weeks later, a friend mentioned a project called Sign. He said it was trying to solve exactly the problem I had been shouting about. I was skeptical. I had heard plenty of companies promise to fix identity verification, and most of them just wanted to store my data in another database where it could eventually get stolen. But he handed me his phone and showed me something different.
He had a digital credential on his device—a verified proof that he held a professional license. What surprised me was not the credential itself but how he got it. He did not upload documents to a company server. He did not wait for approval. The licensing authority had issued it directly to him, and it sat on his phone, encrypted, under his control. When he needed to prove his license to a client, he shared it instantly, and the client could verify it without ever calling the licensing board.
I asked him to show me how it worked, and he pulled up the developer documentation. That was the moment I started to understand. Sign provides the infrastructure that lets any organization issue these credentials and any application verify them. The technology is built around public key cryptography—a concept I had heard of but never really grasped. The simple version is this: the issuing authority signs the credential with a private key, and anyone with the corresponding public key can confirm it is authentic. The credential itself contains all the proof anyone needs. There is no phone call. No round trip. No waiting.
What struck me was how obvious this seemed once I understood it. We have been verifying credentials the same way for centuries: call the source, ask if it is true, wait for an answer. That model made sense when communication was slow and data lived on paper. It makes no sense now. We have the technology to build something better. It just never got built.
Sign is building it. The project already handles millions of credentials and has deployed identity systems for governments. It manages token distributions at a scale that would have required armies of compliance officers just a few years ago. But the part that stuck with me was not the scale. It was the feeling of holding a credential on my own device and realizing that for the first time, I was not asking permission to prove who I was. I just did it.
That is the shift. We have spent decades building systems that assume people cannot be trusted with their own information. The result is a world where proving a simple fact takes an afternoon, a scanner, and a notary. The alternative is not complicated. It is just a different way of thinking: let the authorities issue the credentials, let the people hold them, and let anyone verify them instantly. No middlemen. No waiting. No yelling at scanners.
I still think about that afternoon sometimes. The frustration has faded, but the lesson has not. The problem was never that I could not prove who I was. The problem was that the systems we built made it impossible to do so without permission. That permission is no longer required.
#SignDigitalSovereignInfra #TrumpConsidersEndingIranConflict #Trump's48HourUltimatumNearsEnd