What Is Hathor (HTR)?
The primary problem for creating digital money is how to prevent double spending. As the money is digital, and copies can be made ad nauseam, what can prevent counterfeiting? What would prevent users from sending copies of the same money to two (or more) people? That is precisely the problem solved by Bitcoin and its underlying Blockchain technology. The current solution behind fiat money is having a single issuer, a central bank — then trusting the financial institutions and regulators.
Hathor A block is like a regular transaction with no inputs which confirms exactly one previous block and at least two transactions. There may be any number of outputs provided that they sum up to the number of newly generated tokens. The blocks are ordered according to their timestamp.
Hathor Storage Key Points
|Circulating Supply||228,750,840.00 HTR|
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
This work introduces Hathor’s architecture, which may be a solution to scaling, centralization, and spam issues on the Blockchain architecture. Hathor has both transactions and blocks connected forming a Directed Acyclic Graph (DAG). While transactions are only connected to other transactions, blocks are connected to both blocks and transactions forming a Blockchain inside the DAG.
In Figure 1, the blocks are represented by red boxes, while transactions are represented by ovals. Both transactions and blocks have to solve a proof-of work according to their weight. Blocks and transactions will generically be referred as vertices in this paper.
There is a trade-off in the difficulty of mining new transactions. On the one hand, the higher the weight, the harder it is to generate new transactions, preventing spammers and increasing the confirmation of previous vertices. But, on the other hand, it is worse for micro transactions, and it is harder and slower for IoT and mobile devices to generate new transactions. An alternative is that IoT and mobile devices may only sign their transactions and send them to another device that will solve their proof-of-work and propagate it into the network.
Hathor In the future, the weight of transactions may even be dynamic, increasing when a spam attack is in course and reducing when it is gone. A transaction’s weight depends only on the transaction’s size (in bytes) and on the total amount being moved. The idea here is to allow small amounts to be easily moved, while big amounts will take longer to the moved.
This allows micro transaction to quickly get into the network. Regarding the
transaction’s size, requiring more work for larger transactions makes sense because it prevents abuses, such as a denial-of service attack using enormous transactions and consuming a lot of bandwidth and disk space.
When two or more transactions spend the same output, Hathor say they are conflicting transactions. In this case, at most one of them will be executed while all others will be voided. The executed transaction is the one with the highest accumulated weight, i.e., the one most verified by other transactions. In case of tie, all conflicting transactions will be voided. It is easier to notice that all conflicting transactions have the same outgoing neighbors in the DAG of funds.
When two transactions have exactly the same inputs and outputs, but different hashes, Hathor say they are twin transactions. This is a special case of conflicting transactions because the funds are going from the same origins to the same destinations. All conflicting transactions but twin transactions are double spending attempts.
This timestamp field must be in UTC time to prevent timezone issues. The digital signature is used to ensure that only the owners may spend their tokens. It will be calculated signing the transaction’s input and output only. This allows the transaction to be signed in one device and to be sent to another device that will choose which transaction will be confirmed and will solve the proof-of-work.
Hathor Services of solving proof-of-work may also be offered by companies. They give their customers a wallet address and they send the payment inside of the transaction itself. This allows IoT devices to save energy, delegating the task of solving the proof-of-work.