253861
benny

@bennylada #253861

DeFi plumber
227 Follower 83 Following
253861
benny
@bennylada·09:17 04/11/2024
Fun MEV fact of the day: Sandwich attackers are slightly more efficient on Curve than on Uniswap v2 - but still extremely efficient on both platforms. If you get sandwiched, you will get rinsed up to < 0.005% of your specified min amount 3 out of 4 times.
https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/8b854e24-dbe6-41bc-0b87-1bc2f0171200/original
https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/62f15b45-f537-448f-e011-e669149dc700/original
253861
benny
@bennylada·06:07 31/10/2024
Over the last few days, I spent some time adding protocol language info to DefiLlama's hack page (https://defillama.com/hacks )with 0xngmi's help. I used the opportunity to review the data and chart some stuff. 🧵

DefiLlama

DefiLlama is a DeFi TVL aggregator. It is committed to providing accurate data without ads or sponsored content, as well as transparency.

defillama.com
253861
benny
@bennylada·05:52 06/08/2024
https://arxiv.org/abs/2407.05981

Towards Understanding the Bugs in Solidity Compiler

Solidity compiler plays a key role in enabling the development of smart contract applications on Ethereum by governing the syntax of a domain-specific language called Solidity and performing compilation and optimization of Solidity code. The correctness of Solidity compiler is critical in fostering transparency, efficiency, and trust in industries reliant on smart contracts. However, like other software systems, Solidity compiler is prone to bugs, which may produce incorrect bytecodes on blockchain platforms, resulting in severe security concerns. As a domain-specific compiler for smart contracts, Solidity compiler differs from other compilers in many perspectives, posing unique challenges to detect its bugs. To understand the bugs in Solidity compiler and benefit future research, in this paper, we present the first systematic study on 533 Solidity compiler bugs. We carefully examined their characteristics (including symptoms, root causes, and distribution), and their triggering test cases. Our study leads to seven bug-revealing takeaways for Solidity compiler. Moreover, to study the limitations of Solidity compiler fuzzers and bring our findings into practical scenarios, we evaluate three Solidity compiler fuzzers on our constructed benchmark. The results show that these fuzzers are inefficient in detecting Solidity compiler bugs. The inefficiency arises from their failure to consider the interesting bug-inducing features, bug-related compilation flags, and test oracles

arxiv.org
253861
benny
@bennylada·00:08 10/02/2024
Couple more liquidations then ???
https://i.imgur.com/gsYED9f.jpg
/curvefinance
253861
benny
@bennylada·09:13 08/02/2024
Some great thoughts on ways to improve Curve's gauge controller by @wavey0x A must read for all projects considering veTokenomics!
https://i.imgur.com/vcuGdX6.jpg
/curvefinance
253861
benny
@bennylada·11:23 05/02/2024
Trying to track a contract but events are missing the data you need? dyRPC overlays let you add your own events and even custom logic to any deployed contract. It even works with Vyper contracts!
https://hackmd.io/@crebsy/H1jO9onua
https://github.com/crebsy/dyrpc-overlays

dyRPC overlays - HackMD

Overlays allow you to add your custom logic to already deployed contracts to simulate new events and new read-only functions on top of them. With overlays you can create new view functions, modify existing ones, change field visibility, emit new events and query the historical data of any contract with your modified source code. :sparkles:

hackmd.io

GitHub - crebsy/dyrpc-overlays

Contribute to crebsy/dyrpc-overlays development by creating an account on GitHub.

github.com
/EVM