Algorand builds technology that accelerates the convergence between decentralized and traditional finance by enabling the simple creation of next-generation financial products, protocols, and exchange of value.


Algorand Structure

  • Algorand has two main types of nodes (Relay or Participant) you can run also a 4 networks you can run your node against. Combining the types you can get:
    • Defualt: This is a Non-relay and Non-participant It can run on (Devnet, Testnet, Betanet, Mainnet)
    • Relay: Relay node Can't be participant. It can run only on (Testnet, Mainnet)
    • Participant: Can run on any of the four nets.
    • Indexer: It is a default node but with Archival Mode enbled which will make you able to query the data of the blockchain.

Run Default Node

The basic type. you select any network you want. and for the node type select Default. defaultdep

after the deployment is done. ssh to the node and run goal node status defaulttest here you see your node run against mainnet.

Run Relay Node

Relay nodes are where other nodes connect. Therefore, a relay node must be able to support a large number of connections and handle the processing load associated with all the data flowing to and from these connections. Thus, relay nodes require significantly more power than non-relay nodes. Relay nodes are always configured in archival mode.

The relay node must be publicaly accessable. so it must have public ip. relaydep

after the deployment is done. ssh to the node and run goal node status to see the status of the node. and also you can check if the right port is listening (:4161 for testnet, and :4160 for mainnet) relaytest

The next step accourding to the docs is to register your ip:port on Algorand Public SRV.

Run Participant Node

Participation means participation in the Algorand consensus protocol. An account that participates in the Algorand consensus protocol is eligible and available to be selected to propose and vote on new blocks in the Algorand blockchain. Participation node is responsible for hosting participation keys for one or more online accounts.

What you need?

  • Account mnemonics on the network you deploy on (offline) you can check the status for you account on the AlgoExplorer. search by your account id.

    The account needs to have some microAlgo to sign the participation transaction.

  • First Round: is the first block you need your participaiton node to validate from. you can choose the last block form the explorer. partexp

  • Last Round: is the final block your node can validate. let's make it 30M


after the deployment is done. ssh to the node and run goal node status to see the status of the node. you see it do catchup. and the fast catchup is to make the node sync with the latest block faster by only fetch the last 1k blocks. after it done it will start create the participation keys. partstatus

now if you check the explorer you can see the status of the account turned to Online partonl

Run Indexer Node

The primary purpose of this Indexer is to provide a REST API interface of API calls to support searching the Algorand Blockchain. The Indexer REST APIs retrieve the blockchain data from a PostgreSQL compatible database that must be populated. This database is populated using the same indexer instance or a separate instance of the indexer which must connect to the algod process of a running Algorand node to read block data. This node must also be an Archival node to make searching the entire blockchain possible.


After it finish you can access the indexer API at port 8980 and here are the endpoint you can access.

Select Capacity

The default scinario the capacity is computed based on the node (network/type) accourding to this reference. But you still can change this only to higher values by selecting the option Set Custom Capacity