Solidity Fundamentals
Solidity is a statically typed, contract-oriented programming language for writing smart contracts that run on the Ethereum Virtual Machine. A contract combines code and persistent state at a blockchain address, so callers can update shared rules and data through transactions.
itProgramming languages | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic - Solidity Fundamentals
Solidity is how you write programs that live at an address on an EVM chain: a little bundle of functions glued to storage that anyone can poke with a transaction.
Before that model, the usual answer was "trust a server operator." Here the operator is a peer-to-peer network that runs the same bytecode for every caller. That is the whole sales pitch, and also why a missed require becomes everybody's bug.
Three ideas carry the rest.
First, a contract is code plus state. You compile .sol with solc, deploy bytecode, and callers use the ABI like a typed remote API. The pragma is not decoration; it is how you refuse a compiler that would change your meaning.
Second, data has a home. storage persists, memory is a temporary scratchpad, calldata is read-only input. Mix them up and you get aliasing surprises that look like "local" edits until production balances move.
Third, other contracts are hostile co-workers with reentrancy privileges. Sending Ether can run their code. Checks-Effects-Interactions means finish your bookkeeping before you hand them the microphone. msg.sender is who just called you; tx.origin is a family history lesson you should not use as a lock.
The surprise for newcomers from ordinary backends: private is an ABI curtain, not a vault. Chain observers can still read slots. If a value must stay secret, it should not be on-chain in the clear.
When you want the map, read the Intro and slides. When you want the dense tables, open the Cheatsheet. When you want commands, use the Practice Reference and the Exercise. Field Notes is where judgment lives after the grammar sticks.
If you remember only one operational habit, remember this: pin the compiler, write the pragma to match, update storage before talking to strangers, and treat every on-chain value as public evidence. The rest of the catalog is how those habits look in tables, quizzes, and commands.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://docs.soliditylang.org/en/latest/
Supports
- Language overview, compiler docs index, and navigation into topic pages
- https://docs.soliditylang.org/en/latest/introduction-to-smart-contracts.html
Supports
- Contract as code plus state at an address
- SimpleStorage and subcurrency examples, events, msg.sender, require
- https://docs.soliditylang.org/en/latest/layout-of-source-files.html
Supports
- SPDX license identifiers and version pragma semantics
- https://docs.soliditylang.org/en/latest/structure-of-a-contract.html
Supports
- State variables, functions, modifiers, events, errors, inheritance forms
- https://docs.soliditylang.org/en/latest/types.html
Supports
- Value versus reference types, integers, mappings, data locations
- https://docs.soliditylang.org/en/latest/contracts.html
Supports
- Visibility, getters, events, interfaces, libraries, abstract contracts
- https://docs.soliditylang.org/en/latest/units-and-global-variables.html
Supports
- wei, gwei, ether denominations and msg, block, tx globals
- https://docs.soliditylang.org/en/latest/security-considerations.html
Supports
- Reentrancy, Checks-Effects-Interactions, tx.origin, private data limits
- Unexpected Ether and low-level call pitfalls
- https://docs.soliditylang.org/en/latest/installing-solidity.html
Supports
- solc, solcjs, Docker images, solc-bin distribution
- https://docs.soliditylang.org/en/latest/using-the-compiler.html
Supports
- Compiler outputs, Standard JSON, settings
- https://soliditylang.org/
Supports
- Project portal linked from the official repository README
- https://github.com/argotorg/solidity
Supports
- Canonical repository identity after ethereum/solidity redirect
- https://github.com/argotorg/solidity/blob/develop/Changelog.md
Supports
- Timeline milestones and 0.8.0 checked arithmetic default
- https://github.com/argotorg/solidity/security/policy
Supports
- Security reporting scope and latest-release patch posture
- https://github.com/argotorg/solidity/blob/develop/README.md
Supports
- Language definition as statically typed contract-oriented EVM language
- https://ethereum.org/developers/docs/smart-contracts/
Supports
- Smart contract account framing used alongside Solidity docs
- https://github.com/sindresorhus/awesome
Supports
- Discovery path into topic awesome lists
- https://github.com/bkrem/awesome-solidity
Supports
- Curated Remix, Hardhat, Foundry, OpenZeppelin, Slither, Solhint entries
- https://blog.sigmaprime.io/solidity-security.html
Supports
- Practitioner field notes on reentrancy and historical visibility failures
- https://github.com/sigp/solidity-security-blog
Supports
- Source repository for the Sigma Prime Solidity security write-up
- https://remix.ethereum.org/
Supports
- Awesome link and landscape entry for the browser IDE
- https://hardhat.org/
Supports
- Awesome link and landscape entry for the Hardhat toolchain
- https://book.getfoundry.sh/
Supports
- Foundry documentation destination for learners
- https://docs.openzeppelin.com/contracts/
Supports
- OpenZeppelin Contracts documentation used in awesome links
- https://github.com/protofire/solhint
Supports
- Solhint project destination from Awesome Solidity
- https://github.com/crytic/slither
Supports
- Slither analyzer destination from Awesome Solidity
- https://github.com/crytic/solc-select
Supports
- solc-select helper listed on Awesome Solidity
- https://cryptozombies.io/
Supports
- Interactive tutorial destination from Awesome Solidity
- https://github.com/argotorg/solidity/releases
Supports
- Update source page and Atom feed for compiler releases