# Why redefined? ### Our Core Thesis 1. Web3 will be a seamless multi-chain experience. 2. Convenience and simplicity are essential for mass adoption. 3. Abstraction and orchestration are necessary to overcome the current fragmentation in Web3. ### Our Mission redefined’s mission is to make Web3 accessible, simple, and convenient for everyone, everywhere. The redefined: Connect protocol is fundamental to building the redefined: Smart Profiles and Developer tools to simplify cross-chain interactions and standardize verifiable credentials in the Web3 ecosystem. ### The Problem The identity in Web3 is broken. The lack of standardization and interoperability between different blockchain networks limits the potential for user interaction. Various blockchain networks may use other naming conventions, making it difficult for users to use the same ID, domain, and name across multiple networks. This can lead to confusion and limit users' ability to switch between different blockchain networks easily. There are many other options for Domains (e.g., Unstoppable Domains, ENS, ICNS), each blockchain has its segregated name service (.eth, .bnb, .sol, etc.), and wallet addresses are not human-readable. Furthermore, users often must verify which provider is integrated with each application, leading to significant confusion. For instance, both .bitcoin and .btc domains add to the complexity. The Web3 ecosystem lacks a unique standardized profile that works across all blockchains and simplifies user interactions. ### Web3 Middleware and Access Layer redefined is revolutionizing the Web3 user experience with our innovative Middleware and Access Layer. We aggregate and abstract all essential elements like Name Services, Domains, Identities, and Credentials from multiple Layer 1 and Layer 2 solutions into a single, unified API & SDK. This technology simplifies cross-chain interactions between users, wallets, dApps, and DAOs, delivering a superior user experience through a Widget and User Smart Profiles. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://redefined.gitbook.io/connect/introduction/overview/why-redefined.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.