You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hey there i am having an issue with transaction simulation failing (where if i just skip simulation with the exact same payload and parameters it works)
seems like it has something to do with doing native transfers during my call (simulation) because I get back that I got this error execution reverted, data: "0x9fb7cfe2" which corresponds to this spot in my SC
my suspicion: it may be a bug in simulation where native transfers fail for some reason (maybe forwarding gas? maybe thinking the EOA can't receive eth? idk)
let me know what you think!
The text was updated successfully, but these errors were encountered:
Component
provider, pubsub
What version of Alloy are you on?
0.9.2
Operating System
Linux
Describe the bug
hey there i am having an issue with transaction simulation failing (where if i just skip simulation with the exact same payload and parameters it works)
seems like it has something to do with doing native transfers during my call (simulation) because I get back that I got this error execution reverted, data: "0x9fb7cfe2" which corresponds to this spot in my SC
https://github.com/kassandraoftroy/stealth-gas-contracts/blob/main/src/StealthGasStation.sol#L63
tx payload:
on contract address:
0x943285f1a29281e59514fF35Dc16E5a14E123a27
network: holesky testnet, using an alchemy rpc
wss://eth-holesky.g.alchemy.com/v2/xxxxxxx
block number: ~3196935 (or current)
source code doing simulation: https://github.com/kassandraoftroy/stealth-gas-backend/blob/main/src/http_server.rs#L164-L186
caller/signer of tx being simulated:
0x4B5BaD436CcA8df3bD39A095b84991fAc9A226F1
here you can see that on tenderly simulation the same tx succeeds! https://www.tdly.co/shared/simulation/1efe08e3-a571-4511-82e1-46df3d3bbf05
my suspicion: it may be a bug in simulation where native transfers fail for some reason (maybe forwarding gas? maybe thinking the EOA can't receive eth? idk)
let me know what you think!
The text was updated successfully, but these errors were encountered: