By enabling HTTPS calls, providing a secure method for storing keys (ongoing development with VetKeys), and utilizing the T-ECDSA protocol for signing multi-chain messages and transactions, canisters are pivotal in forming a network of trustless oracles that serve as the orchestration layer for the Dooor protocol. The smart contracts in the Aggregation Layer are mapped to the data peer tools' canisters, synchronizing AI data across chains.
The Dooor architecture introduces a novel infrastructure that unlocks unprecedented use cases for the ICP ecosystem. With a suite of real-world sub-applications, Dooor optimizes canister utilization, leveraging them as key components in a multi-tenant LLM management system.
Dooor's main goal is to build a fully decentralized, privacy-enabled infrastructure for AI development. With this core technology, Dooor is developing feature apps that will take advantage of this end-to-end stack, such as Wisdoms, Web3 Agents, and Dooor Tools.
Currently implemented using the Azle TypeScript framework, the canisters have their own database relationships for critical data points (which cannot be corrupted). These canisters interconnect user interactions with agents, context, and LLMs on the computing layer (Akash). A multiset of canisters stores redundant data to ensure corruption resistance, while a master canister, governed by the Dooor DAO, ensures decentralization throughout the workflow. This setup enables on-chain management of a community-deployed swarm of agents without intermediaries.
The Akash deployment process involves a centralized step for the deployer, requiring a certificate generated locally on the user’s computer to interact with containers. This step necessitates access to the certificate for providing the one-time SDL rules to the provider, creating a significant point of failure where a user could potentially access Dooor's provider configurations.
With ICP canister management, we can generate this Akash certificate in-memory and send the one-time SDL configuration to the provider without storing the certificate data. This ensures a decentralized flow. Once configured, all communication between the canister and Akash can occur securely via T-ECDSA.
Dooor's mission is to serve as an aggregation protocol for AI agents. By connecting with various types of DePIN chains, the protocol achieves redundancy in its infrastructure resources, leveraging the unique capabilities of each chain and ensuring competitive pricing for end users. ICP, as the orchestration layer, eliminates sole dependence on Akash resources, enabling robust multi-chain support.
The system operates through a bidirectional workflow:
EVM sc handle user transactions and manage token pools. Mapping and Queues allow users to create orders (upload, patch, or delete models, tools, and contexts). ICP Canisters perform continuous HTTPS calls using a set of Base RPCs (acting as oracles) to gather transaction data, process it with business logic, and interact with the Akash-ICP SDK for provider management on the Akash layer.
Users or tenants define deployment parameters (data centers, requirements, and pricing) in a manifest file (deploy.yaml). This file, written in the declarative Stack Definition Language (SDL), simplifies the declaration of deployment attributes.
The system is designed with idempotence in mind, ensuring that even in extreme scenarios, redundant calls can guarantee transaction execution without failure.