An account identifies a participant in an Antelope 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.
Introduction
Overview
Core
Step 1: Install Leap binaries
Overview
Overview
An Antelope 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.
Accounts, Wallets and Permissions
Wallets are repositories of public-private key pairs. Private keys are needed to sign operations performed on the blockchain. Wallets are accessed using cleos.
What is an account?
Introduction
To learn about data persistence, you write a simple smart contract that functions as an address book. While this use case is not very practical as a production smart contract, it is a good contract to start with to learn how data persistence works on Antelope without being distracted by business logic that does not pertain to the multi_index functionality.
Step 1: Obtain Contract Source
Learn about Antelope's Development Environment:
The Antelope framework is made up of the following components and toolchain:
We appreciate your interest in contributing to the Antelope framework! We always welcome contributions from our community to make our code and docs better.
- Installing eosio.cdt
ABI
Create the Contract
Previously, we sent an inline action to an action that was defined in the contract. In this part of the tutorial, we'll explore sending actions to an external contract. Since we've already gone over quite a bit of contract authoring, we'll keep this contract extremely simple. We'll author a contract that counts actions written by the contract. This contract has very little real-world use, but will demonstrate inline action calls to an external contract
The Antelope 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.
Learn about Antelope's History Alternative:
Nodes on an active Antelope 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.
Learn about Antelope's available tools, the core concepts and underlying technical features:
Goal
Antelope versions
- Community
Antelope has the ability to sort tables by up to 16 indices. In the following section, we're going to add another index to the addressbook contract, so we can iterate through the records in a different way.
Learn Smart Contract Developemnt on Antelope:
Step 1: Boot Node and Wallet
WebAssembly C++ Compilation
This tic-tac-toe tutorial guides you step by step to build a tic-tac-toe game which runs on an Antelope blockchain. You will create a smart contract containing the game logic, then compile and deploy this smart contract to an Antelope 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 in using the single node testnet see the Getting Started section.
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.
If you do not want to install Antelope binaries or have other types of installation restrictions, you can try Antelope in DUNE (Docker Utilities for Node Execution). This approach, powered by Docker, provides developers with a personal container for Antelope blockchain management, smart contract development, and testing purposes.
1. BIOS Boot Sequence: Demonstrates how to bootstrap a new Antelope blockchain
Introduction
The latest Antelope 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.
What is Antelope