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.
You are viewing a single comment's thread from:
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.
Cool Thanks. So, HAF is a supercharged and easy-to-use hivemind and also the possible foundation to future smart contract implementations I guess?
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 up hivemind into modular components (aka "modular hivemind"), allowing a hivemind operator to select which APIs they wanted to support. But performance limitations of hivemind led us to rethinking the way data is injected and processed in HAF.
So functionally, HAF has two major differences from hivemind: 1) it has a fork manager which enables apps to roll back actions performed when a block is processed, allowing apps to safely process head blocks as soon as they are generated and 2) it gets data from hived via a push model vs a pull model which lowers the CPU loading on hived, increases data throughput, and lowers latency time to process transaction data.
One of our next steps will be to port hivemind to turn it into a HAF app. This will allow hivemind to sync faster and it will also allow it to safely process head blocks and more quickly react to new blockchain transactions.
Cool cool. Just one more clarification. We all know the head block is by far the most unreliable block out there right? With HAF, we DApp developers don't need to wait for say 30-40 secs before deciding if a particular action is part of the block_log? Or would you still suggest that we add a delay of 5-10 blocks if it's a crucial transaction that involves a financial transfer to a DApp account?
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 signal that it is planning to make the transfer, but wait for the block to be irreversible before making the transfer.
Thank you for clarifying all my doubts. Looking forward to the release of HAF.