Skip to main content

46 docs tagged with "eosnetworkfoundation/docs"

View All Tags

Accounts and Permissions

An account identifies a participant in the EOS blockchain. A participant can be an individual or a group depending on the assigned permissions within the account. Accounts also represent the smart contract actors that push and receive actions to and from other accounts in the blockchain. Actions are always contained within transactions. A transaction can be one or more atomic actions.

BIOS Boot Sequence Tutorial

In this tutorial, you will learn how to boostrap a new EOS blockchain and get familiar with the steps involved in its deployment. You will start your boot node, load the system contracts, and then add multiple block producers to extend your single node blockchain into a multi node network. Finally, you will perform some node operator tasks on your new blockchain.


Learn about the compatibility of the EOS EVM with Ethereum:

Consensus Protocol

The EOS blockchain is a highly efficient, deterministic, distributed state machine that can operate in a decentralized fashion. The blockchain keeps track of transactions within a sequence of interchanged blocks. Each block cryptographically commits to the previous blocks along the same chain. It is therefore intractable to modify a transaction recorded on a given block without breaking the cryptographic checks of successive blocks. This simple fact makes blockchain transactions immutable and secure.

Create Development Wallet

Wallets are repositories of public-private key pairs. Private keys are needed to sign operations performed on the blockchain. Wallets are accessed using cleos.

Deploy Local Testnet With EVM Support

This document describes how to set up a local Antelope test environment with EVM support. This setup allows developers to speed up their smart contracts development without worrying about any resource, network, version, or other stability issues that public testnets might introduce. Developers are free to modify, debug, or reset the environment to facilitate their own applications development.

Install the CDT

The EOS Contract Development Toolkit, CDT for short, is a collection of tools related to smart contract compilation. Subsequent tutorials use the CDT primarily for compiling contracts and generating ABIs.

JSON RPC Compatibility

As we described in previous sections, the requests will be forwarded to the Geth Node in our system or a Wrapper service the repacking the transaction into an EOS smart contract call.

Network Peer Protocol

Nodes on the EOS blockchain must be able to communicate with each other for relaying transactions, pushing blocks, and syncing state between peers. The peer-to-peer (p2p) protocol, part of the nodeos service that runs on every node, serves this purpose. The ability to sync state is crucial for each block to eventually reach finality within the global state of the blockchain and allow each node to advance the last irreversible block (LIB). In this regard, the fundamental goal of the p2p protocol is to sync blocks and propagate transactions between nodes to reach consensus and advance the blockchain state.


The EOS blockchain works with three system resources: CPU, NET and RAM. The EOS accounts need sufficient system resources to interact with the smart contracts deployed on the blockchain.

Tic-tac-toe Game Contract

This tic-tac-toe tutorial guides you step by step to build a tic-tac-toe game which runs on the EOS blockchain. You will create a smart contract containing the game logic, then compile and deploy this smart contract to the EOS blockchain. In this tutorial we use a local single node testnet and show you how to play the game by calling the smart contract. For another example of using the single node testnet see the Getting Started for Node Operators section.

Transactions Protocol

Actions define atomic behaviors within a smart contract. At a higher level, transactions define groups of actions that execute atomically within a decentralized application. Analogously to a database transaction, the group of actions that form a blockchain transaction must all succeed, one by one, in a predefined order, or else the transaction will fail. To maintain transaction atomicity and integrity in case of a failed transaction, the blockchain state is restored to a state consistent with the state prior to processing the transaction. This guarantees that no side effects arise from any actions executed prior to the point of failure.


1. BIOS Boot Sequence: Demonstrates how to bootstrap a new EOS blockchain.


Learn about Smart Contract Development on EOS by doing the following tutorials:

V1 History Alternatives

The latest EOS v3.1 release officially ends support for the legacy V1 History plugin. Therefore, block producers and node operators who have integrations that rely on V1 History must seek alternative solutions.


The EOS Documentation Portal hosts a rich array of technical product documentation resources created and curated for the EOS blockchain developers community. These resources empower developers from all technology backgrounds to build enterprise-grade, secure, and scalable blockchain applications using the open-source EOS software.