Do you plan to release HVM in 2025 to enable L1 Smart Contracts for HIVE? If not, why can’t we hire skilled developers for this task and allocate payment via DHF for them?
You are viewing a single comment's thread from:
Do you plan to release HVM in 2025 to enable L1 Smart Contracts for HIVE? If not, why can’t we hire skilled developers for this task and allocate payment via DHF for them?
We're working on L2 smart contracts, not L1 contracts, because I think L1 smart contracts offer a lot of risk and relatively little reward compared to L2 smart contracts. L2 contracts also offer more potential for scaling.
Agree, but it's mostly centralized. How we fix that problem? I think this is the most important point when people invest on L2 tokens. Am I correct?
Most L2 smart contract systems are centralized. But there's no particular reason they have to be, it's just "easier" to do so, just like its easier to write most any software in a centralized manner.
The L2 system we're designing is just as decentralized as Hive (actually, arguably it will be more decentralized, but explaining that probably needs a longer post some time in the future).
Thank you for your reply. If you have time to explain how this proposed L2 system works and how it becomes "decentralized," it would help the entire community gain a clear understanding. Additionally, we need something competitive with the so-called smart contract networks to see HIVE in the top token list, rather than its current position.
One of the most important questions for me is how this L2 layer handles deposits and withdrawals. Is it bound to a single key holder, or does it work through some form of confirmation levels, especially when withdrawing funds?
It would be better if you could explain these points in a separate article, as it would have a greater impact on us.
$WINE