A program and its state deployed at a blockchain address, which runs its defined functions when transactions call it.
Supports: Defines smart contracts as blockchain programs and state, explains interactions, irreversibility, composability, and the oracle limitation.
Supports: Documents that smart-contract security depends on design and implementation rather than automated execution alone.
A smart contract is onchain code and state, not automatically a legal agreement
It can only enforce its implemented logic and permissions on the relevant network
Oracles, upgrades, administrators, and transaction ordering can materially change an outcome
Verify address, code, permissions, approvals, and dependencies before relying on it
A lending protocol has an onchain liquidation function. Before depositing collateral, a user checks its deployed address, the oracle feeding prices, the liquidation parameters, upgrade authority, and whether a pause role can alter access. The word smart contract does not make those risks disappear.
An application that combines a user interface with smart contracts or other decentralized-network components. Its interface, data services, wallet connection, and operations may still have centralized dependencies.
An Ethereum token-interface standard for fungible token contracts. It specifies common methods and events, but it does not certify a token, its issuer, its economics, or its safety.
Ethereum's execution environment: a deterministic virtual machine that executes smart-contract bytecode as part of Ethereum state transitions. EVM compatibility does not make contracts, addresses, assets, or deployments interchangeable across networks.
A system that delivers external data or computation results to a smart contract. The contract can only act on the oracle interface and the protocol rules chosen for it; an oracle value is not a universal guarantee of truth, freshness, or safety.
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles