# #AA 03 AA aggregation table of EVM chains The `EntryPoint` contract of ERC4337 has been deployed on multiple EVM chains. You can view the list of all chains that have deployed the `EntryPoint` contract here: * v0.5: * v0.6: If you want to analyze the combined data of all EVM chains, it would clearly be too cumbersome to write the analyses one by one. Therefore, based on the spellbook of the dune platform, we have aggregated the data of the EntryPoint contracts of two versions on 9 major blockchains into two new data tables. These tables can currently be directly used on the dune platform for easy analysis. The specific source code can be found at: * `account_abstraction_erc4337.userops`: contains UserOperationEvent event data from 9 chains, also joined with the transactions table and price table to get information like the bundler of each `userOp` and the gas fee paid for that transaction. * `account_abstraction_erc4337.account_deployed`: includes AccountDeployed event data from 9 chains Including blockchains: | | | | --------- | ------ | | Ethereum | Base | | Polygon | BNB | | Arbitrum | Celo | | Optimism | Gnosis | | Avalanche | | ## userops For a detailed definition of `UserOps`, see the link below: The aggregated table UserOps contains more information; the included field information is as follows: | COLUMN | DESCRIPTION | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | blockchain | blockchain which EntryPoint was deployed | | version | version of the EntryPoint contract | | block\_month | UTC event block date of each User Operation | | block\_time | UTC event block time of each User Operation | | entrypoint\_contract | the contract address of the EntryPoint | | tx\_hash | Unique transaction hash value tied to each transaction on the User Operation | | sender | the sender(AA wallet address) that submmited the user operation | | userop\_hash | Unique user operation hash | | success | weather the user operation is successfully execuated | | paymaster | the address that pay for the user operation gas fees on behalf of the user | | op\_fee | The gas paid by sender or paymaster It depends on the chain gas setting | | op\_fee\_usd | The user operation gas (in usd) paid by sender or paymaster. | | bundler | address that bundle UserOps and submit those UserOps to the final on-chain by send a EOA transaction. It is the transaction from address | | tx\_to | address where the bundler send the transaction | | gas\_symbol | the gas symbol paied for the transaction | | tx\_fee | the bundler paied gas value for the transaction | | tx\_fee\_usd | the bundler paied gas (in usd) value for the transaction | | beneficiary | the address where the bundler setting for the user operation pay for thier gas fee | The analysis will then be much simpler. For example, analyzing the distribution of user operations across 9 chains: ```sql with total_op as ( select blockchain as chain, * from account_abstraction_erc4337.userops ) select chain, count(*) as nums from total_op group by chain order by nums desc ``` ![](/files/0eu94QSE6ZmZwhKOOEen) For another example, analyzing the monthly profit of bundlers: ```sql with agg_ops as ( select row_number() over (partition by tx_hash order by userop_hash) as rn , sum(op_fee) over(PARTITION by tx_hash) as op_fee , sum(op_fee_usd) over(PARTITION by tx_hash) as op_fee_usd , tx_fee , tx_fee_usd , blockchain as chain , gas_symbol as symbol , block_time from account_abstraction_erc4337.userops ) , revenue as ( select date_trunc('month', block_time) as dt , sum(op_fee_usd - tx_fee_usd) as BundlerRevenueUSD from agg_ops where rn = 1 group by 1 ) select dt, sum(BundlerRevenueUSD) as TotalBundlerRevenueUSD, case when sum(BundlerRevenueUSD)>=0 then 'Positive' when sum(BundlerRevenueUSD)<0 then 'Negative' end as PosNeg from revenue group by 1 ``` ![](/files/MlJhY0pa5zmcARY1oDYc) ## account\_deployed The information contained in account\_deployed is relatively small, it just integrates the data of the two contract versions and several EVM chains together. See the link for detailed definitions: The fields included in the aggregated account\_deployed table are as follows: | COLUMN | DESCRIPTION | | -------------------- | ---------------------------------------------------------------------------- | | blockchain | blockchain which EntryPoint was deployed | | version | version of the EntryPoint contract | | block\_time | UTC event block time of each User Operation | | block\_month | UTC event block date of each User Operation | | userop\_hash | Unique user operation hash | | entrypoint\_contract | the contract address of the EntryPoint | | tx\_hash | Unique transaction hash value tied to each transaction on the User Operation | | sender | the sender(AA wallet address) that submmited the user operation | | paymaster | the address that pay for the user operation gas fees on behalf of the user | | factory | who can create a new AA Wallet. It's smart contract address | Using `account_deployed` aggregated tables makes analysis simpler as well. For example, getting the number of wallet factories on each chain: ```sql with total_op as ( select blockchain as chain, * from account_abstraction_erc4337.account_deployed ) select chain, count(distinct factory) as Factories from total_op group by 1 order by 2 desc ``` ![](/files/WQnKpmmbE7ZULcLE0ivB) For complete examples, please refer to the following link. This dashboard contains analyses of various aspects of `EntryPoint`: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://tutorial.sixdegree.xyz/account-abstraction/ch26-aa-aggregation-table-of-evm-chains.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.