OpenZeppelin Access Control - Stellar Mainnet

Version: 1.0.0

About This Project

# OpenZeppelin Access Control Indexer — Stellar Indexes access control and ownership events emitted by Soroban smart contracts on the Stellar network that implement [OpenZeppelin's Access Control and Ownable patterns](https://github.com/OpenZeppelin/access-control-indexers). ## Indexed Events - **Access Control**: `role_granted`, `role_revoked`, `role_admin_changed` - **Admin**: `admin_transfer_initiated`, `admin_transfer_completed`, `admin_renounced` - **Ownable**: `ownership_transfer`, `ownership_transfer_completed`, `ownership_renounced` ## 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-stellar` **Chain ID**: `Public Global Stellar Network ; September 2015` **Start Block**: `60377000` **Default Horizon RPC**: `https://horizon.stellar.org` **Default Soroban RPC**: `https://soroban-rpc.mainnet.stellar.gateway.fm` This is a lightweight, event-only indexer for Soroban smart contracts. It listens for contract events emitted by OpenZeppelin's Stellar AccessControl and Ownable implementations. **RPC Requirements**: Both a Horizon endpoint and a Soroban RPC endpoint are required. Public defaults are configured, but dedicated endpoints are recommended for faster and more reliable indexing. Note that Soroban RPC nodes typically only serve a rolling window of recent ledgers, so the start block should be within that window or the node must have extended history. **Database Size**: Small to moderate. Stellar's smart contract ecosystem is newer, so the volume of indexed events is lower compared to EVM mainnets. **Indexing Time**: Relatively fast — the start block (ledger 60,377,000) is recent, so initial sync should complete within a few hours. **No breaking changes** — this is a v1.0.0 deployment.