Solidity is an object-oriented, high-level language for implementing smart contracts. 🌐 - an @argotorg project

Joined March 2020
We published a status update on Core Solidity: what the language can do today, what is still missing, what the community told us, and what comes next.
5
18
3
90
7,519
Solidity v0.8.38 is out. This release fixes a low-severity bug in the Yul optimizer, speeds up the Yul optimizer, and warns about identifiers in Yul and inline assembly that are going to be reserved starting from the Amsterdam EVM version.
3
13
4
51
1,895
The compiler now warns when swapn, dupn or exchange is used as an identifier in Yul or inline assembly. EIP-8024 adds opcodes with these names in the Amsterdam upgrade, and the names become reserved starting from the Amsterdam EVM version. Solidity identifiers are not affected.
2
124
Solidity retweeted
Try out the Core Solidity playground!
We published a status update on Core Solidity: what the language can do today, what is still missing, what the community told us, and what comes next.
1
1
14
808
The interviews are still ongoing. If you write, audit, teach or build tools for Solidity and think your feedback could shape Core Solidity, we would like to talk to you. Reach out to @_czepluch or write to coresolidity at argot dot org.
1
4
327
We will be in Mumbai for @EFDevcon where we will do a Core Solidity workshop on the 5th of Nov. We will also be presenting at @summit_defi on the 2nd of Nov Full post: soliditylang.org/blog/2026/1…
1
3
325
Solidity retweeted
Looking very much forward to this one. Getting to share the stage with many of the people I've followed and looked up to for years is going to be fun! Doing so while representing @solidity_lang even more so!
DSS 2026 welcomes @_czepluch “What you need to know about Core Solidity” Explore the session and make it part of My agenda: defisecuritysummit.org/2026/… Tickets: luma.com/9qtxqqxx
2
2
18
681
Solidity 0.8.37 is out.
10
53
12
367
21,885
Experimental SSA CFG backend: the greedy stack shuffler is replaced by a planning one. It computes a full plan for the target stack layout first, then emits the operations. Easier to maintain, and initial benchmarks show it is faster at roughly the same bytecode size.
1
4
395