smartcontracts

@0xsShady @primejacks are you running this on a machine that's already running a Geth instance for Ethereum?

> So, apparently, the issue here was lack of RAM. This happens because the first time l2geth runs, it gets killed and then upon restart, it tries to fetch the...

> Has anyone found a solution to this? I have the same problem. Increase the amount of RAM given to L2Geth, then `docker compose down -v` and `docker compose up...

Closing, make sure to run l2geth with enough RAM

No more compiler warnings in contracts-bedrock, closing!

Likely that an upstream provider is returning bad results and these results are being cached by our proxy.

Believed to be fixed, this was an issue with an upstream node provider. Please reopen this issue if anyone detects similar caching problems.

@pradyuman-verma Have you tested this on an Ethereum testnet? I don't think what you're trying to do will work, because Solidity explicitly encodes errors using a special format `abi.encodeWithSignature("Error(string), err)`.

Something like this will work: ``` //SPDX-License-Identifier: MIT pragma solidity ^0.8.0; pragma experimental ABIEncoderV2; contract revertTry { function revertNow() public { bytes memory revertData = abi.encodeWithSignature("Error(string)", "testing"); assembly { let...

I believe this is the current Geth behavior. Custom reverts do not start with `keccak256("Error(string)")[0:4]` and therefore the errors aren't being decoded. Here I've replicated this behavior on Goerli: oldRevert:...