The problem Identitiy Bridge solves

Most Web3 projects still treat identity as a fragmented, app-specific problem, forcing users to re-verify on every platform while dApps either over-collect sensitive data or skip identity and compliance entirely. This leads to three core issues: users lose control of their data, identities cannot move cleanly across chains, and builders waste time rebuilding brittle, one-off identity checks instead of focusing on product.

IDBR solves this by providing a reusable, privacy-preserving identity layer that lets users hold their own credentials and selectively prove attributes, while dApps on any chain can verify those proofs without ever touching raw PII. It turns identity from a siloed, per-app headache into shared infrastructure: one verification, portable credentials, and simple integration hooks that any hackathon project can drop in to get secure, user-centric identity from day one.

Challenges I ran into

Honestly, the biggest issue was poor UX with proof aggregation via zkVerify. We've sidestepped it by allowing a per-proof verification for the POC.