> For the complete documentation index, see [llms.txt](https://frigghome.gitbook.io/frigghome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://frigghome.gitbook.io/frigghome/executive-summary.md). # Executive summary ## FriggHome's Vision #### 👁️ **One long-term goal :** Empower 1 Billion Users Bridging the digital and physical worlds by integrating blockchains directly at home. We keep the cypherpunk vision of decentralized control, financial freedom, and a rebellion against centralized systems, forging a future where blockchain enhances everyday life. Transform homes into decentralized hubs with FriggBox, hosting validators and nodes for passive income, securing quantum-safe wallets, and enabling true data ownership through BoT. #### 🏦 Redefine DeFi and Secure a Post-Quantum Future Streamline swaps, staking, and restaking with FriggLiquid’s smart routing, ensuring the best ratio and optimal yields. Scale FriggChain’s quantum-resistant blockchain and RINA’s censorship-resistant MESH network to power smart cities and BoT ecosystems. FriggHome is an ecosystem powered by DePIN designed to create a physically decentralized, scalable, and highly efficient foundation for the future of blockchain-powered applications, defying centralized control. ## An ecosystem powered by DePIN #### 💧 FriggLiquid : dApp Layer (2025) Frigg’s native dApps and integrations with external applications, driving real-world use cases. FriggLiquid, the 1st native dApp for one-click DeFi (swaps, LSTs and Restaking), it optimizes yields and manages BoT, driving smart living solutions. #### 📤 FriggBox : Hardware Layer (2026) A plug-and-earn smart device, hosting a MESH network, securing blockchains, and running BoT (blockchain of things) like FriggLock. It’s the physical backbone of **FriggHome**, enabling real-world applications through blockchain. It runs FriggChain nodes and EVM validators, generating DePIN rewards. #### ⛓️ FriggChain : Software Layer (2027) A quantum-resistant **blockchain** securing DeFi transactions and IoT/BoT interactions. Deployed on FriggBox in 2026, it uses quantum-safe consensus to protect the ecosystem, and integrations with existing PoS blockchain, such as ethereum. #### 🤖 BoT AGI (Artificial General Intelligence) : The brain behind FriggHome’s smart ecosystem. BoT AGI learns and adapts in real-time, optimizing everything from energy consumption and home automation to personal lifestyle recommendations. Secured by FriggChain and open-source, it ensures transparency and trust. ### At FriggHome, we’re not just building products... We're forging a decentralized, AI-driven ecosystem where every node earns rewards, every action optimizes life, and every device contributes to a post-quantum, user-centric network. FriggHome envisions a fully decentralized, user-governed internet, resistant to centralized control, aiming to empower 1 billion users in a free, post-quantum future. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://frigghome.gitbook.io/frigghome/executive-summary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.