Avalanche is a network composed of multiple blockchains. Each blockchain is an instance of a Virtual Machine (VM), much like an object in an object-oriented language is an instance of a class. That is, the VM defines the behavior of the blockchain. Coreth (from core Ethereum) is the Virtual Machine (VM) that defines the Contract Chain (C-Chain). This chain implements the Ethereum Virtual Machine and supports Solidity smart contracts as well as most other Ethereum client functionality.
Coreth is a dependency of AvalancheGo which is used to implement the EVM based Virtual Machine for the Avalanche C-Chain. In order to run with a local version of Coreth, users must update their Coreth dependency within AvalancheGo to point to their local Coreth directory. If Coreth and AvalancheGo are at the standard location within your GOPATH, this will look like the following:
cd $GOPATH/src/github.com/ava-labs/avalanchego
go mod edit -replace github.com/VidarSolutions/coreth=../corethNow that AvalancheGo depends on the local version of Coreth, we can build with the normal build script:
./scripts/build.sh
./build/avalanchegoNote: the C-Chain originally ran in a separate process from the main AvalancheGo process and communicated with it over a local gRPC connection. When this was the case, AvalancheGo's build script would download Coreth, compile it, and place the binary into the avalanchego/build/plugins directory.
The C-Chain supports the following API namespaces:
ethpersonaltxpooldebug
Only the eth namespace is enabled by default.
To enable the other namespaces see the instructions for passing the C-Chain config to AvalancheGo here.
Full documentation for the C-Chain's API can be found here.
The C-Chain is compatible with almost all Ethereum tooling, including Remix, Metamask and Truffle.
As a network composed of multiple blockchains, Avalanche uses atomic transactions to move assets between chains. Coreth modifies the Ethereum block format by adding an ExtraData field, which contains the atomic transactions.
The C-Chain supports Avalanche Native Tokens, which are created on the X-Chain using precompiled contracts. These precompiled contracts nativeAssetCall and nativeAssetBalance support the same interface for ANTs as CALL and BALANCE do for vidar with the added parameter of assetID to specify the asset.
For the full documentation of precompiles for interacting with ANTs and using them in ARC-20s, see here.
Blocks are produced asynchronously in Snowman Consensus, so the timing assumptions that apply to Ethereum do not apply to Coreth. To support block production in an async environment, a block is permitted to have the same timestamp as its parent. Since there is no general assumption that a block will be produced every 10 seconds, smart contracts built on Avalanche should use the block timestamp instead of the block number for their timing assumptions.
A block with a timestamp more than 10 seconds in the future will not be considered valid. However, a block with a timestamp more than 10 seconds in the past will still be considered valid as long as its timestamp is greater than or equal to the timestamp of its parent block.
Snowman consensus does not use difficulty in any way, so the difficulty of every block is required to be set to 1. This means that the DIFFICULTY opcode should not be used as a source of randomness.
Additionally, with the change from the DIFFICULTY OpCode to the RANDOM OpCode (RANDOM replaces DIFFICULTY directly), there is no planned change to provide a stronger source of randomness. The RANDOM OpCode relies on the Eth2.0 Randomness Beacon, which has no direct parallel within the context of either Coreth or Snowman consensus. Therefore, instead of providing a weaker source of randomness that may be manipulated, the RANDOM OpCode will not be supported. Instead, it will continue the behavior of the DIFFICULTY OpCode of returning the block's difficulty, such that it will always return 1.
To support these changes, there have been a number of changes to the C-Chain block format compared to what exists on Ethereum.
Version: provides version of theExtDatain the block. Currently, this field is always 0.ExtData: extra data field within the block body to store atomic transaction bytes.
ExtDataHash: the hash of the bytes in theExtDataHashfieldBaseFee: Added by EIP-1559 to represent the base fee of the block (present in Ethereum as of EIP-1559)ExtDataGasUsed: amount of gas consumed by the atomic transactions in the blockBlockGasCost: surcharge for producing a block faster than the target rate