This article comes fromdevelopers.libra.org,author:Libra Association

Translator | Moni

This article comes from

,author:

Translator | Moni

Libra digital wallet development company Calibra has been working on developing Libra Core on GitHub, and the team has released two new guides: one for running the Move app locally and one showing how to run your own network. Many topics are discussed on the Libra Discourse forum, including transaction scripts, client development, and various other Libra activities.

Steady technical development progress and open and transparent dialogue are two key elements of developers' growing interest in the Libra project. As Libra Core moves towards the main network step by step, its development roadmap has also undergone a series of updates, let us take a look below.

Above: Libra Mainnet Milestones

secondary title

The main purpose of Libra launching the test network is to make it easier for the development team to troubleshoot, diagnose and solve software edge problems, so as to quickly improve Libra Core. The testnet features a range of Libra network features and also offers developers early access.

Following the launch of the test network, Facebook has been hoping to successfully launch the Libra main network, so it has chosen a method to track the success of the project: let different partners manage how many nodes they have deployed. The ultimate goal of the Libra mainnet is for all partners to deploy nodes on the network, each of which will operate in a hybrid model combining on-premises and cloud-hosted infrastructure. Facebook believes that this diversity of infrastructure will provide greater flexibility for the Libra network.

In the first milestone stage, the Lirba Association is expected to invite 5 partners to deploy full nodes on the network, and will launch the Libra mainnet in the fourth milestone stage. The Libra Association expects 100 partners to run Libra nodes by then.

secondary title

GitHub update

In order to better help partners track development progress, Facebook has added a Kanban Kanban (visual task board) that contains all major engineering priorities, allowing partners to track the development progress of the roadmap on GitHub.

The current development process enforces a high level of code quality, so Facebook opted for code testing tool Homu, an open-source robot that works with Libra's continuous integration/continuous deployment (CI/CD) system to ensure testing works always pass. Libra's test robot @bors-libra will continuously verify whether the test passes between the PR version and other PR merged versions. Partners can see that the command to mark the robot is issued in the PR version, and then the execution work will start. If you want to constantly test "green" large projects, you usually need to use robots to manage the integration work. In addition, by implementing branch protection, you will also add another layer of security to the Libra project, but if you want to make changes to protected branches, it is smart performed by robots.

The Libra engineering team has begun publishing design notes on GitHub, and co-tenants looking for ways to get involved, or want to track and provide feedback on a Libra-specific feature, can browse the Libra project's issues page on GitHub.

secondary title

Sprint development

secondary title

Libra Core

Roadmap #1 Current Progress

The Libra team will continue to complete design work on all priority features, with good progress on features such as "full nodes". In addition, Libra is also working to define a specification for node redistribution, which will take effect before the Libra protocol definition is finalized.

secondary title

1. Addressing/interoperability

Interoperability between multiple wallets is key to the success of the Libra network, and the Libra team is working hard to develop an easy solution to support sending funds to (and from) subaccounts.

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 storing the full history of validators or non-validating nodes. The Libra development team is also working on making it easier for validators to upgrade full nodes and vice versa.

3. Libra protocol definition

5、Waypoints

The Libra team is working hard to define the application programming interface (API), Wire specification, addressing/interoperability, and other protocol dependencies.

4. Validator reconfiguration

The validator set (validator set) contains the unique identifiers of active validators in the system. The set of validators needs to support changes over time. From a blockchain system perspective, changing the set of validators affects every component. Consensus needs to re-verify blocks, the network needs to be reconfigured, storage needs to keep saving ledger information (LedgerInfo), and the client also needs a solution to verify the read data during validator changes.

Waypoint will provide customers with an external source of information about the history of the blockchain.

Trusted Computing Base (Trusted Computing Base) is critical because it defines a subset of components for system security and stability, minimizes dependencies on critical hardware components and software components, and helps avoid surprises Errors and Malicious Attacks.

Move

1、Events

• 7. Serialization

• The Libra team is looking to implement explicit serialization aimed at sharing RawTransactions between validator nodes.

• secondary title

Explore the design representing Events in Move;

Provide a stable Events API for developers;

2. Collections/generics

Libra Pre-Mainnet

Implement vectors and explore other supported collection types.

3. The Libra team released #597 on Github, which unseals the management of the validator set. There are other works in the validator to support this operation, which is also part of ensuring correctness.