Composable Identity and Credentials in Web3

Hey everyone,

It would be good to talk about composable identity and credentials in Web3, especially in the context of modular blockchain architectures. We often talk about composability in terms of smart contracts and liquidity, but identity is still treated as an afterthought in many systems.

With the rise of decentralized identity standards and verifiable credentials, it seems possible to design applications where users can carry portable attestations across ecosystems. For example, proof of governance participation, developer contributions, or liquidity provision could become reusable building blocks rather than siloed data points. The question is how to structure this in a way that preserves privacy while still enabling meaningful reputation.

There are also architectural decisions to consider. Should credentials live fully on-chain, be anchored on-chain but stored off-chain, or rely on dedicated identity layers? How do we handle revocation, updates, and cross-chain interoperability? In a modular stack where execution and settlement may be separated, identity could become its own specialized layer.

I’m curious whether people see identity as infrastructure that should be standardized early, or as something that will naturally emerge from application-level experimentation. Are there concrete implementations we can learn from when designing composable credential systems?