HiveSQL Update - RC Delegations data available
![](https://i.imgur.com/tYFgjui.png)
Retrieving information about RC delegations can be a bit tricky. Although the Hive API generally allows you to retrieve information from the blockchain, there is no API call to easily find who has delegated RCs to whom.
### HiveSQL to the rescue
Fortunately, HiveSQL allows you to retrieve related information from the `TxCustoms` table which includes all creation, modification or removal of RC delegation operations carried out by users.
However, the main difficulty comes from the fact that you have to filter custom_json operations, parse the JSON payload and perform computations with each operation to get the state of the delegation between accounts.
Add to this that you have to take into account a [bug that I discovered and reported](https://gitlab.syncad.com/hive/hive/-/issues/395) yesterday. This bug in the processing of RC delegation operations will probably be corrected soon, but it must be taken into account for existing operations.
### HiveSQL to the rescue (bis repetita)
Due to all the technical reasons mentioned above, retrieving an accurate list of delegators or delegatees is complex and resources consuming task.
That's why I added a new non-consensus state table named `RCDelegations` to the HiveSQL database in order to allow its users to retrieve RC delegations data quickly and easily.
It contains the list of all **active** RC delegations with the following info:
|Column|Description|
|-|-|
|delegator|The account delegating Hive Power|
|delegatee|The account receiving Hive Power delegation|
|rc|The amount of RCs delegated|
## Documentation
HiveSQL documentation has been updated and can be viewed at https://docs.hivesql.io
## Support
If you have any questions or remarks, support for HiveSQL is provided on [Discord](https://discord.gg/kyEFDfT).
---
### Check out my apps and services
### [Vote for me as a witness ![](https://i.imgur.com/2bi4SnT.png)](https://vote.hive.uno/@arcange)
See: HiveSQL Update - RC Delegations data available by @arcange