The Foundation will utilize submitted questions in upcoming communications. While this blog serves as an educational resource, we encourage the community to dive into HIP 70, have discussions with other Helium Community members in the dedicated HIP 70 Discord channel, and post questions in the questions form here and linked at the bottom of this blog. This blog explains PoC and Data Transfer Accounting under the proposed architecture and - as a result of moving these two actions to Oracles - why the core developers propose Solana as the new Layer 1 to support the Helium Network.įor context, Oracles are entities that connect blockchains to external systems, thereby enabling smart contracts to execute based upon inputs and outputs from existing real-world servers or devices.įurthermore, this blog explains how the change impacts the entire ecosystem - from users to builders to manufacturers. Such a move would bring significant economies of scale through the vast range of composable Solana developer tools, features, and applications. To achieve this goal, the core developer team proposes moving Proof-of-Coverage (“PoC”) and Data Transfer Accounting to Oracles, which simplifies the system architecture and allows for the selection of a more scalable Layer 1 (“L1”) - specifically, Solana. HIP 70: Helium Core Team Proposes to Migrate to SolanaĪnnounced today, HIP 70 is a proposal by the Helium core developer team to improve the operational efficiency of the Helium blockchain significantly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |