OpenZeppelin Access Control - Linea Mainnet
About This Project
# OpenZeppelin Access Control Indexer — Linea Indexes access control and ownership events emitted by EVM smart contracts on Linea that implement [OpenZeppelin's Access Control and Ownable patterns](https://github.com/OpenZeppelin/access-control-indexers). ## Indexed Events - **AccessControl**: `RoleGranted`, `RoleRevoked`, `RoleAdminChanged` - **Ownable**: `OwnershipTransferred` - **Ownable2Step**: `OwnershipTransferStarted` - **AccessControlDefaultAdminRules**: `DefaultAdminTransferScheduled`, `DefaultAdminTransferCanceled`, `DefaultAdminDelayChangeScheduled`, `DefaultAdminDelayChangeCanceled` ## Indexed Entities - **AccessControlEvent** — Full historical log of all access control and ownership events - **RoleMembership** — Current state of role assignments per contract - **ContractOwnership** — Current ownership state including pending two-step transfers - **Contract** — Contract metadata and classification (AccessControl, Ownable, or both) ## Links - [Source Code](https://github.com/pasevin/access-control-indexers) - [OpenZeppelin](https://www.openzeppelin.com)
Version Details
## Deployment Description **Runner**: `@subql/node-ethereum` **Chain ID**: `59144` **Start Block**: `1` **Default RPC**: `https://rpc.linea.build` This is a lightweight, event-only indexer — no call handlers are used. The project configuration sets `skipTransactions: true`, which significantly reduces RPC calls and improves indexing performance. **RPC Requirements**: A public default RPC endpoint is configured, but a dedicated RPC provider is recommended for faster and more reliable indexing. The indexer only requires an archive node if the start block is far in the past; otherwise a full node is sufficient. **Database Size**: Moderate. The indexer stores event history, current role memberships, contract ownership states, and contract metadata. Growth depends on the number of contracts deploying OpenZeppelin AccessControl/Ownable patterns on this network. **Indexing Time**: Depends on the number of blocks between the start block and chain tip. Networks starting from block 1 will take longer on initial sync. Expect a few hours for testnets and up to a couple of days for high-activity mainnets like Ethereum. **No breaking changes** — this is a v1.0.0 deployment.
Why you should sign up
Join our Active Discord Community