Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion contracts/STYLE_GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -234,7 +234,7 @@ Please read the [Foundry Guide](FOUNDRY_GUIDE.md). No new tests should be writte
- Otherwise, Solidity contracts should have a pragma that is locked to a specific version.
- Example: Most concrete contracts.
- Avoid changing pragmas after the audit. Unless there is a bug that affects your contract, then you should try to stick to a known good pragma. In practice, this means we typically only support one (occasionally two) pragma for any “major”(minor by Semver naming) Solidity version.
- The current advised pragma is `0.8.26`, lower versions should be avoided when starting a new project. Newer versions can be considered.
- The current advised pragma is `0.8.35`, lower versions should be avoided when starting a new project. Newer versions can be considered.
- Explicitly use the `Paris` hardfork when compiling with >=0.8.20 to keep the bytecode compatible with all chains.
- All contracts should have an SPDX license identifier. If unsure about which one to pick, please consult with legal. Most older contracts have been MIT, but some of the newer products have been using BUSL-1.1

Expand Down
Loading