Algorand

Algorand is a permissionless, pure proof-of-stake blockchain that delivers decentralization, scalability, security, and transaction finality. Visit our developer website for the most up-to-date information about using and installing the Algorand platform. We currently strive to support Debian-based distributions, with Ubuntu 24.04 as our official release target. Building on Arch Linux also works well. Our core engineering team uses Linux and OSX, so both environments are well-supported for development. OSX Only : Homebrew (brew) must be installed before continuing. Here are the installation requirements. At this point, you are ready to build go-algorand. We use make and have several targets to automate common tasks. to see activity. Refer to the developer website for instructions on using different tools. You can run a node out of other directories than ~/.algorand and join networks other than mainnet. Just make a new directory and copy the genesis.json file for the network into it. For example: Genesis files for mainnet, testnet, and betanet can be found in installer/genesis/ . Provides core functionality to the algod and kmd daemons, as well as other tools and commands: crypto : Contains the cryptographic constructions used for hashing, signatures, and VRFs. It also includes Algorand-specific details about spending keys, protocol keys, one-time-use signing keys, and how they relate to each other. config : Holds configuration parameters, including those used locally by the node and those that must be agreed upon by the protocol. data : Defines various types used throughout the codebase. basics : Holds basic types such as MicroAlgos, account data, and addresses. account : Defines accounts, including "root" accounts (which can spend money) and "participation" accounts (which can participate in the agreement protocol). transactions : Defines transactions that accounts can issue against the Algorand state, including standard payments and participation key registration transactions. bookkeeping : Defines blocks, which are batches of transactions atomically committed to Algorand. pools : Implements the transaction pool, holding transactions seen by a node in memory before they are proposed in a block. committee : Implements the credentials that authenticate a participating account's membership in the agreement protocol. ledger (README): Contains the Algorand Ledger state machine, which holds the sequence of blocks. The Ledger executes the state transitions resulting from applying these blocks. It answers queries on blocks (e.g., what transactions were in the last committed block?) and on accounts (e.g., what is my balance?). protocol : Declares constants used to identify protocol versions, tags for routing network messages, and prefixes for domain separation of cryptographic inputs. It also implements the canonical encoder. network : Contains the code for participating in a mesh network based on WebSockets. It maintains connections to some number of peers, (optionally) accepts connections from peers, sends point-to-point and broadcast messages, and receives messages, routing them to various handler code (e.g., agreement/gossip/network.go registers three handlers). rpcs : Contains the HTTP RPCs used by algod processes to query one another. agreement (README): Contains the agreement service, which implements Algorand's Byzantine Agreement protocol. This protocol allows participating accounts to quickly confirm blocks in a fork-safe manner, provided that sufficient account stake is correctly executing the protocol. node : Integrates the components above and handles initialization and shutdown. It provides queries into these components. Contains the two daemons that provide Algorand clients with services: daemon/algod : Holds the algod daemon, which implements a participating node. algod allows a node to participate in the agreement protocol, submit and confirm transactions, and view the state of the Algorand Ledger. daemon/al