I've spent 7 days talking about revenue, offices, and investors.
But the question I kept getting was: "How does it actually work?"
I'm not a developer. But I've spent the last few days trying to understand Sign's architecture. Here's what I found.
LAYER 1: SIGN PROTOCOL
What it is: Verifiable digital records. Think of it like a notary for the internet.
How it works: Sign Protocol lets you create, manage, and verify digital records on-chain. Anything from credentials to contracts to identity claims.
Why it matters: For governments, this means they can issue digital IDs or verify documents without centralizing everything. The data lives on-chain. The verification is public. But the sensitive parts stay private.
What I didn't understand at first: This isn't a blockchain. It's a protocol that runs on blockchains. Multi-chain. Flexible. Designed for governments who don't want to lock themselves into one chain.
LAYER 2: TOKENTABLE
What it is: Distribution infrastructure. They help projects distribute tokens to users.
How it works: TokenTable handles the complex part of token distribution — airdrops, vesting, claims. They've already distributed over $4B across 40M+ wallets.
Why it matters: Projects like Starknet, ZetaChain, and Notcoin used TokenTable. That's real volume. Real users. Real infrastructure.
What I didn't understand at first: TokenTable isn't just a tool. It's revenue. Every distribution has fees. That's part of the $15M annual revenue.
LAYER 3: SIGNPASS
What it is: Digital identity infrastructure. Built for governments and enterprises.
How it works: SignPass lets governments issue digital IDs to citizens. The IDs are verifiable on-chain. But citizen data stays private. Only the government can access sensitive info.
Why it matters: This is the layer Abu Dhabi cares about. Digital identity is the foundation for everything — welfare payments, voting, property records, banking.
What I didn't understand at first: The "sovereign" part isn't marketing. Governments need control. Sign gives them control while still using public blockchains for verification.
THE GLUE: ZK-PROOFS
This is the part that took me the longest to understand.
Zero-knowledge proofs let you prove something is true without revealing the information itself.
Example: You can prove you're a citizen without showing your passport. You can prove you're over 18 without showing your birth date.
For governments, this is huge. They get control over who has access. Users get privacy. Both win.
WHAT THIS MEANS FOR $SIGN
I'm not a token economist. But here's my simple take:
Protocol fees: Every time someone uses Sign Protocol, there's a fee
Distribution fees: TokenTable takes a cut of every distribution
Enterprise licenses: Governments pay for SignPass
More users = more fees = more revenue.
WHERE I'M STILL LEARNING
I'm not going to pretend I understand all the technical details.
ZK-proofs are complicated. The multi-chain architecture is complicated. How exactly all three layers interact? Still figuring that out.
But I understand enough to know why Abu Dhabi signed the partnership. And why Sequoia backed them.
OVER TO YOU
What technical questions do you have? What parts of Sign do you want me to dig deeper on?
Drop your questions below. I'll research and answer.
Sources:
Sign Protocol documentation
TokenTable distribution data
SignPass technical overview
CEO interviews on architecture