A system that allows smart contracts to function as user accounts instead of relying only on externally owned accounts.

ABI stands for Application Binary Interface. It defines how to interact with smart contracts and is usually represented in JSON.

A server that submits transactions on behalf of users, enabling gasless or subsidized transactions.

The low-level machine code that smart contracts compile to before deployment.

A special function that runs once when a contract is deployed, used to initialize state variables.

A contract call is an interaction where one account or contract invokes a function on a smart contract.

The process of publishing smart contract bytecode to the blockchain, creating a permanent on-chain contract instance.

A low-level Solidity function that executes code from another contract while preserving the calling contract's context.

An Ethereum standard for creating both fungible and non-fungible tokens in a single smart contract.

A standard for upgradeable smart contracts using proxy patterns and transparent storage slots.

The standard for fungible tokens on Ethereum, defining how token contracts implement transfer and approval functions.

The Ethereum standard for creating and managing unique NFTs.

An advanced token standard improving on ERC-20 with operator concepts and better transfer hooks.

The Ethereum Virtual Machine (EVM) is the computation engine that executes smart contract bytecode on Ethereum and EVM-compatible chains.

A logging mechanism that records important contract actions on the blockchain for external monitoring.

An immutable record of significant actions that occur within a smart contract.

A special function that executes when no other function matches a contract call.

A 4-byte identifier that specifies which function in a smart contract to call.

A mathematical function that converts input data of any size into a fixed-size output called a hash, used for data integrity and security.

A blueprint that defines function signatures and behaviors a smart contract must implement.

Reusable smart contract code that other contracts can call to perform specific functions.

A reusable code segment that adds restrictions or requirements to function execution.

A service that provides external data to smart contracts, enabling them to interact with real-world information and data.

Smart contract feature allowing admin to pause functions to prevent exploitation.

Smart contract that delegates function calls to another contract, enabling upgradeable logic.

Smart contract instruction that cancels transaction and reverts all state changes.

Self-executing program stored on a blockchain that automatically executes when predefined conditions are met.

A programming language for writing Ethereum and EVM-compatible smart contracts.

A variable stored permanently on the blockchain as part of a smart contract's data.

The arrangement of state variables in a smart contract's storage, affecting gas costs and upgrade compatibility.

A smart contract whose logic can be updated after deployment, usually via proxy architecture.

An abstracted transaction request used in account abstraction, processed by a mempool and bundlers.

Python-like programming language for smart contracts emphasizing security and simplicity over flexibility.