As Libra Core moves toward the main network step by step, its development roadmap has also been updated.
Editor’s note: This article comes from the strategic cooperation blockchain media “Odaily Planet Daily” (Public ID: o-daily, < a href="https://download.odaily.com/">APP Download)
This article is from developers.libra.org, author: Libra Association
Star Daily Translator | Moni
Since the release of the Libra Digital Money White Paper in June this year, despite the concerns of many governments and regulators, the response from the developer community has been exciting. So far, developers have released multiple blockchain browsers, such as Libranaut, Libraview, Librabrowser, and Libexplorer; others have integrated the Libra test network into their wallets, such as ZenGo. In addition, we have seen other blockchain projects integrate the Move programming language into their own systems, such as Solana.
Libra Digital Wallet Development Company Calibra has been working on developing Libra Core on GitHub, and the team has released two new guides: a Move app for running locally, and a show for how to run it yourself. The internet. A number of topics were discussed at the Libra Discourse forum, including transaction scripting, client development, and a variety of other Libra activities.
Stable technology developments and open and transparent conversations are two key elements of developer interest in the Libra project. As Libra Core moves toward the main network step by step, its development roadmap also has a series of updates, belowLet us take a look together.
Top: Libra main network milestone
Beyond Test Network
The main purpose of Libra’s launch of the test network is to make it easier for development teams to troubleshoot, diagnose, and resolve software edge issues to quickly improve Libra Core. The test network has a range of Libra networking features and provides early access to developers.
After the launch of the test network, Facebook has been hoping to successfully launch the Libra main network, so it chose a way to track the success of the project: let different partners manage how many nodes they have deployed. The ultimate goal of the Libra main network is to have all partners deploy nodes on the network, each running in a hybrid mode that combines on-premise and cloud-hosted infrastructure. Facebook believes that this diverse infrastructure will provide greater flexibility for Libra networks.
In the first milestone, the Lirba Association is expected to invite five partners to deploy the full node on the network and will launch the Libra main network in the fourth milestone phase. The Libra Association expects 100 partners to run Libra node.
GitHub update
To better help partners track development progress, Facebook added Kanban Kanban (Visual Task Board) with all major engineering priorities, allowing partners to track the progress of the roadmap on GitHub.
Like many open source projects, contributors must contribute to the project in accordance with the signed Contributor License Agreement (CLA), and Facebook will review some service options to streamline the existing manual contributor license agreement approval process. .
The current development process enforces a high level of code quality, so Facebook chose the code testing tool Homu, an open source robot that works with Libra’s Continuous Integration/Continuous Deployment (CI / CD) system to Make sure the test work is always passed. Libra’s test robot @bors-libra will continuously verify that the test passes between the PR version and other PR-merged versions, and the partner can see it in the PR version.This is the command to issue the tag to the robot, and then the execution will start. If you want to constantly test large “green” projects, you usually need to use robots to manage the integration work, and by performing branch protection, you will add another layer of security to the Libra project, but if you want to make changes to the protected branch, then smart Executed by the robot.
The Libra engineering team has begun publishing design notes on GitHub. If the sharing partner is looking for a way to participate, or if you want to track a Libra-specific feature and provide feedback, you can browse the Libra project’s problem page on GitHub.
Libra is working hard to provide clearer, richer solutions to help partners stay on the project for a long time. In addition, by releasing project roadmaps in a timely manner and updating the status of high-priority jobs, you can provide guidance to your partners and deepen your understanding of Libra Core features.
Sprint Development
Since the Libra project started, its engineering team spent 60 days sprinting to complete Libra Core’s planning and development work, with each sprint job having a prioritized set of work. For Roadmap #1, the Libra team is more focused on security and reliability, and is committed to integrating more partners into the upcoming Libra main network.
Roadmap #1 Current Progress
The Libra team will continue to work on all of the priority features and make good progress on features like “full node.” In addition, Libra is working to define a specification for node redistribution that will take effect before the Libra protocol definition is finalized.
Libra Core
1, addressing/interoperation
Interoperability between multiple wallets is key to the success of the Libra network, and the Libra team is working to develop a simple solution to support sending funds to sub-accounts (or sending funds from sub-accounts).
2, full node
The Libra blockchain will consist of a single node type that supports different configurations, which will allow the node to act as a full node for storing the full history of certifiers or non-authenticated nodes. The Libra development team is also working to make it easier for certifiers to upgrade all nodes and vice versa.
3, Libra Protocol Definition
The Libra team is working hard to define application programming interfaces (APIs), wire specifications, addressing/interoperability, and other protocol dependencies.
4, certifier reconfiguration
Verifiers collection (validator sEt) contains the unique identifier of the authenticator in the system. As time passes, the certifier collection needs to support changes. From the perspective of the blockchain system, changing the set of verifiers affects each component. Consensus requires revalidation of blocks, network reconfiguration, storage needs to keep account information (LedgerInfo), and clients also need a solution to verify read data during certifier changes.
5, Waypoints
Waypoint will provide customers with an external source of information about blockchain history.
6, TCB (Trusted Computing Library)
The Trusted Computing Base is critical because it defines a subset of components for system security and stability, minimizing dependencies on critical hardware and software components, and helping Avoid accidental errors and malicious attacks.
7, serialization
The Libra team is looking to achieve explicit serialization to verify that RawTransactions are shared between human nodes.
Move
1, Events
-
Explore the design that represents Events in Move;
-
Providing an application interface for stable Events for developers;
-
Provides relevant developers with examples of how to record Events on the chain.
2, collection/generic
Implement the vector and explore other supported collection types.
3. The Libra team posted #597 on Github, which unpacked the management of the certifier collection, and there are other things in the validation program to support this operation, which is part of the assurance of correctness.
Libra Pre-Mainnet
As the Libra project moves toward the main network milestone, it is necessary to keep the test network running while allowing more nodes to come online. To do this, the Libra team created a staging primary network environment called Pre-Mainnet. At this stage, only partner nodes can access Pre-Mainnet and allow them to connect to each other. A few partners have deployed nodes and can support communication with each other. Libra expects more partners to come online soon, and to ensure that the Libra network meets stringent performance benchmarks and overall system stability requirements before officially opening up to the new.
Let’s wait and see.