12 docs tagged with "explanation"

Explore the how-to guides for IOTA Smart Contracts, offering step-by-step instructions on various topics and functionalities.

Each smart contract instance has a program with a collection of entry points and a state.

Smart contracts can be invoked through their entry points, from outside via a request, or from inside via a call.

IOTA Smart Contracts consensus is how Layer 2 validators agree to change the chain state in the same way.

As there is no way for the Wasm code to access any memory outside its own memory space, the WasmLib interface provides a number of proxies to make accessing data within the ISC sandbox as seamless as possible.

IOTA Smart Contracts chains keep a ledger of on-chain account balances. On-chain accounts are identified by an AgentID.

The current release of IOTA Smart Contracts also has experimental support for EVM/Solidity, providing limited compatibility with existing smart contracts and tooling from other EVM based chains like Ethereum.

Invoking smart contracts with on-ledger and off-ledger requests with Solo.

Smart Contracts can only interact with the world by using the Sandbox interface which provides limited and deterministic access to the state through a key/value storage abstraction.

Smart contracts are applications you can trust that run on a distributed network with multiple validators all executing and validating the same code.

The state of the chain consists of balances of native IOTA digital assets and a collection of key/value pairs which represents use case-specific data stored in the chain by its smart contracts outside the UTXO ledger.

Each chain is run by a network of validator nodes which run a consensus on the chain state update.