Bhargava Shastry retweeted
📺⚡️ #TrustX2023 Speaker: Bhargava Shastry
🎙️ @ibags, Security Engineer, @ethereum Foundation spoke about "Finding and Understanding Miscompilation Bugs in the Solidity Compiler"
youtu.be/mJcUiwP03S0
Bhargava Shastry retweeted
🚨 Storage Write Removal Bug On Conditional Early Termination 🚨
On Sep 5, we found a bug in Solidity's Yul optimizer by differential fuzzing. The bug was introduced in v0.8.13. We assigned the bug a severity of "medium/high". [2/3]
#xp
Bhargava Shastry retweeted
🚀10 Days to go! Call for Papers
⏫Kickstart your 2022 by sharing knowledge with the World from your latest research at Nullcon's 1st Berlin edition
😎Choose from different categories & Submit your paper➡️bit.ly/3CDsg1T
#NullconBerlin2022 #CFP #infosec #cybersecurity
Bhargava Shastry retweeted
Mark your calendars for @EthCC! 📅📌
→ Solidity in 2021 / @ethchris /July 21st 11:45 am
→ Fully automated formal verification: How far can we go? / @leonardoalt / July 22nd 10:15 am
→ Sourcify: Towards safer contract interactions for humans / @_franzihei / July 22nd 3:35 pm
Bhargava Shastry retweeted
⛽️✨ The former can provide a big gas benefit when writing structs that cover a full storage slot to storage. For details on how this works, please have a look at the "Notable New Features" section of the release announcement! blog.soliditylang.org/2021/0…
Bhargava Shastry retweeted
🐞 In summary, the bytecode optimizer incorrectly re-used previously evaluated Keccak-256 hashes. You are unlikely to be affected if you do not compute Keccak-256 hashes in inline assembly. blog.soliditylang.org/2021/0…
Bhargava Shastry retweeted
Solidity v0.8.3 is out! 0.8.3 is a bugfix release that fixes an important bug about how the optimizer handles the Keccak256 opcode. In addition, it includes two improvements to the optimizer.
📖: blog.soliditylang.org/2021/0…
🐞: blog.soliditylang.org/2021/0…
💾: github.com/ethereum/solidity…
Bhargava Shastry retweeted
#MuchClicked
* @EF_ESP Staking community grants
* @gridplus Lattice hardware wallet is back
* @ibags fuzz testing @solidity_lang
* @stlouisfed DeFi review
* @SourcifyEth contract autoverification
* @semenov_roman_ ABI fetcher @HardhatHQ plugin
* @ofnumbers PoW = enviro nightmare
⟠ Latest Week in $ETH News
📥Hacks from @ETHGlobal MarketMake & @EthereumDenver
🪙 @mcuban: $ETH better store of value than $BTC
🥷 @paradigm CTF writeups
⏩ weekinethereumnews.com/week-…
🙏 thanks to @CelerNetwork for making this issue possible
Bhargava Shastry retweeted
Interested in contributing to Solidity but don't know where to start? We compiled an overview post to walk you through the ways you can get involved covering...
→ Issues
→ Testing
→ Docs
→ Community
→ Language Design
Help is always welcome! ☺️
blog.soliditylang.org/2021/0…
Bhargava Shastry retweeted
Want to learn more about how Solidity uses fuzz testing? In our latest blog post, @ibags gives an overview and explains the ins and outs of front-end fuzzers for the parser/analyser, and back-end fuzzers for the optimiser. 🧑🔬📖 ↓
blog.soliditylang.org/2021/0…
Bhargava Shastry retweeted
Solidity 0.8.1 is out! 🆙 v0.8.1 introduces many new features for the SMTChecker, updates the emscripten version for building soljson.js to 2.0.12, allows to catch panic errors and adds other small improvements.
📖: blog.soliditylang.org/2021/0…
💾: github.com/ethereum/solidity…
Bhargava Shastry retweeted
Want to get a digest of what the Solidity team has been up to in the last few months? As per usual, we're part of the EF-supported teams report! ☺️ blog.ethereum.org/2020/12/09…
While #eth2 has been on our minds, incredible progress has been made in recent months by all EF-supported teams. We might’ve missed quite a bit from each other while apart this year, so we’re excited to share a *long* report detailing their updates today.
blog.ethereum.org/2020/12/09…
Bhargava Shastry retweeted
The Solidity Developer Survey 2020 is live! Please participate and help us shape the future of Solidity by sharing your feedback, dev habits, needs and insights.
📋 Take the survey: docs.google.com/forms/d/e/1F…
✨ Read the announcement: blog.soliditylang.org/2020/1…
Bhargava Shastry retweeted
Replying to @ibags
@ibags leads us through the challenges of #fuzzing #soliditycompilers and how he modified #libfuzzer to test the code. You can find his talk from #FuzzConEurope2020 here 👉 hubs.li/H0xTt3s0
Bhargava Shastry retweeted
We just released #Solidity 0.5.15 fixing a bug that was introduced in 0.5.14 that only manifests itself if you manually activate the Yul optimizer. github.com/ethereum/solidity…
Bhargava Shastry retweeted
#Solidity talks today: Yul+eWasm: 10.10 in B7 (slides: chriseth.github.io/notes/tal…) Formal verification (yay, loops!) by @leonardoalt: same time in B2 (@leonardoalt). Fuzzing the compiler by @ibags at 10.40 in B2.
Bhargava Shastry retweeted
Things are going well, and I'm hiring 5 people for ShiftLeft's code analysis team in Berlin: shiftleft.io/careers/?gh_jid… :)
Bhargava Shastry retweeted
Question for Solidity assembly devs: Do you use the side-effect of mload and other operations to modify msize() or would you be fine with the optimizer being able to remove redundant mload and maybe even mstore instructions?
8%remove redundant mloads
62%remove red. mstore+mloads
31%don't touch my msize!
13 votes • Final results Bhargava Shastry retweeted
Please upgrade: #Solidity 0.5.6 released, fixing an optimizer bug introduced in 0.5.5. Also included: dynamic calldata arrays and structs for ABIEncoderV2 and arrays for SMTChecker @ethereum github.com/ethereum/solidity…


















