# Databases

On the Lido protocol, we have the following databases to store various types of data:

<table><thead><tr><th width="258">Databases</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>LidoSubmission</td><td>Records user deposits into the Lido protocol, including sender, amount, shares minted, and pool totals.</td><td></td></tr><tr><td>LidoTransfer</td><td>Tracks transfers of Lido shares between addresses, including balances before and after.</td><td></td></tr><tr><td>SharesBurn</td><td>Stores data related to burning of Lido shares during rebase events.</td><td></td></tr><tr><td>LidoApproval</td><td>Captures approval events where an account grants permission to another address to spend tokens.</td><td></td></tr><tr><td>CurrentFee</td><td>Stores the current fee configuration for the Lido protocol, including fee breakdown.</td><td></td></tr><tr><td>LidoConfig</td><td>Contains general configuration settings for the Lido protocol, such as addresses, limits, and flags.</td><td></td></tr><tr><td>LidoTotals</td><td>Stores the total amount of Ether pooled and total Lido shares in circulation.</td><td></td></tr><tr><td>LidoStats</td><td>Provides statistics about Lido, including unique holders and the last completed oracle report ID.</td><td></td></tr><tr><td>LidoHolder</td><td>Lists addresses that hold Lido shares and their current balance status.</td><td></td></tr><tr><td>LidoShares</td><td>Stores the number of Lido shares held by each address.</td><td></td></tr><tr><td>LidoOracleConfig</td><td>Contains configuration settings for the Lido oracle, such as quorum size and epoch details.</td><td></td></tr><tr><td>LidoOracleReport</td><td>Stores data about oracle reports, including total rewards, hash, and items processed.</td><td></td></tr><tr><td>LidoOracleComplete</td><td>Records completed oracle reports, including epoch ID, beacon balance, and transaction details.</td><td></td></tr><tr><td>LidoTotalReward</td><td>Stores information about total rewards earned, fees, APR, and share allocations.</td><td></td></tr><tr><td>LidoOracleMember</td><td>Lists members of the Lido oracle and their removal status.</td><td></td></tr><tr><td>LidoNodeOperatorFees</td><td>Records fees allocated to each node operator based on total rewards.</td><td></td></tr><tr><td>LidoNodeOperatorShares</td><td>Stores the number of Lido shares allocated to each node operator.</td><td></td></tr><tr><td>LidoBeaconReport</td><td>Contains beacon reports submitted by callers, including epoch ID, balance, and validators.</td><td></td></tr><tr><td>LidoOracleExpectedEpoch</td><td>Lists the expected epoch IDs for which oracle reports should be generated.</td><td></td></tr></tbody></table>


---

# 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://docs.blockflow.network/use-cases/lido-finance/databases.md?ask=<question>
```

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.
