v06-wrapper-five-handleops

Bundler 0xf70d…dbef Unattributed bundler #48 (EOA) evidence level: hint submitted a bundle of 5 v0.6 UserOperations through a wrapper contract for 1 smart account(s), requesting call x5 across 1 target contract(s); 5 of 5 succeeded.

Transaction

0x8d40e3df4cffadcd525bdd65046ea0a07c5fa1284c79926a415017a2180f124e explained →

Block

96,955,051

Outer status

success grade: observed

UserOperations

5 in 5 handleOps calls

Selector

0xcd6e13f7

• 5 BeforeExecution events: this tx made 5 separate handleOps calls (typical of a wrapper contract). Logs between calls are labelled 'between_calls' unless they can be tied to an op.
• The outer transaction was sent to a non-EntryPoint contract (a wrapper). Logs before BeforeExecution may include the wrapper's own activity, not only validation.

Who was involved

Bundler

0xf70d…dbef Unattributed bundler #48 (EOA) evidence level: hint

sent and paid for the outer transaction · grade: observed

Called contract

0xb92f…ff4f evidence level: unlabelled

not an EntryPoint: a wrapper contract · grade: observed

EntryPoint (call 1)

0x5ff1…2789 EntryPoint v0.6 evidence level: primary source

v0.6 handleOps, embedded in the wrapper's call · grade: decoded

Beneficiary (call 1)

0xc727…74a3 evidence level: unlabelled

the beneficiary argument of handleOps · differs from the bundler · grade: decoded

EntryPoint (call 2)

0x5ff1…2789 EntryPoint v0.6 evidence level: primary source

v0.6 handleOps, embedded in the wrapper's call · grade: decoded

Beneficiary (call 2)

0xc727…74a3 evidence level: unlabelled

the beneficiary argument of handleOps · differs from the bundler · grade: decoded

EntryPoint (call 3)

0x5ff1…2789 EntryPoint v0.6 evidence level: primary source

v0.6 handleOps, embedded in the wrapper's call · grade: decoded

Beneficiary (call 3)

0xc727…74a3 evidence level: unlabelled

the beneficiary argument of handleOps · differs from the bundler · grade: decoded

EntryPoint (call 4)

0x5ff1…2789 EntryPoint v0.6 evidence level: primary source

v0.6 handleOps, embedded in the wrapper's call · grade: decoded

Beneficiary (call 4)

0xc727…74a3 evidence level: unlabelled

the beneficiary argument of handleOps · differs from the bundler · grade: decoded

EntryPoint (call 5)

0x5ff1…2789 EntryPoint v0.6 evidence level: primary source

v0.6 handleOps, embedded in the wrapper's call · grade: decoded

Beneficiary (call 5)

0xc727…74a3 evidence level: unlabelled

the beneficiary argument of handleOps · differs from the bundler · grade: decoded

Operations: what was asked, what happened

Money

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

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.
• 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 signer is a passkey (a P-256 public key held by a device or password manager); there is no address to look up, and the key does not tell you who holds the device.
• 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.
• handleOps was embedded inside a wrapper contract's call. The wrapper's own logic (what it did before/after, and with which funds) is not decoded.

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