Contracts for Smart Contract Developers
Contract structure is how Solidity code is organised: constructors, visibility and modifiers, inheritance, interfaces, libraries, events and custom errors. Low-level features such as call, delegatecall, fallback and receive functions and inline assembly give direct control of the EVM. They are powerful but a frequent source of security problems.
Stage: Solidity Language · Part of the Smart Contract Developer roadmap · Last reviewed 19 November 2026
What to learn in Contracts
- Apply public, external, internal and private visibility correctly
- Write modifiers for access control and use inheritance to share logic
- Define interfaces and libraries, and know when to use each
- Declare events and custom errors instead of long revert strings
- Explain what receive, fallback and delegatecall do and where they are risky
Contracts interview questions
What does delegatecall do?
It runs another contract's code in the context of the caller, so storage, msg.sender and msg.value stay those of the calling contract. Proxy upgrade patterns rely on it, and a wrong storage layout or untrusted target can corrupt state or hand over control.
What is the difference between an interface and an abstract contract?
An interface only declares function signatures and cannot hold state or implementations. An abstract contract can mix implemented and unimplemented functions and can have state variables. Interfaces define what other contracts can call, while abstract contracts offer partial shared logic.
Where Contracts fits in the Smart Contract Developer roadmap
Contracts belongs to the Solidity Language stage (intermediate level), which takes about 33 hours. The language in depth.
Other units in this stage
Back to the full Smart Contract Developer roadmap