ERC-4337 UserOperation Math

This node recomputes the exact 32 bytes an ERC-4337 account signs, from the UserOperation fields you supply. It does not verify a signature or recover a signer address, and the ERC-4337 specification itself excludes the signature from the hashed struct, so supplying one changes nothing. A recomputed hash is not an inclusion, and a reconciled charge is not a settlement. This node never reads chain state: it cannot tell you whether the account exists, whether the EntryPoint holds a deposit, whether the nonce is still valid, or whether the operation was ever mined.

The EntryPoint version is yours to declare, and it changes what gets hashed. v0.6 hashes a ten-word UserOperation pack. v0.7 hashes an eight-word PackedUserOperation, in which verificationGasLimit and callGasLimit pack into a single accountGasLimits word and maxPriorityFeePerGas and maxFeePerGas pack into gasFees. The prefund formulas differ as well. Guessing the version would silently produce a wrong hash that still looks perfectly well formed, so this node refuses to guess: an unrecognised version returns INDETERMINATE rather than falling back to either layout.

L1 data and blob fees are never derived. On rollups the total charge includes an L1 data-fee component that, after EIP-4844, depends on the inclusion-time L1 basefee and blob basefee. Neither is derivable offline from a UserOperation, so this node does not compute them. An L1 data fee enters the reconciliation only when you declare it, and when you do not, its absence is reported as a named gap rather than quietly absorbed into a residual.

The value block.basefee is never fetched either. The effective gas price is min(maxFeePerGas, maxPriorityFeePerGas + block.basefee). When your two fee caps are equal, the EntryPoint's own legacy shortcut returns maxFeePerGas directly and the basefee drops out, so the price is fully derivable offline. When they differ, the price is reported as null with the reason unless you declare a basefee. It is never guessed.