🧵 SIGN’s offline verification is powerful.
But there’s a tradeoff no one is naming.
The promise:
SIGN enables identity verification without internet.
QR codes. NFC.
Verify anywhere — borders, rural zones, outages.
That’s real infrastructure. That’s resilience.
But here’s the tension 👇
Offline verification ≠ real-time truth.
Revocation lives on-chain → requires connectivity.
Offline verification uses cached state.
And caches… go stale.
---
The gap: Revocation integrity
A credential can be:
❌ Revoked on-chain (1 hour ago)
✅ Still accepted offline
Why?
Because the verifier hasn’t synced.
Cryptography checks out.
Schema is valid.
Reality is outdated.
---
The failure mode to think about ⚠️
A visa gets revoked.
An ID gets flagged.
At a remote checkpoint:
No internet.
Cache = 12 hours old.
Result?
👉 Invalid credential gets accepted as valid.
---
This isn’t a bug. It’s a tradeoff.
You can have:
✔️ Offline resilience
✔️ Real-time revocation
But not both — at the same time.
The real issue: it’s not clearly stated.
SIGN is building for high-stakes identity at scale.
That demands clarity, not assumptions.
If the system chooses availability over immediacy…
👉 That choice should be explicit.
Infrastructure doesn’t fail at design.
It fails at unspoken assumptions.