# Introduction Welcome to RE:DREAMER, the gateway to hybrid commerce. We are here to challenge the status quo and set a new standard for the future of commerce. Our revolutionary protocol aims to bridge on-chain records with off-chain real-life assets and experiences, bringing a new level of security and efficiency to the future of commerce. The core of our approach is our evolving protocols, which enable users to interact with digital records and utilize their assets smoothly. Our Blockchain-as-a-Service (BaaS) bridges the gap between chains and existing systems, logistics, manufacturing, and more, allowing businesses to benefit from emerging technologies while operating with proven procedures. We offer a range of services to support the implementation of the Redeem Protocol and the Redeem System. Our goal is to empower businesses by providing a new standard in security and efficiency for commerce. We believe that by coordinating on-chain records with off-chain real-life assets and experiences, we can revolutionize the way people do business. We welcome collaborations and partnerships to expand and enhance our services, and we are excited to see where this journey takes us. \ \&#xNAN;*Notes on 2023 Mar 8th:*\ \&#xNAN;*We are providing a separate location for Redeem Protocol DAO white paper, including details of tokenomics and DAO governance. (available soon)*\ \&#xNAN;*For previous version of our docs and DAO white paper, please see* [*https://docs-2022.redreamer.io/*](https://docs-2022.redreamer.io/) --- # 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://docs.redreamer.io/readme.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.