Open Source Progress | WeBASE v1.5.4 released, new training case sets and management console operation guidelines

As a friendly and feature-rich blockchain middleware platform, WeBASE has been committed to lowering the R&D threshold for blockchain developers and improving the efficiency of blockchain development.

Now, WeBASE v1.5.4 is here. This update adds a case set of blockchain application training courses, as well as management console operation guidelines and design instructions to help community developers learn blockchain more quickly and efficiently, and build blockchain application. Let's take a look at the new features brought by v1.5.4!

New training course case set

How to combine WeBASE with blockchain courses to better serve developers? In order to answer this proposition, the WeBASE team cooperated with community partners and community developers to make targeted adjustments to WeBASE functions, and launched the WeBASE training plug-in in WeBASE v1.5.1 to support teaching and training scenarios. For details, see " Open Source ". Progress | WeBASE v1.5.1 Released, Supporting Teaching and Training Scenarios ".

In this v1.5.4 update, the WeBASE technical documentation has added a "WeBASE training course case" section. The included course cases are specially designed for community training courses. The case implementation consists of training topics, experimental steps and The reference answer consists of three modules.

At present, three cases from easy to difficult are included: running the first smart contract, realizing the point transfer contract, and realizing the application of the deposit contract. Developers can refer to the case to quickly start contract development, and community partners can refer to the case and make corresponding adjustments according to their actual course design.

Practical Questions : Describe the specific requirements of this course.

As shown in Figure 1 below, the requirements for "running the first smart contract" are: use Solidity language to write a HelloWorld contract, explain what contract logic the contract needs to contain, what effect to achieve, and give the basic framework of the contract.

Figure 1: Creating the first smart contract - training topic

Experimental steps: describe the experimental steps required for the training, and each experimental step will give the corresponding answer "submission method" requirements, that is, what content needs to be submitted after completing the experimental steps.
As shown in Figure 2 below, in the step of "send transactions to the deployed smart contract", we list the content that students need to submit based on the knowledge points that students need to master in this course. For example, if students are required to master the knowledge points of connecting nodes through SDK, students are required to submit the source code of connecting nodes through SDK.
Just to be clear, the lab steps and submissions here can be adjusted according to the customized course content.

Figure 2: Creating the first smart contract - some experimental steps

Reference answers: WeBASE provides a set of reference answers for courses completed based on FISCO BCOS and WeBASE, including the source code of the implementation, screenshots of experimental steps, etc.
In the future, the WeBASE team will continue to tap the potential of WeBASE in the field of blockchain education. Community developers are also welcome to participate in the joint construction and create more diversified training courses to contribute to the community.

New operation guide for WeBASE console

In this update, [Operation Guide] has been added to each page of the WeBASE management console, which explains the design and usage of page module functions, so that users can quickly familiarize themselves with and master WeBASE.
As shown in Figure 3 below, on the WeBASE "Private Key Management" page, users can quickly understand the functions of the "Add User" and "Import Private Key" buttons through the [Operation Guide] on the right side of the page. how to use it.

Figure 3: WeBASE console - private key management page

For another example, some users may wonder why their private key or contract is marked as "abnormal" by WeBASE, and an alarm of "abnormal user" or "abnormal contract" occurs.

As shown in Figure 4 below, the user "0x97e9b7a9d5e19a8a0aa7cd39f632244da69640b6" is marked as an abnormal user by WeBASE and appears in the alarm list of "Transaction Audit - Abnormal User". After the operation guide is added in v1.5.4, users can quickly view the design and use instructions of the transaction audit function in the operation guide on the right side of the "Transaction Audit - Abnormal User" page of the WeBASE management console, and know that it is marked as "abnormal user" The reason is: the private key user has initiated transactions on the chain, but has not been registered in WeBASE's private key management.
*As long as a private key initiates a transaction on the chain, or a contract is deployed on the chain but not registered in WeBASE, the corresponding private key address or contract address will be marked as "abnormal" by WeBASE.

Figure 4: WeBASE Management Console - Transaction Audit - Abnormal User Page

In fact, we can see the user in the "private key management - full" user list, indicating that the user has indeed initiated transactions on the chain (for example, the private key that has not initiated transactions cannot be seen in the full user list). According to the description in the "Transaction Audit - Abnormal User" operation guide, the user only needs to "import" the address of the private key into WeBASE for all users, or import the private key corresponding to the user's address into WeBASE, and the "" User Abnormal" alert.

Figure 5: WeBASE console - private key management page

Other optimizations and fixes

Optimization: Optimize the contract IDE trading experience of the WeBASE management console, and enrich the input parameter prompts, such as the bytesN type prompt to enter the length and verify the parameters.

Optimization: Added "Forgot your password" and "Captcha failed to load" prompts on the login page of the WeBASE console.

Optimization: Optimize the loading method of the contract warehouse. The contract template can be loaded through the .json file in the conf/warehouse directory; community users can submit a Pull Request contribution contract directly in json format.

Optimization: Update the build_chain script of visual deployment to the latest v2.8.0, and fix the openssl version compatibility issue.

bugfix: Fixed the problem of duplicate private keys in the KeyFactory of Java-SDK called by WeBASE under certain circumstances.
bugfix: Fixed the issue of contract duplication when getting the contract list in the query event page.
bugfix: Fix the misjudgment of localhost detection in visual deployment.

Immediate use

The latest code and technical documents involved in the above optimizations and functions have been updated synchronously, and experience and star support are welcome.
If you need to consult technical questions, please reply to [Little Assistant] in this public account dialog box and enter the technical exchange group.

WeBASE code repository:
https://github.com/WeBankBlockchain/WeBASE/
WeBASE code warehouse domestic mirror:
https://gitee.com/WeBank/WeBASE/
WeBASE technical documentation:
https://webasedoc.readthedocs.io/en_US/latest
WeBASE technical documentation domestic mirror:
https://osp-1257653870.cos.ap-guangzhou.myqcloud.com/WeBASE/doc/index.html

To experience WeBASE for the first time, you can refer to the one-click deployment document:
https://webasedoc.readthedocs.io/en_US/latest/docs/WeBASE/install.html
To upgrade an existing version, please refer to:
One-click upgrade of WeBASE one-click deployment:
https://webasedoc.readthedocs.io/en_US/latest/docs/WeBASE-Install/upgrade.html#auto
WeBASE-Front upgrade instructions:
https://webasedoc.readthedocs.io/en_US/latest/docs/WeBASE-Front/upgrade.html
WeBASE-Node-Manager upgrade instructions:
https://webasedoc.readthedocs.io/en_US/latest/docs/WeBASE-Node-Manager/upgrade.html
WeBASE-Sign upgrade instructions:
https://webasedoc.readthedocs.io/en_US/latest/docs/WeBASE-Sign/upgrade.html
WeBASE-Web upgrade instructions:
https://webasedoc.readthedocs.io/en_US/latest/docs/WeBASE-Web/upgrade.html
Report problems to us, welcome to submit issues:
https://github.com/WeBankFinTech/WeBASE/issues

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 .