At a glance
In Roadmap # 2, we will focus on three things: 1) provide the mainnet function in order of priority; 2) define the launch criteria from Libra pre-mainnet to mainnet 3) Educate and embrace the Libra community so that they can become valuable contributors to the Libra project.
- Mainnet function works
- Libra pre-mainnet
- Community support and open work
Roadmap 1 review
Roadmap # 1 includes a discussion of design changes in Libra Core, from how we deploy Libra pre-mainnet to the Move language script release. Thankfully, we are still completing the completeness of the functionality as planned, and the Libra community is growing fast!
- Wanxiang Innovation Energy City Wang Yunwei: Building a smart city to test the token economy
- Jianan will be listed, and these 20 A-share “mining concept stocks” will know in advance?
- Technical Guide | Teach you to discuss Wasm contract development: (C++)
- Facebook Libra person in charge hearing testimony: will not launch (full text)
- Trojan attacks, 5,000 computers reduced to mining "black labor"
- Is the Ethereum blockchain full? V God commented like this
· Libra main network function work: In order to make the main network function complete, we have completed the design in all the main functions, and all teams have entered the execution mode.
· Libra pre-mainnet deployment: The work of the pre-mainnet has been changed to accommodate changes in the membership list and extended testing time.
Community support: Interest in the Libra project has turned into interest in its implementation and collaborative design.
- We regularly talk to members of the Libra Association to share progress and answer related questions.
- The first development contributions to the Libra Developer Blog came from members of the Libra Association.
- We attended conferences like SF Blockchain Week and discussed topics such as identity and security / privacy / economics.
- We are using GitHub Kanban to manage the project and provide full transparency.
Roadmap # 2
The goal of Roadmap # 2 is to implement our roadmap, define the release requirements for version 1, modify our pre-mainnet plan for non-tech members, and increase community participation.
Work on mainnet functions
We have completed the relevant design work and developed a thorough, bottom-up timeline for all features. We are now working on a complete Libra protocol architecture document and finalizing our external API based on community input. Looking ahead, we are starting to identify some of the work that made the Libra project hope to attract the community.
Below is a summary of our progress. Some new projects have been added to understand what the team is currently doing. For a view of the project management hierarchy, see our GitHub kanban and recently released updates.
List of highest priority features and progress status
Now we have eight validator nodes deployed to the Libra pre-mainnet!
New pre-mainnet strategy for non-technical Libra members
We created a new milestone for non-technical member validator node deployment. These members may not have an internal technical team. The Libra Association, partners, and the Libra protocol team are developing a strategy to assist non-technical personnel in the deployment after the software has completed its functions. Such members need to start preparing how to deploy their validator nodes by hiring technical support or leveraging a third party to run their validator nodes.
Looking ahead, we will focus on inviting new organizations to join the Libra Association, maintaining the growth of the network, and continuing to move towards a self-service model.
Libra validator node operator community
Our initial members agreed with us that the Libra network needs to be a self-service model to scale to 100 members. Existing members have participated in it, participated in the first Libra Core summit of the node operation group, and chaired a group discussion. Bison Trails also wrote a Libra blog about running validator nodes. Our initial member team is strong and we have been growing the community (including SRE and software engineers).
We have created a Libra Slack workspace that is open to all members and has multiple discussion channels to help the community grow. We have also launched a member portal that will feature a slack bot to support members, integrate with GitHub, Discourse, and CLA processes, and allow members to access documents, configurations, and more.
We also strive to figure out the software release process, continuous integration / deployment, and topics such as which software branch members should be used.
Mainnet exit criteria and preparation for startup
As we approach the release, the association will need to determine metrics to enable members to assess whether the Libra blockchain is ready for release (the public release of the Libra network will be determined by a vote of the association's board). We need to measure success criteria and determine dependencies. We have already started these discussions. In Roadmap # 2, we will begin to define these indicators (technical indicators and non-technical indicators). First, we will start with the Libra protocol.
· Technical indicators: Correlation with Libra protocol software (network, developer infrastructure, storage, etc.), Libra protocol and wallet, testing real funds, scale testing and other related indicators.
Non-technical indicators: indicators related to Libra Association, reserves, other wallets, market entry indicators, etc.
Community support and open work
Having achieved the goals of Roadmap # 1, we have expanded what we are doing to really increase quality, scale, and engagement in the Libra community. Here are the plans we added.
We have worked completely publicly, published our plan (including this document), and had a shift engineer on support to support our testnet, forums, and GitHub issues. But all these things are passive and share what we have done. We have also streamlined the CLA process for association members and external contributors (individuals and companies) to enable them to contribute their strength.
For Roadmap # 2, we want to join a proactive plan and start engaging the community on how to make decisions and structure things. To this end, we are writing recommendations for the formal Libra Technical Working Group (for example, discussions on interoperability and common identification standards).
Getting input from the community will also create better products. When things happen off-chain and not within the Libra protocol, we have a very fertile ground for sowing the seeds of community growth without slowing our development towards the mainnet.
We are working hard to build communities directly, rather than involve them. It's not entirely clear at this time, but there are two main audiences: association members and non-member customer developers (application level and smart contract level).
For Association members, we held the first Libra Core Summit in mid-November 2019. The goals of this work include creating a community of technical contact points for association members, communicating to our members how the Libra network works technically, and brainstorming what working groups are needed.
For client developers, we are actively involved in getting many product requirements about developer infrastructure and APIs directly from the community. So far, we have focused on creating new things and facing more internally. This marks a shift towards the most active solicitation and research to maximize the development of the Libra community.