Ethereum: Why are the hips not kept in the block chain?
When it comes to administering assets and transactions on the Ethereum network, you often wonder why the hips are not stored directly in the block chain. In this article, we will explore the reasons behind this design decision, and how to include new balances together with each transaction can be more efficient.
Current approach: A brief description
Currently, when a user performs a transaction in the Ethereum network, the following happens:
- The sender’s account is consulted to recover your balance.
- The sender may send ETER (ETH) or other assets to the recipient.
- Once the transaction is processed, the sender’s new balance is updated.
While this approach has its advantages, it also has some inconvenience. Here are some reasons why the hips are not kept directly in the block chain:
* Scalability: As the Ethereum network increases in terms of the number of transactions and users, storage balances directly in each block can lead to an increase in times and transaction processing costs.
* Security: If an attacker has manipulated a user’s account balance, he could achieve control over his assets. When you store hips in the block chain, it becomes much more difficult for an attacker to exploit this vulnerability.
* Lack of efficiency: As mentioned above, crossing the complete block chain to determine the balance of a user can take long and expensive.
Alternative: Include new hips together with each transaction
Now, imagine a scenario in which the hips are stored directly in each block. This is known as “block -based accounting”.
This is what to happen:
- When a transaction is processed, the sender’s new balance (including transactions or pendent rates) is processed and includes in the block.
- The updated balance is transmitted to all nodes in the network.
This approach has more advantages:
* Improved scalability: You do not have to consult the hip block chain, transaction processing times can be significantly reduced.
* Improved security: With block -based accounting, it becomes much more difficult for attackers to handle a user’s balance without affecting other transactions in the same block.
* Effective use of network resources:
When storing hips directly in each block, the network can preserve the calculation resources and reduce the amount of data to be processed.
Conclusion
While storing hips in the block chain may seem like an effective solution, it comes with some inconvenience. In this article, I explored why the hips are not stored directly in the Ethereum network. However, given alternative approaches, such as block -based accounting, it is clear that there are ways to improve scalability, safety and efficiency.
As the Ethereum network continues to evolve, it is essential for developers and users due to the latest developments and possible solutions. Who knows? Maybe one day, we will see a future in which the hips are stored directly in each block!
related items
- “Ethereum 2.0: What do you need to know”
- “How to use smart contracts from Ethereum”
- “The benefits of decentralized finance (def) in the Ethereum network”