Open source progress | WeBASE v1.5.4 release, new training case collection and management console operation guide

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 collection of blockchain application training course cases, 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 collection

How to combine WeBASE with blockchain courses to better serve developers? In order to answer this proposition, the WeBASE team, community partners, and community developers worked together to make targeted adjustments to WeBASE functions, and launched a 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 section called "WeBASE Training Course Cases". The included course cases are all specially designed for community training courses . 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 certificate deposit contract application. Developers can refer to the case to quickly get started with contract development, and community partners can refer to the case to make corresponding adjustments according to their own actual course design.

Training topic: 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: Create the first smart contract - training topic

Experimental steps : Describes 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 "sending 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.

To clarify, the experimental steps and submissions here can be adjusted according to the customized course content.

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

Reference answer : WeBASE provides a set of course reference answers based on FISCO BCOS and WeBASE, including the source code of the implementation, screenshots of the experimental steps, etc.

In the future, the WeBASE team will continue to explore 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 course cases to contribute to the community.

  New operation guide for WeBASE management console

In this update, [Operation Guide] has been added to each page of the WeBASE management console, explaining the design and usage of the 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 two buttons "Add User" and "Import Private Key" through the [Operation Guide] on the right side of the page, and master the How to use it.

Figure 3: WeBASE management console - private key management page

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

As shown in Figure 4 below, the user "0x97e9b7a9d5e19a8a0aa7cd39f632244da69640b6" was marked as an abnormal user by WeBASE and appeared in the alarm list of "Transaction Audit - Abnormal User". After the new operation guide in v1.5.4, users can quickly view the design and usage 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 they are marked as "abnormal users" The reason is: the private key user has initiated a transaction 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 is 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, which means that the user has indeed initiated a transaction on the chain (for example, the private key that has not initiated a transaction cannot be seen in the full user list). According to the operation guide of "Transaction Audit - Abnormal User", 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 address into WeBASE to eliminate the " User exception" alarm.

Figure 5: WeBASE management console - private key management page

 Other optimizations and fixes

  • Optimization : Optimize the contract IDE transaction experience of the WeBASE management platform, enrich the input prompts, such as the bytesN type prompts to enter the length and verify the parameters.

  • Optimization : Added "forgot password" and "failed to load verification code" prompts on the login page of the WeBASE management 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 directly submit Pull Request contributions to the contract in accordance with the 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 : Fix the problem that the KeyFactory of the Java-SDK called by WeBASE repeats the private key under certain circumstances.

  • bugfix : Fix the problem of contract duplication in querying the event page to obtain the contract list.

  • bugfix : Fix the misjudgment of detecting localhost in visual deployment.

 use immediately

The latest codes and technical documents involved in the above optimizations and functions have been updated synchronously. Experience and star support are welcome.

If you need to consult technical questions, welcome to reply [ Little Assistant ] in the dialog box of this official account to enter the technical exchange group.

WeBASE code repository:

https://github.com/WeBankBlockchain/WeBASE/

Domestic image of WeBASE code warehouse:

https://gitee.com/WeBank/WeBASE/

WeBASE technical documentation:

https://webasedoc.readthedocs.io/zh_CN/latest

Domestic mirror of WeBASE technical documentation:

https://osp-1257653870.cos.ap-guangzhou.myqcloud.com/WeBASE/doc/index.html

For the first experience of WeBASE, please refer to the one-click deployment document:

https://webasedoc.readthedocs.io/zh_CN/latest/docs/WeBASE/install.html

If you need to upgrade the existing version, please refer to:

One-click upgrade of WeBASE one-click deployment :

https://webasedoc.readthedocs.io/zh_CN/latest/docs/WeBASE-Install/upgrade.html#auto

WeBASE-Front upgrade instructions :

https://webasedoc.readthedocs.io/zh_CN/latest/docs/WeBASE-Front/upgrade.html

WeBASE-Node-Manager upgrade instructions :

https://webasedoc.readthedocs.io/zh_CN/latest/docs/WeBASE-Node-Manager/upgrade.html

WeBASE-Sign upgrade instructions :

https://webasedoc.readthedocs.io/zh_CN/latest/docs/WeBASE-Sign/upgrade.html

WeBASE-Web upgrade instructions :

https://webasedoc.readthedocs.io/zh_CN/latest/docs/WeBASE-Web/upgrade.html

Report problems to us, welcome to file an issue:

https://github.com/WeBankFinTech/WeBASE/issues

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.

Guess you like

Origin blog.csdn.net/FISCO_BCOS/article/details/124132915