» Structure of a Contract
Structure of a Contract
Contracts in Solidity are similar to classes in object-oriented languages. Each contract can contain
declarations of State Variables, Functions, Function Modifiers, Events, Errors, Struct Types and
Enum Types. Furthermore, contracts can inherit from other contracts.
There are also special kinds of contracts called libraries and interfaces.
The section about contracts contains more details than this section, which serves to provide a quick
overview.
State Variables
State variables are variables whose values are permanently stored in contract storage.
// SPDX-License-Identifier: GPL-3.0
pragma solidity >=0.4.0 <0.9.0;
contract SimpleStorage {
uint storedData; // State variable
// ...
}
See the Types section for valid state variable types and Visibility and Getters for possible choices
for visibility.
Functions
Functions are the executable units of code. Functions are usually defined inside a contract, but they
can also be defined outside of contracts.
// SPDX-License-Identifier: GPL-3.0
pragma solidity >=0.7.1 <0.9.0;
contract SimpleAuction {
function bid() public payable { // Function
// ...
}
}
// Helper function defined outside of a contract
function helper(uint x) pure returns (uint) {
return x * 2;
}
Function Calls can happen internally or externally and have different levels of visibility towards
other contracts. Functions accept parameters and return variables to pass parameters and values
between them.
Function Modifiers
Function modifiers can be used to amend the semantics of functions in a declarative way (see
Function Modifiers in the contracts section).
Overloading, that is, having the same modifier name with different parameters, is not possible.
Like functions, modifiers can be overridden.
// SPDX-License-Identifier: GPL-3.0
pragma solidity >=0.4.22 <0.9.0;
contract Purchase {
address public seller;
modifier onlySeller() { // Modifier
require(
[Link] == seller,
"Only seller can call this."
);
_;
}
function abort() public view onlySeller { // Modifier usage
// ...
}
}
Events
Events are convenience interfaces with the EVM logging facilities.
// SPDX-License-Identifier: GPL-3.0
pragma solidity >=0.4.21 <0.9.0;
contract SimpleAuction {
event HighestBidIncreased(address bidder, uint amount); // Event
function bid() public payable {
// ...
emit HighestBidIncreased([Link], [Link]); // Triggering event
}
}
See Events in contracts section for information on how events are declared and can be used from
within a dapp.
Errors
Errors allow you to define descriptive names and data for failure situations. Errors can be used in
revert statements. In comparison to string descriptions, errors are much cheaper and allow you to
encode additional data. You can use NatSpec to describe the error to the user.
// SPDX-License-Identifier: GPL-3.0
pragma solidity ^0.8.4;
/// Not enough funds for transfer. Requested `requested`,
/// but only `available` available.
error NotEnoughFunds(uint requested, uint available);
contract Token {
mapping(address => uint) balances;
function transfer(address to, uint amount) public {
uint balance = balances[[Link]];
if (balance < amount)
revert NotEnoughFunds(amount, balance);
balances[[Link]] -= amount;
balances[to] += amount;
// ...
}
}
See Errors and the Revert Statement in the contracts section for more information.
Struct Types
Structs are custom defined types that can group several variables (see Structs in types section).
// SPDX-License-Identifier: GPL-3.0
pragma solidity >=0.4.0 <0.9.0;
contract Ballot {
struct Voter { // Struct
uint weight;
bool voted;
address delegate;
uint vote;
}
}
Enum Types
Enums can be used to create custom types with a finite set of ‘constant values’ (see Enums in types
section).
// SPDX-License-Identifier: GPL-3.0
pragma solidity >=0.4.0 <0.9.0;
contract Purchase {
enum State { Created, Locked, Inactive } // Enum
}