Recently, the community organized a special online Meetup to share the development route and deployment method of v3.0 in 2022. The discussion in the live broadcast room was very lively. We have sorted out some issues that developers are more concerned about, and compiled it into this FAQ and answers 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 on-chain, in terms of system architecture, v3.0 divides the blockchain system into micro-service modules such as network, computing, storage, and scheduling. Each micro-service 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 the microservice, and realize the horizontal expansion of the blockchain system.
Currently, v3.0 is still in the rc stage. Judging from the current pressure test results, the overall performance has surpassed v2.x. In 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 application fields such as cross-border, government affairs, finance, social governance, traceability of agricultural products, and copyright protection. v3.0 is currently in the rc stage, two rc versions have been released, and in the continuous iteration, it is expected that the LTS version will be released around June, and the v3.0 LTS version can be used in the production environment at that time.
Q : Have you considered converting the EBM layer into a model similar to Docker? Existing languages can be supported to write smart contracts.
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 model you mentioned is also in our future exploration plan.
Q : Is Gas in the alliance chain useful? Can it be removed?
A : Gas in the consortium chain is mainly used to prevent malicious attacks, to avoid malicious transactions that take too long to drag down nodes, so they 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 the 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. In v3.0, the dynamic group is that each node corresponding to the group 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 Pro version blockchain nodes?
A : The Pro version blockchain nodes share the network part. As we just demonstrated, we will build the RPC cluster and the Gateway cluster. These parts are shared; if you don’t want to share the RPC cluster or the Gateway cluster, you can build a separate chain. Or blockchain nodes are connected to 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 new services to the v3.0 chain, and let new services run on v3.0, or use v2 .0 corresponding to all transactions 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 DAG of v2.0 requires users to actively analyze conflict variables and find parallel conflict domains; v3.0 implements the automatic analysis function of parallel conflict domains at the SDK layer, which can automatically analyze conflict variables and automatically enable parallel conflict domains at the bottom layer. .
Q : How to study FISCO BCOS in depth?
A : You can read FISCO BCOS technical documents, or get started with the technical documents. You can also pay attention to the official account [FISCO BCOS Open Source Community], there are hundreds of development tutorials to divide blockchain learning into three stages: entry, advanced, and professional , which helps to learn step by step.
Q : When I first learned about FISCO BCOS, I want to know which ones are open source and which ones are not. Is there any boundary problem?
A : All the content of FISCO BCOS is open source. If you have any questions about FISCO BCOS, you can submit them in the form of issue on Github. FISCO BCOS developers will answer them through issues on Github. In addition, FISCO BCOS also has an official technical exchange group, you can add the small assistant WeChat account FISCOBCOS010 to the technical exchange group, and you can communicate in the group with technical questions about FISCO BCOS.
Q : After upgrading the Java-SDK to 3.0.0-rc2 in version v3.0Air, when starting the Springboot project and calling the Deploy method to deploy the contract, a null pointer is reported?
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 that Springboot depends on to 3.0.0-rc1.
If you have any questions in the process of using v3.0, welcome to contact the assistant to join the technical exchange group for in-depth exchanges. The community values each partner's feedback and suggestions very much, and looks forward to more developers joining in R&D and co-construction. If you are currently experiencing the use of v3.0, or want to participate in R&D co-construction, please contact the assistant (v: fiscobcosfan) or click to read the original text to participate in the award-winning research, and work together 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/
To learn more about dry goods, please pay attention to the FISCO BCOS open source community public account, visit the FISCO BCOS code warehouse to download all the source code of the project: https://github.com/FISCO-BCOS/FISCO-BCOS , welcome to click the star collection in the upper right corner of the page , to get the latest version.