GB/T 47677.1-2026Blockchain and distributed ledger technology - Service operation - Part 1: General technical requirements for blockchain as a service (English PDF)

9.1 User Account Management Requirements

9.1.1 Account Lifecycle Management The lifecycle management of user accounts (hereinafter referred to as "users") on a blockchain-as-a-service platform should include.

a) Supports administrators in generating account passwords for Blockchain-as-a-Service platform users;

b) Supports regular users to register accounts independently;

c) Supports users in creating sub-accounts and assigning permissions to them;

d) Supports administrators in reviewing authentication information submitted by regular users, allowing them to approve or reject authentications;

e) Administrators can freeze the accounts of regular users, preventing frozen users from logging into the Blockchain-as-a-Service platform;

f) Administrators can unfreeze frozen users, and unfrozen users can log in to the Blockchain-as-a-Service platform normally.

9.1.2 Account Information Management Account information management should include.

a) Supports users submitting authentication information, which may include mobile phone number, email address, ID card number, organization code, etc.

b) After the authentication information is approved, ordinary users can modify some variable information such as mobile phone number and email address;

c) Allows administrators to view the account information and update history of all users on the Blockchain-as-a-Service platform.

9.1.3 Key Management Key management includes.

a) The blockchain-as-a-service platform should automatically create and distribute keys for users after they register;

b) Users should be able to create, download, and use both national cryptographic and non-national cryptographic keys;

9.2 Alliance Management Requirements

9.2.1 Automated Deployment Automated deployment should include.

a) Supports users in dynamically adjusting network and storage resources when deploying blockchain;

b) Supports users in deploying blockchain with a single click through a visual interface;

c) Supports user management of the entire lifecycle of the chain, including but not limited to. adding, starting, stopping, restarting, and deleting. Except for, etc.

d) Supports users in updating blockchain configurations, such as configuring TLS, flow control, maximum transaction count, etc.;

e) Supports users in visually viewing detailed information about the blockchain.

9.2.2 Node Management Node management includes.

a) Node lifecycle management should be supported, including but not limited to. adding, disabling, restarting, and deleting nodes;

b) It should support modifying and downloading node configuration files, such as node certificates, TLS configuration files, and node SDK configuration files;

c) The system should support visual viewing of the node list and detailed node information, which may include, but is not limited to, node ID, domain name, and port. Number, etc.;

d) It should support the management of node resources, including computing resources, storage resources, and network resources, throughout their entire lifecycle. This includes, but is not limited to. creating, dynamically adjusting, removing, and disabling.

9.2.3 Certificate Management Certificate management includes.

a) It should support viewing the certificate list and certificate details of consortium blockchain nodes;

b) Downloading node certificate files should be supported;

9.3 Smart Contract Management Requirements

9.3.1 Smart Contract Template Management Smart contract template management should include.

a) Support user-created contract templates, ideally supporting local upload of contract files, import of Blockchain-as-a-Service platform contract templates, and online generation. Creation methods;

b) Supports users in creating smart contracts in different languages, including Java, Solidity, and Go.

c) Supports users in editing contract template information and code;

d) Support users in deleting already created contract templates.

9.3.2 Smart Contract Lifecycle Management After gaining smart contract management privileges, users can manage the lifecycle of smart contracts. Management requirements may include.

a) Supports deploying created smart contracts on a running blockchain to form contract instances;

b) Supports calling successfully deployed contract instances on a running blockchain, and returns the call result after the call;

c) Supports viewing detailed call logs for contract instances;

d) Supports dynamic contract tracking and auditing during contract instance execution;

e) Supports upgrading created contract instances, records the contract version after upgrading, and allows users to view the contract upgrade status by version number;

f) Supports freezing running contract instances; contracts in a frozen state can no longer be successfully invoked by users.

g) Supports unfreezing frozen contract instances; unfrozen contracts can be successfully invoked.

h) Supports the cancellation of contract instances; cancelled contract instances are permanently uncallable.

9.4 Development Tool Requirements

9.4.1 API Development and Integration Tools Blockchain-as-a-Service platforms provide unified interface services for blockchain application developers, including.

a) It should support interface methods such as RESTful, WebSocket, GraphQL, and gRPC;

b) Detailed interface specifications and sample documentation should be provided;

c) The interface should adopt security measures, such as authentication mechanisms, secure transmission protocols, and encryption of sensitive fields, to ensure the security of the interface. The security of data transmission, operation, etc.;

d) Access logs for application programming interfaces (APIs) should be fully recorded, and requester-sent messages should be retained as appropriate; requester logs should be kept in conjunction with application... The sequence interface calls related login, authorization, and transaction logs.

9.4.2 Smart Contract Development Tools Smart contract development tools include.

a) It is advisable to support users in creating contract projects using contract templates;

b) The system should support users in editing, updating, and saving contract code;

c) It should support users in simulating the compilation, deployment, and execution of contracts, and return the corresponding results;

d) It is advisable to support security testing of contracts on the Blockchain-as-a-Service platform, with testing methods including but not limited to. formal verification, static verification, etc. Analysis, etc.

10.1 Monitoring and Maintenance Requirements

10.1.1 Visual Monitoring Visual monitoring should include.

a) Supports displaying data on the blockchain, including but not limited to. transaction information, block information, resource information, etc.;

b) Supports users in querying all chains under an account;

c) Visualize the number and status of nodes on the chain;

d) Visualize and display the resource usage of nodes, including but not limited to network inbound/outbound information and node status. CPU usage, node memory usage, node storage space usage, etc.;

e) Visual charts display changes in the chain's block TPS, transaction TPS, and on-chain data volume, which can be filtered by time.

f) Visualize and display the usage of infrastructure resources, including but not limited to CPU usage and memory usage. Status, storage usage, bandwidth usage, etc.

10.1.2 Log Management After obtaining log access permissions for the consortium blockchain, log management should ideally include.

a) Visualize the operation logs of each node on the chain;

b) Supports users downloading node operation logs;

c) Visualize the current user's operation history, supporting the recording of user operations related to the chain, nodes, and contract lifecycle;

d) Supports users in searching and querying logs by date selection, keywords, and other information;

e) Supports archiving and backup of logs after retaining them for a specified number of days. The retention period should be determined based on specific needs.

10.1.3 Alarm Management Alarm management should include.