Skip to main content

Introduction to INTU Architecture

With INTU, Flexibility is power. Our architecture is highly customizable to enable projects to connect on-chain without compromising on their user experience or their product.

In this section, we will introduce the various components of the INTU system, and elaborate on the powerful flexibility and customization available to developers for different applications. This includes Account Participants, Communication Channels, Data Storage, Coordination, and Target On-chain Application.

Account participants or factors control the unique dynamic keyshares created by the decentralized account generation process. These include end-users factors, such as web3 wallets or social log-in services, as well as non-user factors such as Co-signers or hosted services running the INTU SDK.

In order to form valid signatures for on-chain interactions, these factors must coordinate and communicate with each other. By default, the SDK will use INTU’s smart contract system to provide a resilient, permissionless, and decentralized channel for factors.

All communication and data stored on-chain is secured using INTU’s novel encryption protocol, which requires no additional keys or passwords stored on local devices.

The smart contract system also facilitates account recovery, and safely serves as a ultimate source of truth for using and managing INTU accounts.

Alternative channels of communication and storage can also be defined by the application for a variety of use cases or requirements.. Some examples include:

  • Private channels of communication for Enterprise security

  • Private or Permissioned blockchains

  • P2P communications protocols, inluding decentralized databases or LibP2P

  • Private, on-prem, or self-managed cloud-based storage

The end result is always the same: A static public address for an EVM-compatible Externally-Owned Account, and Signatures for EVM-verification.