If this is about blocktrades.us, please submit a support request from our web site and one of our support people will assist you.

HAF should require less RAM than an existing full node, because there will be no need to run an account history node (this will be replaced by running hafah on your HAF server).

You would still want to wait till a block becomes irreversible before performing an action based on it that can't easily be canceled (e.g. a blockchain transfer of funds). So in such cases, your app might

HAF is a general-purpose programming framework, whereas hivemind is focused on social media data. Problems we encountered with hivemind inspired the creation of HAF. Originally, we were planning to break

All transactions go to the mainnet, not HAF. HAF will see them and react to them once the transactions get included into blocks and hived pushes the block data to the HAF nodes.

We do get requests for specific functionality every now and then (e.g. the ability to change keys more than once per hour was a request by @engrave IIRC), but such changes are usually easy to make and

Yes, we use the very ASUS board you showed (and a couple other similar ones by MSI and Cablecc) that allow you to use one PCI 16x slot in "bifurcated mode" to connect 4 2TB gen4 nvme drives,

We haven't tested it here because we're generally trying to test a max performance setup to see where the potential performance bottlenecks are, but a HAF setup like that should be fine.

I think setting up a public HAF server is problematic, because of the issues around providing write access to schemas in your HAF database (at the very least, you'd need to figure out how to set disk storage

The server spec is for a general purpose HAF node that can store all the blockchain data. In a couple of weeks we'll have support for operations filtering (i.e. to filter for only the operations your app

Yes, you would be able to create your own API calls, so you could create a single call that met your needs. If your app is already dependent on a lot of hivemind-based API calls, one option would be to

At some point it would probably make sense to look into changing this into a HAF app. That would have eliminated all the issues you had with account history fetches and batching, because you would have

It is very different from HiveSQL. For example, HiveSQL doesn't have a fork manager.

Yes, it will make it easier to create apps, and they will be faster and have fewer bugs.

It's simpler than it probably sounds here. If you've ever written an event-driven program, the programming model for the backend should be fairly familiar. Your app makes a SQL call to get notified whenever

The airdrop will be for a future smart contract processor that will be built on top of HAF (we don't have a name for the smart contract processor yet).

No, HAF is quite different from a smart contract on ethereum, although both allow you to create apps on a blockchain. HAF is a general-purpose 2nd layer programming platform that offers much more flexibility

One of the most important things HAF does is making forking "invisible" to applications. If you want to make a reliable app that can safely process blocks very soon after they are produced, using

As far I understand it works technically like a buffer? It provides buffering of a sort, because it removes loading from the hived nodes themselves, but that's only aspect of the design benefits of using

Thanks, and please feel free to create issues in gitlab when/if you find any places where we can make improvements.