Libra Association officially released the first road map, after four milestones will start the main network

The Libra Association has released its first roadmap detailing the milestones (currently four) that the Calibra team plans to launch before the Libra network.

Balance-335980_1280

Image source: Pixabay

For the first milestone, the Libra Association wants to deploy five full nodes (full nodes) on the network. The Libra Association expects to start the Libra main network when it reaches its fourth milestone, with 100 partners running Libra nodes.

According to the Libra Association, "One way we use to track project success is how many deployed nodes are managed by different partners." The Libra Association points out that each Libra node will "run in a hybrid local and cloud hosting "Infrastructure," added, "The wider diversity of infrastructure will provide greater flexibility for the Libra network."

In preparation for the release of mainnet, the Libra Association created an environment called Pre-Mainnnet. Pre-Mainnet is a test environment available only to a few Libra partners who have deployed a full Libra node. This environment will enable partner nodes to communicate with each other and test the stability of the Libra network.

z+ObigelBbLtAAAAABJRU5ErkJggg==

The following is the details of the Libra Association :

Since the official announcement of the Libra project in June, the response from the developer community has been exciting. Community developers have released several blockchain browsers (libranaut, libraview, librabrowser, and libexplorer) and integrated the Libra test network into their wallets (ZenGo, including a large PR for Libra Core). We also saw other blockchain projects integrating the Move programming language into their systems (Solana). Calibra continues to develop Libra Core on GitHub . The Calibra team also released two new guides: one to run the Move app locally and the other to show how to run your own Libra network. The Libra Discourse forum is active in discussions about trading scripts, client development and interest in Libra activities.

Stable technological advances and open and transparent dialogue are key to developing this growing interest in the project. As Libra Core moves towards the main web, we will check out the latest developments in the roadmap in this blog.

After testing the network (Testnet)

The release of Testnet allows teams to quickly improve Libra Core by simply troubleshooting, diagnosing and resolving software edge conditions. Testnet demonstrates Libra networking capabilities and provides early access to developers.

Following Testnet, we hope that the Libra main network (Mainnet) will be released successfully. One way we use to track project success is how many deployed nodes are managed by different partners.

The ultimate goal of Mainnet is to have all partners deploy nodes on the network. Each node will run on a local and cloud-hosted infrastructure. We believe that the wider diversity of infrastructure will provide greater flexibility for the Libra network.

GitHub update

To help you better track your development progress, we have added a Kanban (Visual Task Board) that includes all major project priorities. Here you can track the progress of the roadmap.

As with many open source projects, the contributed code must follow the signed Contributor License Agreement (CLA). We are reviewing some options to streamline the existing manual CLA approval process.

The current development process mandates a high level of code quality. One tool we use is homu . Homu is an open source robot that works with our Continuous Integration/Continuous Deployment (CI/CD) system to ensure that testing always passes. Our homu robot @bors-libra works by continuously verifying whether the test passes between PR revisions and other PRs. You can see the commands posted on the PRs that mark the bot and indicate that it works. Using robots to manage merges is common in large projects that want to keep test results "green." This change adds an extra layer of security to the project by enforcing branch protection, so changes to the protected branch can only be performed by the robot.

The engineering team has begun publishing their design notes on GitHub. If you are looking for ways to participate, or want to track the progress of a particular feature and give feedback, you can browse the GitHub question page.

We are working hard to provide a clearer and richer way to help you get involved. We hope to publish this blog post and future roadmaps, update high-level priority status, and share design notes to give you guidance and insight into upcoming Libra Core features.

Sprint based development

From the beginning of the project, the team used a 60-day sprint to help guide the planning and development of Libra Core. Each sprint has a set of features organized by priority. For Roadmap #1, the team focused on security and reliability and is committed to integrating more partners into the upcoming Libra main network.

Libra's core goal in roadmap#1 is to focus on security and reliability and to integrate our first partners into the Libra network.

Roadmap# 1

Current progress

We are continuing to design all of the priority features. We are making good progress in implementing functions such as full nodes. The node reconfiguration specification we are defining will work before the Libra protocol definition is completed.

Libra Core

Addressing/interaction

Interoperability between multiple wallets is key to the success of the Libra network. The team is working on a simple solution to support sending data to/from subaccounts.

Full node (full node )

The Libra blockchain will consist of a single node type that can be configured differently. This will allow the node to act as a validator or a non-authentication node, which stores the complete history (full node). We will also allow the entire node to be easily upgraded to the validator and vice versa.

Libra protocol definition

The team is defining APIs, connection specifications, addressing/interoperability, and other protocol dependencies.

Authenticator reconfiguration

The validator set contains the unique identifier of the validator in the system. As time passes, the validator set needs to support changes. From the perspective of the blockchain system, changing the set of validators affects each component. The consensus needs to revalidate the block, the network needs to be reconfigured, the store needs to save a LedgerInfo, and the client needs a way to verify the read data across the validator.

Waypoints

Waypoints will provide clients with an external source of information about blockchain history.

TCB (Trusted Computing Foundation)

The Trusted Computing Foundation (TCB) defines a subset of components that are critical to system security and stability. Minimizing the hardware and software dependencies of critical components helps avoid unintentional errors and malicious attacks.

Serialization

The team wanted to implement deterministic serialization to share the original transaction between the verifier nodes. For more discussion on this topic, see #454.

Move language

·Events

  1. Browse the design that represents the event in Move.
  2. Provide developers with a stable event API.
  3. Provides an example of how developers can record events that occur on the chain.

·Collection/generic

Implemented the vector to support and browsed other collection types.

· We found #597 , which relieved the blocking of the validator set management. There is additional work in the validator and correctness guarantee to support this.

Libra Pre-Mainnet

As the project moves toward the Mainnet milestone, it is necessary to bring more nodes online while maintaining the testnet operation. To support this work, we created a staging environment, which we call Pre-mainnet. Currently, only partner nodes can access Pre-Mainnet to allow them to connect to each other. A few partners have deployed their nodes and have them communicate with each other. We expect more partners to be online soon. We want to ensure that Libra networks meet stringent performance benchmarks and overall system stability before opening up. Please continue to pay attention.

Come join our forum

If you have any other questions or suggestions about this roadmap, please leave a message here .