Meetup Review | FISCO BCOS v3.0 FAQ

Recently, the community organized a special online Meetup to share the development route and development and deployment method of v3.0 in 2022. The discussion in the live broadcast room was very lively. We sorted out some of the issues that developers are more concerned about, and organized them into this common question and answer about v3.0 for your reference.

Q : What is the current performance of v3.0?
A : In order to improve system performance and deal with the problem of massive data uploading to the chain, in terms of system architecture, v3.0 divides the blockchain system into microservice modules such as network, computing, storage, scheduling, etc. Each microservice can be independently deployed, Expansion and fault tolerance, the application can meet the network and performance requirements of the business by adjusting the physical resources of microservices, and realize the horizontal expansion of the blockchain system.
At present, v3.0 is still in the rc stage. Judging from the current stress test results, the overall performance has exceeded v2.x. In the subsequent versions of v3.0, we will continue to verify and optimize v3.0 according to actual applications. Please We will wait and see.

Q : How to choose between v2.0 and v3.0?
A : FISCO BCOS has successfully supported more than 200 benchmark applications in cross-border, government affairs, finance, social governance, agricultural product traceability, copyright protection and other application fields. v3.0 is currently in the rc stage, two rc versions have been released, and in continuous iteration, the LTS version is expected to be released around June, when the v3.0 LTS version can be used in the production environment.

Q : Have you considered converting the EBM layer into a model similar to Docker? Smart contracts can be written in existing languages.
A : We have considered this. At present, most developers in the community are accustomed to using Solidity to write contracts, so we will continue to support the use of Solidity to write contracts. The mode you mentioned is also in our future exploration plan.

Q : Is the Gas in the alliance chain useful? Can it be removed?
A : Gas in the alliance chain is mainly used to prevent malicious attacks, so as to avoid malicious transaction execution time being too long and dragging down the node, so it cannot be removed.

Q : If the chain IDs are both Chain0 and two groups Group0 and Group1 are deployed, do they share one chain? Does the data exist together?
A : Their chains are shared, and data is stored separately. In v3.0 and v2.0, the shape of the Group is different. In v2.0, a single process supports multiple groups, and the multi-thread dimension supports groups. The dynamic group of v3.0 is that the nodes corresponding to each group are It is a single process form.

Q : Is there a Docker image for Arm?
A : I understand that the Docker image itself supports multiple platforms, so it is also possible on Arm. In the future, we will plan to provide the binary of the Arm version of FISCO BCOS, and then support the construction of the Pro/Air version of FISCO BCOS in the Arm environment.

Q : What components are mainly shared by the Pro version blockchain nodes?
A : The Pro version blockchain nodes share a network part. As we just demonstrated, we will build an RPC cluster and a Gateway cluster. These parts are shared; if you don’t want to share an RPC cluster or a Gateway cluster, you can build a separate chain. Or the blockchain nodes are connected to the services of different RPC clusters or Gateway clusters.

Q : How is the data migrated from v2.0 to v3.0?
A : There are some differences between v2.0 and v3.0. It is recommended to keep the v2.0 chain in a read-only state, adapt the new business to the v3.0 chain, let the new business run on v3.0, or put the v2 All transactions corresponding to .0 are replayed to the v3.0 chain.

Q : Does v3.0 no longer use DAG?
A : v3.0 still supports DAG, and supports more DAG dimensions. Cpp/Solidity/Liquid contract languages all support DAG. In addition, the v2.0 DAG requires users to actively analyze conflict variables and find parallel conflict domains; v3.0 implements an automatic parallel conflict domain analysis function at the SDK layer, which can automatically analyze conflict variables and automatically enable parallelism at the bottom layer. .

Q : How to learn FISCO BCOS in depth?
A : You can read the FISCO BCOS technical documents, or start practical operations according to the technical documents, and you can also follow the official account [FISCO BCOS Open Source Community]. There are hundreds of development tutorials that divide blockchain learning into three stages: introductory, advanced and professional. , which facilitates step-by-step learning.

Q : When I first learned about FISCO BCOS, I wanted to know which ones are open source and which ones are not. Is there any boundary problem?
A : All content of FISCO BCOS is open source. If you have any questions about FISCO BCOS, you can submit it in the form of an issue on Github, and FISCO BCOS developers will answer it through an issue on Github. In addition, FISCO BCOS also has an official technical exchange group. You can add a small assistant micro-signal FISCOBCOS010 to the technical exchange group, and you can exchange technical questions about FISCO BCOS in the group.

Q : After the v3.0Air version upgrades the Java-SDK to 3.0.0-rc2, when the Springboot project is started and the Deploy method is called to deploy the contract, a null pointer is displayed?
A : This problem should be caused by the inconsistency between the SDK and the node version. The node version is 3.0.0-rc1, but the Java-SDK that Springboot depends on is 3.0.0-rc2, and the node needs to be upgraded to 3.0.0-rc2. Or downgrade the Java-SDK version that Springboot depends on to 3.0.0-rc1.

If you have any questions in the process of using v3.0, you are welcome to contact the assistant to join the technical exchange group for in-depth exchanges. The community cherishes the feedback and suggestions of each partner, and expects more developers to join R&D and joint construction. If you are currently experiencing the use of v3.0, or want to participate in R&D co-construction, please contact the little assistant (v:fiscobcosfan) or click to read the original text to participate in the award-winning research, and work with the community to promote v3.0 further.

Long press the QR code to add WeChat assistant

FISCO BCOS v3.0 code repository:
https://github.com/FISCO-BCOS/FISCO-BCOS/releases/tag/v3.0.0-rc2
FISCO BCOS v3.0 technical documentation:
https://fisco-bcos-doc.readthedocs.io/zh_CN/latest/

For more dry goods, please pay attention to the FISCO BCOS open source community public account, visit the FISCO BCOS code repository to download all the source code of the project: https://github.com/FISCO-BCOS/FISCO-BCOS , please click the star collection in the upper right corner of the page , to get the latest version .