Unexpected data in our useroperations collection

[tomarsachin2271]

While getting data from mongodb to clickhouse, i encountered this unexpected transaction which doesn't make sense in our database.

Transaction Details

Query: {transactionId: '0xb838f0b5782a29973213c37225c972b32ccec9b33cf6065bea54f35bb2f07389'}
Collection: useroperations_8453
database: relayer-node-service

Observation

The transaction hash saved in this document is 0xe57ea8e2450950c0eb93ed6fd27b8441d1c1e5a3a4e96958cd51f53e937f938e

1. This is not sent by our bundlers
2. This is a legacy transaction with type 1, our bundler never sent this type of transaction
3. Even though this is AA transaction, but EP is not called directly. Some method executeWithPaymaster is called. Paymaster used here is some CheckoutPaymaster by Fun.xyz

Expected Outcome

How this transaction ended up in our database? This is not our bundler transaction and should not be in our database. This needs to be debugged, either our node provider sent the wrong data while fetching the transaction receipt and we saved it to our database without checking it.

This happened once in hyphen where node provider sent the wrong data. We should check this in our bundler code also.

[arcticfloyd1984]

Current Findings

The above transactionId is linked to a transaction that got front-runned. A bug in the code was causing issues related to saving receipts for these transactions. The error was:

This did not allow the saving of some data for a certain duration.

@TheDivic fixed this bug in this PR.

There was a certain chunk of transactions for which this error occurred so there would be transactional data in the blockchain_transactions table that doesn't have an updated front-runned receipt.