I just got asked to resubmit my proof of funds on a new platform last week, even though I’ve already sent the same info to three other platforms this month.
It’s the exact same dataset and process, but on this new system, it feels like starting from scratch
To me, this is exactly the problem $SIGN is addressing. They don’t treat attestation as a “verify once and done” task. Instead, they make verification data reusable. Schemas create a common standard, attestation records proof according to that standard, and schema hooks let you attach logic to the proof when it’s created or updated.
If this works as intended, verification becomes less repetitive and more like a portable asset that can move across platforms. This is where Sign could really change how Web3 manages trust.