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

Examples v07-daily-result-registry

v07-daily-result-registry

v0.7 succeeded 1 operation

Bundler 0x2873…7b7b Bundler EOA submitting 'Avax-dle' ops evidence level: hint submitted one v0.7 UserOperation: account 0x2784…9a42 asked to call selector 0x1e781cbd on 0xfb31…8a3f Signed daily-result registry (EIP712 domain 'Avax-dle' v1) evidence level: self-description (function unknown); the op succeeded; gas sponsored by 0x25ff…8df9 Paymaster used by 'Avax-dle' participants evidence level: hint.

Transaction
0xad946150133f7fcd9120ffec5a50e4ceb488b23449603f27807336a635ac484a explained →
Block
97,838,807
Outer status
success grade: observed
UserOperations
1 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
0x2873…7b7b Bundler EOA submitting 'Avax-dle' ops evidence level: hint
sent and paid for the outer transaction · grade: observed
Called contract
0x0000…a032 EntryPoint v0.7 evidence level: primary source
grade: observed
EntryPoint
0x0000…a032 EntryPoint v0.7 evidence level: primary source
v0.7 handleOps · grade: decoded
Beneficiary
0x2873…7b7b Bundler EOA submitting 'Avax-dle' ops evidence level: hint
the beneficiary argument of handleOps · same address as the bundler · grade: decoded

Operations: what was asked, what happened

Operation 1

v0.7 succeeded index 0

Account 0x2784…9a42 asked to call selector 0x1e781cbd on 0xfb31…8a3f Signed daily-result registry (EIP712 domain 'Avax-dle' v1) evidence level: self-description (function unknown); the op succeeded; gas sponsored by 0x25ff…8df9 Paymaster used by 'Avax-dle' participants evidence level: hint.

Who was involved

Smart account
0x2784…9a42 evidence level: unlabelled
the sender field of UserOperationEvent · grade: observed
Account code
0xb4a7…e031 evidence level: unlabelled
contract code and storage read at block 97838807 · EIP-1967 proxy · grade: contract read
Paymaster
0x25ff…8df9 Paymaster used by 'Avax-dle' participants evidence level: hint
the operation's paymasterAndData field · grade: decoded
Signer key
0xcddc…a7bf evidence level: unlabelled
signature scheme personal_sign(userOpHash), an EOA (secp256k1) key; matches the on-chain owner getter owner()=0xcddc28eab48d1df14d4f9fc33357677716d2a7bf at block 97838807. 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 selector 0x1e781cbd on 0xfb31…8a3f Signed daily-result registry (EIP712 domain 'Avax-dle' v1) evidence level: self-description (function unknown)

    target 0xfb31…8a3f Signed daily-result registry (EIP712 domain 'Avax-dle' v1) evidence level: self-description · function 0x1e781cbd grade: unknown · 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 0xa865f5e7 x1); this shows it ran, not what it achieved

Money for this operation

The EntryPoint charged this operation 0.001137 AVAX (actualGasCost) grade: observed, taken from paymaster deposit 0x25ff7720cff5e7c479cad2a8b48f99561f7c8df9 Paymaster used by 'Avax-dle' participants evidence level: hint 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.001057 AVAX
gas used × effective gas price, paid once
Σ actualGasCost (deposits → beneficiary)
0.001137 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 (4), in order, with the lifecycle phase each belongs to
#EmitterEventPhase
00x0000…a032 EntryPoint v0.7 evidence level: primary sourceBeforeExecutionboundary
10xfb31…8a3f Signed daily-result registry (EIP712 domain 'Avax-dle' v1) evidence level: self-descriptionotherexecution
20x25ff…8df9 Paymaster used by 'Avax-dle' participants evidence level: hintUserOperationSponsored(bytes32,uint128,address)execution
30x0000…a032 EntryPoint v0.7 evidence level: primary sourceUserOperationEventexecution

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.
  • 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 →