As a follow-up to our recent post on the HoloFuel UI, we’re going to do a deep dive into the HoloFuel transactor. It is perhaps the most critical component in building out the HoloFuel ecosystem within the larger Holo ecosystem.
Making sure the transactor works properly, particularly when it comes to payments and hosting, is a priority for us as we progress through the Alpha Testnet.
The HoloFuel transactor is the hApp for sending and receiving HoloFuel, and similar in many respects to a Bitcoin wallet.
We’ve shown you what the UI will look like from the user’s perspective, but it’s important to remember that the UI acts as a bridge to the HoloFuel transactor, which is where the actual process of moving HoloFuel to various destinations takes place
We therefore want you to see the underlying product functions and what makes our approach to HoloFuel different from other digital currencies.
The key element that distinguishes the HoloFuel transactor from others is its agent-centric design. In other words, it is up to both the sender and receiver of HoloFuel to sign transactions confirming them.
This marks a difference from Bitcoin, Ethereum, and similar currencies, where only the sender signs the transaction. This simple distinction creates a more accountable experience, yet intuitive and forgiving, experience.
A HoloFuel transaction goes through a series of verification and signing stages. Until the recipient has committed the transaction to their source chain, it remains in a pending state.
You therefore have a window in which you can cancel the transaction if you accidentally send someone fundsor find suspicious activity on your counterparty’s source chain.
You see an advantage over blockchain-based currencies in which transactions even—accidental or fraudulent ones—are irrevocable once sent. Pending state also helps eliminate the frustrating crypto problem of sending HoloFuel to the wrong address
Unlike other currencies that are created from mining or staking, #HoloFuel is backed by (and redeemable for) the useful work of hosting by people like you from across the globe.
Again, with our agent-centric approach, if the agent who is being asked to send funds declines to do so, they can reject the request. #Easy
In addition, the request function can be integrated with logging #hApps to handle invoicing.
This makes it much simpler to build an e-commerce operation fully within #Holochain Holochain without the need for third-party invoicing or other data collection/storage services—it can be done simply by integrating HoloFuel.