$SIGN
teams are issuing attestations, using schemas, and plugging them into workflows. but the cross-project reuse piece still feels early. i haven’t seen strong evidence that schemas are becoming shared primitives yet — more like per-project definitions with similar shapes.
second piece is the verification model. SIGN supports both onchain and offchain verification paths, which sounds flexible, but also introduces some ambiguity. onchain verification is deterministic, expensive, but clean. offchain verification is cheaper and more expressive, but now you’re depending on external resolvers.
and that’s where things get a bit fuzzy. if a credential depends on an offchain resolver, then its trust model extends beyond the chain. two integrators could technically resolve the same attestation differently depending on implementation details or data freshness. not catastrophic, but enough to introduce edge cases. @SignOfficial
this part is partially live — you can already see hybrid verification flows in production. but standardizing how resolvers behave, or even what guarantees they provide, feels like an unsolved layer.
third is the distribution engine, which is probably the most mature piece today