Proposal: Public Hivemind SQL service

Hivemind, a tool by Steemit inc., is a backend API service currently replace some of the endpoints of steemd. It's in use for a good amount time.

<p dir="auto">I've been running a public Hivemind node, distributing daily database <a href="https://hivemind.emrebeyler.me/dumps/" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">snapshots almost 9 months. There is also <a href="https://tower.emrebeyler.me" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">tower, a REST interface for Hivemind data, is developed and maintained by me, so far. <p dir="auto">RPC and REST interfaces are just the tip of the iceberg since the underlying database -PostgreSQL- offers much more flexible queries. (Check some <a href="https://steemit.com/hivemind/@inertia/hivemind-queries" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">examples) <p dir="auto">I want to offer read-only public accounts to query the Hivemind database. This requires new infrastructure planning. Can't offer public accounts on the <code>master PostgreSQL instance due to obvious reasons, I need new at least one or two replica instances where people can query and benefit the power of the Hivemind. <p dir="auto">These come with additional development/maintenance/server costs. While I am happy to do that with my witness earnings, I already run a lot of dedicated servers. <p dir="auto">Didn't really do the math, but probably get into a loss if we compare the costs with witness earnings. Here is my server list for STEEM related things: <ul> <li>Two dedicated servers for witness <li>One dedicated server for Hivemind <li>One medium-sized virtual private server dPoll <li>One small-sized virtual private server for scripts (witness backup failover, etc.) <h1>TL;DR What will be delivered? <p dir="auto">A reliable, fast, public SQL service (direct connection) of the Hivemind. I expect to deliver it before 2020. The plan is exposing Hivemind's database directly to the public with a good, old PostgreSQL user. (read-only) <h1>Timeframe of the funding <p dir="auto">1 year <h1>Daily request amount of SBD <p dir="auto">12 SBD <h1>Q.A <ul> <li>What will happen when the funding window is closed? Will you shut down the service? <p dir="auto">1 year is a lot, I cannot promise anything at this time. But, worth to mention, I already served free public Hivemind node for 9 months, and I expect to keep this service is up as long as I can, financially. <ul> <li>Will you cash out the funding instantly? <p dir="auto">My plan is to power up the SBD, instantly after converting to STEEM. I will cover the server costs with fiat and don't create sell pressure on STEEM with the steem dao funds. However, this might change in upcoming months depending on the costs, my financial status, etc. <ul> <li>Are you eligible for that kind of thing? <p dir="auto">I am a software engineer with 10+ years of experience. Also, experienced with Python (the language powers Hivemind), and PostgreSQL. (My github account <a href="https://github.com/emre" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">@emre might be a good indicator about what can I do.) <ul> <li>What will be the outcome for community? <p dir="auto">This is useful mostly for software developers, data people. Applications, dapps, reports can benefit this direct SQL access. <ul> <li>Difference between SteemSQL? <p dir="auto">SteemSQL is a general blockchain data service, while Hivemind only stores a partition of the blockchain data. Mostly social part like posts, accounts, votes, relationships (follow, ignore, resteem), etc. It's also planned to store <code>communitiesdata at Hivemind. <h1>Voting for the proposal <ul> <li><p dir="auto">Vote via <a href="https://beta.steemconnect.com/sign/update-proposal-votes?proposal_ids=%5B51%5D&approve=true" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Steemconnect <li><p dir="auto">Vote via <a href="https://steemproposals.com/proposal/51" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">steemproposals.com <p dir="auto">You can view all the proposals on: <ul> <li><span><a href="https://steemproposals.com/proposals" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">https://steemproposals.com/proposals <li><span><a href="https://steemitwallet.com/proposals" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">https://steemitwallet.com/proposals <li><span><a href="https://steempeak.com/proposals" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">https://steempeak.com/proposals <p dir="auto">If you have any questions or suggestions, shoot in the comments section.