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

ERC-4337 · Avalanche C-Chain

EntryPoint Intelligence

Learn what ERC-4337 EntryPoints do, then read real Avalanche C-Chain activity with the evidence behind every claim.

How it works See 17 examples
Illustration: many small signed operations are packed into one bundle, which passes through a single shared contract (orange) and fans out to separate smart accounts.
Many signed operations are bundled into one transaction, pass through the shared EntryPoint contract, and fan out to separate smart accounts.

An EntryPoint is a single shared smart contract (one per ERC-4337 version) that lets smart-contract wallets act like ordinary accounts without any change to the chain itself. Users sign UserOperations instead of transactions, and a bundler packs them into one normal transaction that calls the EntryPoint’s handleOps. The EntryPoint checks that each operation is authorised and paid for, runs it through the user’s smart account, and settles the gas, which a third-party paymaster may cover.

The cast

One operation passes through these parties, in this order:

  1. SignerThe key (an EOA key, passkey or multisig owners) that authorises an operation. A key, never a person.
  2. BundlerThe EOA that signs the outer transaction and pays native gas up front.
  3. EntryPointThe shared singleton contract that validates, executes and settles every operation.
  4. Smart account (sender)The contract wallet that holds assets and makes the calls; what apps call “the user’s address”.
  5. Target appThe contracts the account actually calls: tokens, bridges, swaps, games…

Around the EntryPoint

Paymaster
An optional contract whose EntryPoint deposit pays an operation’s gas (sponsorship).
Factory
Deploys the smart account on its first operation at a precomputed address.
Beneficiary
Where the EntryPoint sends the gas it collected; usually the bundler itself.

How one handleOps call works, step by step →

Avalanche C-Chain at a glance

UserOperations, all versions
6.5M
6,531,304 since 2023-04-17
Outer transactions
6.4M
6,400,627 bundles that emitted a UserOperationEvent
Distinct smart accounts
947.8K
addresses, not people
Paymaster-paid share
97.3%
sponsored is not the same as free
Receipt fees paid by bundlers
8,995 AVAX
counted once per outer transaction
Busiest day
73,641
v0.7 UserOps on 2026-05-03

On the archive’s last day, 2026-10-25: 1,092 outer transactions carried 1,226 UserOperations for 459 distinct accounts (1.2692 AVAX in receipt fees).

Monthly UserOperations on C-Chain, all EntryPoint versions

  • v0.6
  • v0.7
  • v0.8
  • v0.9
Monthly UserOperations on C-Chain, all EntryPoint versionsStacked monthly UserOperation counts per EntryPoint version from the start of activity to the archive end.0500K1M1.5M20232024202520261,127,804 (2026-04)
Monthly UserOperations on C-Chain, all EntryPoint versionsStacked monthly UserOperation counts per EntryPoint version from the start of activity to the archive end.0500K1M1.5M20232024202520261,127,804 (2026-04)
Show the data as a table
Monthly UserOperations on C-Chain, all EntryPoint versions
Monthv0.6v0.7v0.8v0.9Total
2023-04102000102
2023-05189000189
2023-06275000275
2023-07353000353
2023-0853,64300053,643
2023-09157,637000157,637
2023-1097,14800097,148
2023-1162,12700062,127
2023-1233,30700033,307
2024-0144,89700044,897
2024-0237,45400037,454
2024-0336,02800036,028
2024-0429,91850029,923
2024-0530,566120030,578
2024-0626,327570026,384
2024-0716,9121470017,059
2024-0813,1883,9740017,162
2024-0917,9192280018,147
2024-1015,4113150015,726
2024-1111,7993140012,113
2024-1216,58415,3560031,940
2025-0117,2919,4310026,722
2025-0255,7098,3660064,075
2025-0365,1521,9050067,057
2025-0450,9644,61812055,594
2025-0546,12936,0307082,166
2025-0658,22671,65700129,883
2025-0763,6318,1270071,758
2025-0861,37112,2370073,608
2025-0953,2817,9074061,192
2025-1044,956103,6432380148,837
2025-1122,250296,740620319,052
2025-1230,027145,166100175,203
2026-0173,389500,726210574,136
2026-0228,316966,45360994,775
2026-0346,2931,040,423801,086,724
2026-0462,7351,065,0293821,127,804
2026-0531,617487,83219694520,162
2026-0629,8198,96621,82340,610
2026-0730,81910,23311,81742,870
2026-0833,98212,6534401,80848,883
2026-0928,73524,998521,70755,492
2026-1016,74624,27171,48542,509

What happened: the 2026 surge was Pixelmon players logging in daily, until it switched off in May →

More charts: the 2026 v0.7 burst, concentration, failures →

Explore

How to read this site

Every named address carries a small marker for the evidence level of its label, and facts on the example pages carry an evidence grade for how the value was obtained. A name is never a real-world identity, and a signer is only a key.

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.