Skip to main content

15 docs tagged with "reference"

View All Tags

Compatible Tools

Existing EVM tooling is compatible and can be used directly with an IOTA Smart Contracts chain running EVM. You can configure hardhat, metamask, remix, Ether.js and Web3.js among others.

Contracts

Important EVM contracts in the IOTA ecosystem.

Core Contracts

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

Core Contracts

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

The blob Contract

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

The blocklog Contract

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

The errors Contract

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

The evm Contract

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

The governance Contract

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

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

WasmLib Data Types

The WasmLib provides direct support for the basic value data types that are found in all programming languages, and WasmLib versions of ISC-specific value data types.