We released Solidity v0.8.15! 🆙 Solidity 0.8.15 fixes two important bugs. On top of this, the release includes several minor bug fixes and improvements. For details on the bugs, please read the release blog post and the linked security alerts!
A few weeks ago we released Solidity v0.8.14! Solidity 0.8.14 fixes two important bugs. Apart from this, the release includes several minor bug fixes and improvements. For details on the bugs, read the release announcement and the included bug posts!
We can’t believe it’s already been four weeks since we met in Amsterdam for the 2nd Solidity Summit. Read our event summary on the blog or check the videos of the talks!
Solidity 0.8.13 has been released! 🥳 It fixes an important bug related to abi.encodeCall, extends the "using for" directive and implements "go to definition" for the LSP. We also consider compiling via Yul IR stable.
Speaker applications for the next Solidity Summit on 4/20 in Amsterdam are open! Help us make this event as packed with good content as possible by sharing your knowledge and updates. Apply for a talk here: https://summit.soliditylang.org/#sign-up
The Solidity Summit is finally back! After a first virtual Solidity Summit in 2020, we are excited to announce an in-person event. Solidity Summit 2022 is part of Devconnect and will happen on April 20 in Amsterdam.
Today is #ilovefs day!
We 💗 love 💗 #FreeSoftware and we wouldn't be here without many other amazing free software projects and the continued support of our ~500 contributors. Thank you! 👏💐https://github.com/ethereum/solidity/graphs/contributors
Submissions for the Underhanded Solidity Contest 2022 are open! This year's mission? Build a decentralized exchange where trades do not really work as expected...
📖 : https://blog.soliditylang.org/2022/02/09/underhanded-solidity-contest-2022-announcement/
Feedback wanted: Solidity does not yet support catching custom errors. We are currently evaluating different implementation options & would love to hear your thoughts. In which situations do you want to catch custom errors? Let us know in the forum! 🗃️⬇️ https://forum.soliditylang.org/t/feedback-wanted-catching-custom-errors-default-catch-clause/810
Interested in learning even more about what other developers think about Solidity, what they responded to the survey and how the results compare to 2020? Then make sure to read the full report! ⬇️ https://blog.soliditylang.org/2022/02/07/solidity-developer-survey-2021-results/
 Ethereum IDEs: Compared to 2020, Truffle (2020: 34.6% -> 2021: 17.9%) and Remix (2020: 29.3% -> 2021: 17%) lost significant share, while Hardhat, Brownie, Dapptools and newcomers like Foundry increased their share in users.
 Ethereum IDEs: Hardhat becomes the most popular Ethereum-specific development environment with almost 45% of all respondents using it. Truffle and Remix follow with a user share of roughly 17% each. Brownie (7.2%), Dapptools (5.6%), Scaffold-ETH (3.2%), Foundry/Forge (1.1%).
 Editors: More than 50% use VSCode as an editor to write Solidity, followed by Visual Studio (14%) and Remix (11%). Vim is used by 7% of respondents, followed by IntelliJ (5.8%) and Atom (3%).
 Future Features: A more efficient optimizer & the ability to catch custom errors are ranked as most important future features under discussion. Moreover, support for fractional numbers, better array management and fixing stack too deep are among the most anticipated features.
 Language Restrictiveness: More than 60% of respondents wish that Solidity becomes more restrictive/explicit (having more checks). 26% would prefer it to remain as is.
 Developer Experience: The majority (+70%) believes that the Solidity developer experience improved in the last year. Only 1.6% are of the opinion it got worse.
Solidity is an object-oriented, high-level language for implementing smart contracts. 🌐
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.