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

Examples v08-bundle-beneficiary-is-paymaster

v08-bundle-beneficiary-is-paymaster

v0.8 succeeded 2 operations

Bundler 0x7e81…2f4c submitted a bundle of 2 v0.8 UserOperations for 2 smart account(s), requesting call x2 across 1 target contract(s); 2 of 2 succeeded.

Transaction
0x6c97b6bf1fa1de6e69eae496f94ba3a5265b0c94ac751756e86c91c11c6a8dc7 explained →
Block
95,285,437
Outer status
success grade: observed
UserOperations
2 in 1 handleOps call
Selector
0x765e827f
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.

Who was involved

Bundler
0x7e81…2f4c evidence level: unlabelled
sent and paid for the outer transaction · grade: observed
Called contract
0x4337…f108 EntryPoint v0.8 evidence level: primary source
grade: observed
EntryPoint
0x4337…f108 EntryPoint v0.8 evidence level: primary source
v0.8 handleOps · grade: decoded
Beneficiary
0xef45…d8c0 evidence level: unlabelled
the beneficiary argument of handleOps · differs from the bundler · grade: decoded

Operations: what was asked, what happened

Operation 1 of 2

v0.8 succeeded index 0

Account 0xa681…8d4d asked to call executePayment(...) on 0x7bfa…03a8; the op succeeded; gas sponsored by 0xef45…d8c0.

Who was involved

Smart account
0xa681…8d4d evidence level: unlabelled
the sender field of UserOperationEvent · grade: observed
Account code
0x00ed…3f38 evidence level: unlabelled
contract code and storage read at block 95285437 · EIP-1167 minimal proxy · grade: contract read
Paymaster
0xef45…d8c0 evidence level: unlabelled
the operation's paymasterAndData field · grade: decoded
Signer key
0x7e81…2f4c evidence level: unlabelled
signature scheme raw ECDSA(userOpHash), an EOA (secp256k1) key; matches the on-chain owner getter owner()=0x7e818d18da640539e715f96b9c94eb7a8eb52f4c at block 95285437. A key, not a person. · grade: contract read

What was asked

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

  1. Call 1 call executePayment(...) on 0x7bfa…03a8

    target 0x7bfa…03a8 evidence level: unlabelled · function executePayment(bytes32,uint256) grade: decoded · via the account's execute function

What happened

The outer transaction reported success grade: observed; this UserOperation succeeded grade: observed.

  • Call 1 ran (its logs show it) grade: inferredthe target emitted 1 log(s) in this op's execution segment (unknown event 0x96820c9f x1); this shows it ran, not what it achieved

Token movements logged during this operation:

Money for this operation

The EntryPoint charged this operation 0.000017 AVAX (actualGasCost) grade: observed, taken from paymaster deposit 0xef45dae4935f6b21ac12d845b28bfc4771a3d8c0 grade: inferred and paid to the beneficiary grade: inferred.

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

Operation 2 of 2

v0.8 succeeded index 1

Account 0x3d75…0e69 asked to call executePayment(...) on 0x7bfa…03a8; the op succeeded; gas sponsored by 0xef45…d8c0.

Who was involved

Smart account
0x3d75…0e69 evidence level: unlabelled
the sender field of UserOperationEvent · grade: observed
Account code
0x00ed…3f38 evidence level: unlabelled
contract code and storage read at block 95285437 · EIP-1167 minimal proxy · grade: contract read
Paymaster
0xef45…d8c0 evidence level: unlabelled
the operation's paymasterAndData field · grade: decoded
Signer key
0x5513…7233 evidence level: unlabelled
signature scheme personal_sign(userOpHash), an EOA (secp256k1) key. A key, not a person. · grade: recovered

What was asked

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

  1. Call 1 call executePayment(...) on 0x7bfa…03a8

    target 0x7bfa…03a8 evidence level: unlabelled · function executePayment(bytes32,uint256) grade: decoded · via the account's execute function

What happened

The outer transaction reported success grade: observed; this UserOperation succeeded grade: observed.

  • Call 1 ran (its logs show it) grade: inferredthe target emitted 1 log(s) in this op's execution segment (unknown event 0x96820c9f x1); this shows it ran, not what it achieved

Token movements logged during this operation:

Money for this operation

The EntryPoint charged this operation 0.000015 AVAX (actualGasCost) grade: observed, taken from paymaster deposit 0xef45dae4935f6b21ac12d845b28bfc4771a3d8c0 grade: inferred and paid to the beneficiary grade: inferred.

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

Money

Outer receipt fee (bundler → chain)
0.000027 AVAX
gas used × effective gas price, paid once
Σ actualGasCost (deposits → beneficiary)
0.000032 AVAX
2 operation charges

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 (9), in order, with the lifecycle phase each belongs to
#EmitterEventPhase
00x4337…f108 EntryPoint v0.8 evidence level: primary sourceBeforeExecutionboundary
10xc891…2acd evidence level: unlabelledTransferexecution
20x7bfa…03a8 evidence level: unlabelledotherexecution
30x4337…f108 EntryPoint v0.8 evidence level: primary sourceUserOperationEventexecution
40xc891…2acd evidence level: unlabelledTransferexecution
50x7bfa…03a8 evidence level: unlabelledotherexecution
60x4337…f108 EntryPoint v0.8 evidence level: primary sourceUserOperationEventexecution
70x4337…f108 EntryPoint v0.8 evidence level: primary sourceDepositedcompensation
80xef45…d8c0 evidence level: unlabelledPaymasterDeposited(uint256)compensation

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.
  • UserOp success=true only means the account's call did not revert at the top level. Accounts and batch executors can catch inner failures, so individual legs can still have failed.
  • Some contracts involved are unlabelled: event and function names shown for them are signature-database hints and do not identify the app or protocol.
  • 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.

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