Practical overview
When it fits
Use it when an LBRY-focused application or analysis workflow needs a self-hosted SQL index instead of querying the blockchain directly over RPC.
Who it is for
- Developers building LBRY explorers or data applications
- Operators maintaining LBRY analytics and reporting infrastructure
- Teams needing SQL access to indexed LBRY blockchain and claim data
Documented uses
- Synchronize LBRY blocks and transactions into structured database tables
- Query LBRY claims, addresses and transaction records with SQL
- Provide indexed data to dashboards, explorers and downstream applications
- Maintain derived blockchain data through scheduled jobs
Requirements & limits
The repository is public and uses the MIT license. The project is designed for server and self-hosted operation.
- It requires an LBRY full node connection over JSON-RPC.
- MySQL is the documented structured-data store.
- The service combines block synchronization, an HTTP API and scheduled derived-data jobs in one binary.
- The read-only SQL endpoint is public in the documented API, while processing and synchronization routes use API-key protection.
- The daemon includes handling for blockchain reorganizations and transaction dependencies.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Chainquery as an LBRY SQL data layer
Configure the documented Chainquery components needed to synchronize LBRY blockchain records into MySQL.
Before you start
- A server suitable for self-hosted operation
- An LBRY full node using lbcd or lbrycrd
- A MySQL database
- Chainquery configuration for the API and database connections
Steps
Connect Chainquery to the LBRY full node over JSON-RPC.
Configure the MySQL storage connection and separate API read connection.
Run the single Chainquery serve binary to start the daemon and API server.
Use the documented scheduled jobs and API routes for derived data, status and read-only SQL access.
Expected outcome
A Chainquery service with an indexing daemon, MySQL-backed LBRY records and an HTTP API for querying and operational access.
Guide limitations
- Processing and synchronization endpoints require an API key when enabled; metrics can require basic authentication.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- OdyseeTeam/chainquery · Official homepage title · retained in its source language

