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
I don't think the issue is with your node setup since both your local node and the public node (base-rpc.publicnode.com) are giving the same "execution reverted" error. This means the contract itself is rejecting the call.
Looking at your transaction data:
Contract: 0x4401e30b92c0a9deab9943880586d478d5d15c89
Function: 0xc913d6d5
Params: An address (d0b53d...) and what looks like a boolean/uint (1)
The contract is probably rejecting your call because either the input parameters don't meet the contract's requirements or function's conditions aren't being met.
My guess would be there's some business logic causing it to revert.
When I execute eth_call, the node reports an error
curl --location 'http://127.0.0.1:8545' \ --header 'Content-Type: application/json' \ --data '{ "jsonrpc":"2.0", "method":"eth_call", "params":[ { "to":"0x4401e30b92c0a9deab9943880586d478d5d15c89", "data":"0xc913d6d5000000000000000000000000d0b53d9277642d899df5c87a3966a349a798f2240000000000000000000000000000000000000000000000000000000000000001" }, "latest"], "id":1 }'
start base with conifg:
geth --datadir=/opt/rockx/base --verbosity=3 --http --http.corsdomain=* --http.vhosts=* --http.addr=0.0.0.0 --http.port=8545 --http.api=web3,debug,eth,net,engine,txpool,personal --authrpc.addr=0.0.0.0 --authrpc.port=8551 --authrpc.vhosts=* --authrpc.jwtsecret=/opt/rockx/base/secrets/engine-auth-jwt --ws --ws.addr=0.0.0.0 --ws.port=8546 --ws.origins=* --ws.api=debug,eth,net,engine,txpool --syncmode=full --gcmode=full --maxpeers=100 --rollup.sequencerhttp=https://mainnet-sequencer.base.org --rollup.halt=major --op-network=base-mainnet --port=30303 --rpc.gascap=150000000 --txpool.globalqueue=5000
I use a public node https://base-rpc.publicnode.com/ that can return data
What is the reason for this? Thank you.
The text was updated successfully, but these errors were encountered: