The Asimov architecture is made up of into 6 modular components, which group loosely into 3 segments:
Unified Storage
a. Files
b. Database
Digital Scarcity
a. Identity
b. Assets
Portable Compute
a. Private & Trusted
b. Public & Trustless
+--------------------------------------------------------------------------------------------------------+| +---------------+ |+-----+ | Unified Storage | Files (IPFS) | || | | =============== +---------------+ || | -----> | +------------+ +------------+ || | | +--------------------+ | | | | || | | | Database (OrbitDB) | | | | | || | | +--------------------+ | | | | ||Route| +-------------------------------------------------------------------+ +-----+ +----+|(DNS)| | | | || | +-------------------------------------------------------------------+ +-----+ +----+| | | +----------------------------------+ | | | | || | | Digital Scarcity |Identity (Public Key Cryptography)| | | | | || | | ================ +----------------------------------+ | | | | || | <----> | | Encryption | | FaaS | || | | +----------------------------------+ | | | | |+-----+ | |Assets (primarily ERCs 20 and 721)| | | | | || +----------------------------------+ | | | | |+-------------------------------------------------------------------+ +-----+ +----+| | | |+-------------------------------------------------------------------+ +-----+ +----+| +-------------------------------+ | | | | || Portable Compute | Private / Trusted (Wasm & JS) | | | | | || ================ +-------------------------------+ | | | | || +------------+ +------------+ || +------------------------------------+ || | Public / Trustless (Ethereum & L2) | || +------------------------------------+ |+--------------------------------------------------------------------------------------------------------+
Cutting across these are two second-order modules that rely on the 3 core areas:
Encryption
Functions-as-a-Service
The vast majority of end users will not have cryptographically-backed routing available locally for some time. To bridge this gap, Asimov leverages public DNS infrastructure as a backwards-compatibility bridge.