11 docs tagged with "Core Contract"

The `transferAccountToChain` contract needs special consideration.

There currently are 6 core smart contracts that are always deployed on each chain, root, _default, accounts, blob, blocklog, and governance.

There currently are 6 core smart contracts that are always deployed on each chain, root, _default, accounts, blob, blocklog, and governance.

With call and callView you can interact with any core contract

The `accounts` contract keeps the ledger of on-chain accounts.

The `blobs` contract maintains a registry of _blobs_ (a collection of arbitrary binary data) referenced from smart contracts via their hashes.

The `blocklog` contract keeps track of the blocks of requests processed by the chain.

The errors contract keeps a map of error codes to error message templates. These error codes are used in request receipts.

The evm core contract provides the necessary infrastructure to accept Ethereum transactions and execute EVM code.

The `governance` contract defines the set of identities that constitute the state controller, access nodes, who is the chain owner, and the fees for request execution.

The root contract is the first smart contract deployed on the chain. It functions as a smart contract factory for the chain.