> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moca.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Interoperability Challenges Across Web2/Web3

> Web2 and Web3 identity interoperability challenges — fragmented onboarding, mismatched standards, repeat KYC, and the developer burden of bridging silos.

Identity today is a tale of two worlds—**Web2 and Web3**—but both share the same fundamental problem: **a lack of consistent standards**.

Users are forced into **fragmented onboarding journeys**, re-doing KYC at every bank, re-verifying themselves on each exchange, or recreating their loyalty profile from scratch on every platform. Social, gaming, financial, and utility apps each operate in silos, locking data and accounts away. The result? Poor UX and exhausted users.

### The Developer’s Dilemma

It isn’t just the users who suffer. Developers face their own maze:

* Web2 systems rarely follow a unified standard, each with **different schemas and APIs**.
* Web3 brings a different problem—**multiple blockchains, competing protocols, and fragmented standards**.

This means endless resources spent on building **custom adapters and bridges**, just to make apps compatible with the systems they need to interact with.

### Why does this matter ?

Without interoperability, both **users and developers lose**:

* Users lose control and convenience.
* Developers lose time, speed, and innovation.

That’s why we’re making **interoperability a first-class goal**—building modular components that adapt to diverse systems. Our aim is simple:\
👉 **Unify the user experience** so identity is portable, secure, and seamless.\
👉 **Simplify the developer experience** so teams build once and deploy everywhere.

Together, this sets the stage for a **true identity stack** that bridges Web2 and Web3.