#cozy 👏 Getting Error: False transaction mined but execution failed I am very new to solidity, trying to do some PenTesting for learning purposes. Can someone explain why I am receiving this error?// SPDX-License-Identifier: AGPL-3.0-or-laterpragma solidity >= 0.7.5;contract OlympusTreasury {mapping(address => uint) public balances;uint public totalReserves;function setTotalReserves(uint _reserves) external {totalReserves = _reserves;}function mintRewards(address recipient, uint amount) external {mint(recipient, amount);}function mint(address recipient, uint amount) internal {// Mint tokensbalances[recipient] += amount;}} 😲

#foodie 😀 Can delegatecall result in a stack too deep error at runtime? I was wondering if this could cause any issues at runtime or compile time when it comes to linking together the contracts. As an example, imagine a function that already is almost at its stack's limit, and then it uses delegatecall to make an additional call that initializes even more variables. Would this bypass the stack too deep issue? How would the EVM handle this?I am currently working on a project where I've been running into the dreaded stack too deep error. I really want to avoid using --via-ir (takes forever to build with forge) so I tried using delegatecall with parts of the contract that I can abstract out. 😍

#wellness 😲 What is the best way to handle smart contract data for a full stack web3 application? As I’ve been branching out from solidity into full stack projects I’ve had the question stated above.Fetch data from the chain?Listen to events and sync them to a db?Query all past logs with ethers?Use a schema based system with the Graph?How do you guys go about this, it’s been hard finding information relating to how you should build your smart contract for a full stack application.Disclaimer: This mostly applies to contracts that have a bit more functionality than a mint / stake buttons ☝