Excellent witness update, @c0ff33a! Your commitment to maintaining Hive infrastructure is particularly interesting to me because I’m currently working on integrating HIVE and HBD into the BlockGators Army Advertising Network.
Our ecosystem includes BGA Poker, BGA SportsCenter, BGA Exchange, and our advertising network. We’re building payment infrastructure that will allow members to use HIVE and HBD for purchases, account funding, and services across the network, alongside our existing BGAT utility token on the Waves blockchain.
What caught my attention was your full API node running the HAF API Stack. Having access to reliable blockchain data, account histories, transfers, and transaction verification could be extremely valuable for the payment infrastructure we’re developing.
I’m particularly interested in connecting our PHP-based payment services to Hive API nodes so we can detect incoming HIVE/HBD transfers, verify payments, reconcile transactions, and credit the correct member accounts automatically.
Your explanation of redundancy, witness infrastructure, and Tailscale also gives me ideas about building a more reliable backend without immediately investing in the resources required to operate a full Hive API node.
I have a technical question: Would you recommend using your public API endpoint as one of the data sources for a commercial application processing HIVE/HBD payments, alongside other public Hive nodes for redundancy?
I’m also interested in learning more about running Hive infrastructure as our network expands.
Thank you for supporting Hive and sharing the technical details behind your operation. Posts like this are valuable to developers building real-world utility around the blockchain.
Thank you for the reply and feedback, you are more then welcome to make use of https://api.c0ff33a.uk as a Hive full node for your projects, you can view all the public full nodes and availability at https://beacon.peakd.com/
I do my best to keep my own full node up as much as possible, obviously during updates to new software versions there will be downtime - but at the moment since a full rebuild of 1.28.8 it has been rock solid reliable - I check https://beacon.peakd.com/ multiple times a day myself just to make sure it is in good health.
Generally speaking whatever you are building should have a list of four or five Hive API nodes so if one is slow or does not respond it can failover to the next - that gives you the best chance of always being always to serve your content.
If you wish to learn more about running full hive nodes or just basic nodes to pull blocks from I can point you in the right direction on both how to do that and the kind of server hardware you would need to do it.