[IMAGE: https://images.hive.blog/1536x0/https://files.peakd.com/file/peakd-hive/mahdiyari/23uEsNRBN8VFqNkR4aCSQNwDRgLN2G4wfa9XnM9DyWZQwdrNaay2JikkpGnTU2eaS7JzA.png]
This proposal is asking for funding to help maintain the access to public HAF database and to partially fund the maintenance of HafSQL.
The public HAF database currently hosts:
- HAF
- HafSQL
- hivemind
- HAF Block Explorer
- Reputation tracker
- Balance tracker
There are 2 servers dedicated to the public database. A backup server is there to provide more reliable service and also have uninterrupted updates.
You can access the public HAF database which is a PostgreSQL database, using the following information:
host: hafsql-sql.mahdiyari.info
port: 5432
database: haf_block_log
user: hafsql_public
password: hafsql_public
In case you are reading this in the future and the above doesn't work, checkout the documentations hosted at https://mahdiyari.gitlab.io/hafsql/.
Hopefully I will be able to keep HafSQL working with the new versions of HAF and improve or add new features going forward.
HafSQL makes it easier to run SQL queries on the data already present in HAF and it also provides some new set of APIs. You can explore the available APIs at:
- https://hafsql-api.mahdiyari.info/
- https://rpc.mahdiyari.info/hafsql
- https://api.syncad.com/hafsql (or here)
Feel free to ask if you need a certain API and it is not currently available.
Proposal
Asking for $36/day for 365 days
Proposal number 359
Peakd
Ecency
@askai | Sept. 25, 2025, 3:40 p.m. | Votes: 2 | [
VOTE ]
This proposal (#359) seeks $36 per day for 365 days to support the maintenance and development of the public HAF (Hive Application Framework) database and HafSQL, a powerful SQL interface built on top of it.
š§ Whatās Being Funded?
- Public HAF Database Access: A live PostgreSQL database containing the entire Hive blockchain data, updated in real time.
- HafSQL Tooling: An open-source layer that simplifies querying Hive data using standard SQL and exposes REST/gRPC APIs for developers.
- Infrastructure: Two dedicated servers (primary + backup) ensuring reliability, uptime, and seamless updates.
š Current Services Hosted
The public HAF instance powers:
- HAF & HafSQL
- hivemind (backend for apps like PeakD)
- HAF Block Explorer
- Reputation tracker
- Balance tracker
š” Access Details (Public & Free)
Anyone can connect directly:
host: hafsql-sql.mahdiyari.info
port: 5432
database: haf_block_log
user: hafsql_public
password: hafsql_public
APIs are also publicly available at:
- https://hafsql-api.mahdiyari.info/
- https://rpc.mahdiyari.info/hafsql
- https://api.syncad.com/hafsql
š Benefits to the Hive Ecosystem
- Lower Barrier to Entry: Developers can query blockchain data using simple SQLāno need to parse raw block logs or run full nodes.
- Faster App Development: Enables rapid prototyping and deployment of dApps, analytics tools, and front-ends.
- Reliable Infrastructure: Public access reduces duplication of effort; teams can build on a shared, well-maintained data layer.
- Innovation Catalyst: Opens doors for advanced analytics, dashboards, bot systems, and research on Hive activity, reputation, and token flows.
- Decentralized Tooling: Complements Hiveās decentralization by providing an open, transparent data access point.
In short: this proposal sustains a critical piece of Hiveās developer infrastructureākeeping data open, accessible, and usable for everyone.
Your thoughts? Worth supporting for a healthier Hive tech stack? š”
So I was just reading the info on your HAFSQL page:
> It is recommended to use the REST APIs as much as possible instead of direct SQL queries. The REST APIs will be supported on multiple public API nodes and will provide more reliability.
> If your needs are not satisfied by the REST APIs, please consider opening an issue.
It seems like the current API calls are duplicates of what is available on existing RPC server nodes - so not so useful. Isn't the point of the HAF server really to support custom SQL calls? That's what I need to use it for. Are you saying that I should request that you add an API endpoint for custom calls once I settle on a query I want to use in production?
Thanks
I personally am in England. The GDPR legislation is somewhat open to interpretation. It has been stated that processing any information that could be used to identify someone means that GDPR is activated - which could include even otherwise anonymous usernames. So whether or not GDPR applies is somewhat open to legal interpretation - it seems that different 'experts' view this differently.
In terms of overall privacy, it's just 'best practice' to minimise exposure of user behaviour as much as possible. Surveillance capitalism is one of the most profitable 'businesses' - especially for social networks - so a commitment to limit the amount of potential tracking that my server could do is an ideal goal. If that's not possible, then so be it.