From c83c176c161ecfa94b0d297d58ab7d75a6199525 Mon Sep 17 00:00:00 2001
From: Ryan <80392855+RayXpub@users.noreply.github.com>
Date: Thu, 13 Aug 2026 12:01:39 +0400
Subject: [PATCH] chore: bump solidity version in style guide

---
 contracts/STYLE_GUIDE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contracts/STYLE_GUIDE.md b/contracts/STYLE_GUIDE.md
index 65ff14d545..787df71d76 100644
--- a/contracts/STYLE_GUIDE.md
+++ b/contracts/STYLE_GUIDE.md
@@ -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