System design
Last updated
Last updated
The core idOS network consists of two main components. The first is , a decentralized, storage-specific L1 blockchain which allows for compliant and secure storage of personal user information and relies on the idOS Operators coming to consensus over the current state of a distributed SQL database. The second is the an Arbitrum Orbit L2 blockchain, settling to Ethereum, which implements the idOS economy, including node provider selection, staking and slashing, gas fee payment, and payment for access grants.
In order to efficiently integrate idOS into existing applications, we are providing targeted SDKs that are targeted for each given use-case. In addition to a base SDK, the idOS provides both an Issuer and Consumer SDKs that enable a seamless integration for entities writing new data into the idOS or consuming existing data via access grants.
The idOS Enclave is an standardized interface that facilitates the encryption and decryption of user credentials. idOS provides a default web-based enclave that allows for the cryptographic integration via user-secret (e.g. passwords), passkeys or secure MPC protected network persistence and restoration. Furthermore, the Enclave can be implemented directly in 3rd party wallets that would like to support encryption and decryption natively.
The idOS Isle is a hosted iFrame component that enables an efficient default UI/UX integration of user-flows into existing web-based applications. It allows for an "one-line" integration to enable idOS user-flows within any 3rd-party application. However, if required, applications can always implement their own custom user journeys directly on top of our SDKs.
As the idOS Dashboard provides for granular information on the key application-level abstractions of users, profiles and access grants, we've prioritized it over a traditional block explorer. idOS Storage Network blocks will be made visually navigable in the future as we build a dedicated block explorer.
The idOS Dashboard enable specific in the ecosystem to directly visualize and interact with core idOS funtionalities. For example, users are able to add additional wallets across chains to their profile, issuers are able to inspect and revoke issued credentials while data consumers get an overview of their existing Access Grants to user data.
