Skip to content
This repository has been archived by the owner on Oct 20, 2024. It is now read-only.

error: "Missing/invalid userOpHash" when querying userOpHash with secondary entryPoints #333

Open
antoncoding opened this issue Oct 31, 2023 · 1 comment

Comments

@antoncoding
Copy link
Contributor

Summary

Hi team, we have been using the stackup bundler on our app chain testnet, and we ran into the following issue today, when we deploy a new EntryPoint and add that to ERC4337_BUNDLER_SUPPORTED_ENTRY_POINTS variable as a secondary entrypoint address.

ERC4337_BUNDLER_SUPPORTED_ENTRY_POINTS=0xC25Dc675669907Aee390C0144eA8bB3DFd33a4c7

We now set it to

ERC4337_BUNDLER_SUPPORTED_ENTRY_POINTS=0xC25Dc675669907Aee390C0144eA8bB3DFd33a4c7,0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789

We tried sending the tx to the new 0x5FF13... entrypoint and it worked, but querying the status with eth_getUserOperationReceipt result in invalidOpHash error. Here is a more comprehensive log:

2023-10-31T03:38:05.898418+00:00 app: 
{"level":"info","bundler_mode":"private","entrypoint":"0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789","chain_id":"901","userop_hash":"0x89bf9a0667fe7f78846367e360024e2a599e79f2c0149a242fc27c9421c83e28","v":0,"logger":"stackup_bundler/client/eth_sendUserOperation","caller":"/tmp/build_e7170bdc/pkg/client/client.go:138","time":"2023-10-31T03:38:05Z","message":"eth_sendUserOperation ok"}
2023-10-31T03:38:05.898473+00:00 app: {"level":"info","bundler_mode":"private","client_id":"***********","method":"POST","status_code":200,"body_size":103,"path":"/","latency":"1.117860191s","rpc_method":"eth_sendUserOperation","v":0,"logger":"stackup_bundler/http","caller":"/tmp/build_e7170bdc/internal/logger/middleware.go:60","time":"2023-10-31T03:38:05Z"}

# Return error when requesting userOp status
{"level":"error","bundler_mode":"private","userop_hash":"0x89bf9a0667fe7f78846367e360024e2a599e79f2c0149a242fc27c9421c83e28","error":"Missing/invalid userOpHash","logger":"stackup_bundler/client/eth_getUserOperationReceipt","caller":"/tmp/build_e7170bdc/pkg/client/client.go:207","time":"2023-10-31T03:38:08Z","message":"eth_getUserOperationReceipt error"}
2023-10-31T03:38:08.451507+00:00 app: {"level":"info","bundler_mode":"private","client_id":"***********","method":"POST","status_code":200,"body_size":124,"path":"/","latency":"140.114496ms","rpc_method":"eth_getUserOperationReceipt","v":0,"logger":"stackup_bundler/http","caller":"/tmp/build_e7170bdc/internal/logger/middleware.go:60","time":"2023-10-31T03:38:08Z"}

# 0x89bf9a0... is correctly batched and submitted on-chain 
2023-10-31T03:38:11.432767+00:00 app: {"level":"info","bundler_mode":"private","entrypoint":"0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789","chain_id":"901","batch_userop_hashes":["0x89bf9a0667fe7f78846367e360024e2a599e79f2c0149a242fc27c9421c83e28"],"dropped_userop_hashes":[],"relayer_est_revert_reasons":[],"txn_hash":"0xb5aeb6f1a53cdcdd2263396a5d5633da1c8cbfcf480885bd84798db577d688e7","duration":"5.223555446s","v":0,"logger":"stackup_bundler/bundler/run","caller":"/tmp/build_e7170bdc/pkg/bundler/bundler.go:189","time":"2023-10-31T03:38:11Z","message":"bundler run ok"}

# Return error when requesting userOp status
2023-10-31T03:38:12.920433+00:00 app: {"level":"error","bundler_mode":"private","userop_hash":"0x89bf9a0667fe7f78846367e360024e2a599e79f2c0149a242fc27c9421c83e28","error":"Missing/invalid userOpHash","logger":"stackup_bundler/client/eth_getUserOperationReceipt","caller":"/tmp/build_e7170bdc/pkg/client/client.go:207","time":"2023-10-31T03:38:12Z","message":"eth_getUserOperationReceipt error"}

I tried restarting the bundler with only the new entryPoint, and everything works smoothly. So I assume the error came from setting multiple entryPoints

@antoncoding antoncoding changed the title error: "Missing/invalid userOpHash" when querying userOpHash to secondary entryPoints error: "Missing/invalid userOpHash" when querying userOpHash with secondary entryPoints Oct 31, 2023
@bhargavkacharla
Copy link

@antoncoding can you share the env format, I deployed stackup bundler locally but getting this error when submitting the userops. This is for mumbai network using ERC4337_BUNDLER_ETH_CLIENT_URL=https://rpc.ankr.com/polygon_mumbai

data {
  error: {
    code: -32502,
    data: 'The method debug_traceCall does not exist/is not available',
    message: 'The method debug_traceCall does not exist/is not available'
  },
  id: 1,
  jsonrpc: '2.0'
}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants