EntryPoint IntelligenceERC-4337 on Avalanche C-Chain Data to 2026-10-25

Examples v06-failed-outer-handleops

v06-failed-outer-handleops

v0.6 outer transaction reverted 1 operation

Bundler 0x4337…a93d Unattributed bundler #2 (EOA) (third-party label: Pimlico) evidence level: hint tried to submit 1 UserOperation(s) to EntryPoint v0.6, but the whole transaction reverted, so nothing happened except that the bundler paid 0.00335265333122668 AVAX in fees.

Transaction
0x5f081018dc82d89d26516778192d15a98a4c1ccd4ab4daa8559ad7a9babf2d53 explained →
Block
97,535,679
Outer status
reverted grade: observed
UserOperations
1 in 1 handleOps call
Selector
0x1fad948c
How to read the evidence markers

Evidence levels (how strong an address label is)

  • evidence level: primary source The vendor or protocol itself publishes this exact address
  • evidence level: self-description What the contract says about itself via a getter; contracts can claim any name
  • evidence level: cluster Shares a key, getter or bytecode with labelled addresses: same machinery, not proof of the same operator
  • evidence level: hint Ranking, explorer tag, metadata or third-party label: a clue, never proof
  • evidence level: unlabelled No registry label. In running text, an address without a marker has no label.

Evidence grades (how a value was obtained), strongest first

grade: observed grade: decoded grade: recomputed grade: recovered grade: contract read grade: inferred grade: unknown

Weaker grades are set in italics. Hover or focus a marker for its definition; full definitions.

  • Outer transaction reverted (status 0): the receipt has no logs; every effect was undone.

Who was involved

Bundler
0x4337…a93d Unattributed bundler #2 (EOA) (third-party label: Pimlico) evidence level: hint
sent and paid for the outer transaction · grade: observed
Called contract
0x5ff1…2789 EntryPoint v0.6 evidence level: primary source
grade: observed
EntryPoint
0x5ff1…2789 EntryPoint v0.6 evidence level: primary source
v0.6 handleOps · grade: decoded
Beneficiary
0x4337…a93d Unattributed bundler #2 (EOA) (third-party label: Pimlico) evidence level: hint
the beneficiary argument of handleOps · same address as the bundler · grade: decoded

Operations: what was asked, what happened

Operation 1

v0.6 outcome unknown index 0

Account 0x06a0…7a62 asked to call selector 0x4b268241 on 0x5bbb…603a Collateral coordinator (application unattributed) evidence level: hint (function unknown); the op did not execute; gas sponsored by 0x6666…c68b Pimlico singleton paymaster (EntryPoint v0.6) evidence level: primary source.

Who was involved

Smart account
0x06a0…7a62 evidence level: unlabelled
the operation's sender field · grade: decoded
Account code
0xd3f5…40ab ZeroDev Kernel v0.2.3 implementation evidence level: primary source
contract code and storage read at block 97535679 · EIP-1967 proxy · grade: contract read
Paymaster
0x6666…c68b Pimlico singleton paymaster (EntryPoint v0.6) evidence level: primary source
the operation's paymasterAndData field · grade: decoded
Signer key
0x018e…958d evidence level: unlabelled
signature scheme raw ECDSA(userOpHash), an EOA (secp256k1) key; matches the on-chain owner getter Kernel v2 ECDSAValidator.ecdsaValidatorStorage=0x018e6f075469474ec313b7e76992b472d9b4958d at block 97535679. A key, not a person. · grade: contract read

What was asked

Entry function on the account: execute(address,uint256,bytes,uint8) grade: decoded

  1. Call 1 call selector 0x4b268241 on 0x5bbb…603a Collateral coordinator (application unattributed) evidence level: hint (function unknown)

    target 0x5bbb…603a Collateral coordinator (application unattributed) evidence level: hint · function 0x4b268241 grade: unknown · via the account's execute function

What happened

The outer transaction reported reverted grade: observed; this UserOperation unknown grade: unknown.

  • Call 1 not executed grade: observedthe whole outer transaction reverted, so nothing it requested took effect

Money for this operation

No per-operation charge: the outer transaction reverted, so the EntryPoint charged nothing and the bundler alone paid the receipt fee.

Sponsorship: sponsored, terms not visible: a paymaster pays the gas charge from its deposit; its terms (free, token-paid, off-chain billing) are not decodable from this record grade: decoded

The call trace

6 internal calls grade: observed in a trace.

Errors in the call tree:

  • call to 0x5ff1…2789 EntryPoint v0.6 evidence level: primary source handleOps((address,uint256,bytes,bytes,uint256,uint256,uint256,uint256,uint256,bytes,bytes)[],address): execution reverted · EntryPoint FailedOp: op #0 "AA25 invalid account nonce" -- invalid account nonce (already used or out of order)

an error deep in the call tree can be caught by a caller; only the outer status and the UserOp success flag say what persisted

Money

Outer receipt fee (bundler → chain)
0.003353 AVAX
gas used × effective gas price, paid once
Σ actualGasCost (deposits → beneficiary)
0.000000 AVAX
1 operation charge

The outer fee (what the bundler paid the network) and the per-op charges (what the EntryPoint collected from deposits and paid to the beneficiary) are different quantities. They are listed, never added together; their difference is not 'bundler profit'.

The logs

Receipt logs (0), in order, with the lifecycle phase each belongs to
#EmitterEventPhase

What we can't tell

  • The signer is a key (address) recovered from the signature. It does not tell you which person, company or bot controls that key.
  • A paymaster paid the gas charge, but that does not mean the user paid nothing: the paymaster may bill the user off-chain or in a token (see sponsorship mode).
  • The beneficiary is only where gas compensation was sent; it is not the user, and it is not proof of who runs the bundler.
  • Some labels are only at 'hint' or 'cluster' level; treat them as leads, not identity.
  • Names (token symbols, labels) are metadata unless their evidence level says otherwise.
  • The outer fee is what the bundler paid the network for the whole transaction; it cannot be split fairly across ops or legs, and comparing it with the per-op charges does not give bundler profit.
  • Because the outer transaction reverted there are no logs: we only know what was requested, not why it failed (a trace or replay would be needed).

Rendered from the explain record (schema epi.explain/v1). Address labels and levels come from the current registry. How evidence grades and levels work →