Skip to content


Welcome to the documentation. This site will provide you with all the necessary information, resources, and tools to get started with the project.

What is is an open-source off-chain P2P (peer-to-peer) network. It offers decentralized volumes and blockchain indexing, function execution and VM provisioning, as well as a DID (decentralized identity) framework. also includes bridges to many major blockchain networks, such as Ethereum (or any EVM-compatible blockchain), Tezos and Solana, to enable smart contracts access to the resources and hosted on the network.

The project has the following components:

The network

The network

The network is composed of 2 sets of nodes:

  • CCNs, the backbone of the P2P network. They serve as an entry point into the network through an API (similar to a blockchain node's RPC).
  • CRNs, responsible for the actual compute and storage available on CRNs must be tied manually to a single CCN, and each CCN is incentivized to tie up to 3 CRNs.


In terminology, a "message" is similar to a "transaction" for a blockchain: it is a set of data sent by an end user, propagated through the entire peer-to-peer network. A message can be generated using either the python or typescript SDKs, or through the aleph-client or the web dashboard. These messages can contain several different instructions, such as reading or writing posts, programs/functions, or indexing data created on external blockchains.


While Aleph is not a blockchain. It uses the ALEPH token hosted on Ethereum to manage users' payments and offer network integrity and workload execution rewards to node operators. Because of this, you must have an EVM-compatible wallet (such as Metamask) provisioned with some ALEPH tokens to write to the network.


Let's take the example of a user who wants to run a program on the network:

  1. The user makes sure to have an Ethereum wallet with at least 2000 ALEPH tokens
  2. The user writes and sends a message using either the aleph python client, one of the SDKs, or the web dashboard
  3. The message arrives at a CCN, which then broadcasts that message to all CCNs in the network
  4. The "program" workload scheduled by the user's message gets assigned to one of the CCNs
  5. The assigned CCN now assigns that workload onto one of its CRNs
  6. The assigned CRN creates a micro-vm executing the user's requested workload.

Where to start?