数据库管理系统软件产品对标技术方案

征求意见截止日期:2025年07月18日


编制单位:杭州趣链科技有限公司

参编单位:

方案编号:CS4659-20250703

标准号:ITU-T F.751.7

标准名称:Functional assessment methods for distributed ledger technology platforms

序号 关键指标名称 指标值 试验/评价方法标准
1 Hardware-based private key management To validate the ability of private key management based on hardware. Test workflow:Step 1. Generate a key pair by hardware or software, then store the private key in hardware; Step 2. Construct and submit a transfer transaction using the hardware client, and verify the transaction signature. Expected results:1. The private key was generated successfully, and stored in hardware client successfully; 2. The transaction was executed successfully and the transaction signature was verified successfully.
2 Software-based private key management To validate the ability of private key management based on software. Test workflow:Step 1. Generate a key pair by software, and store the private key in ciphertext; Step 2. Construct and submit a transfer transaction using the created account and verify the transaction signature. Expected results:1. The key pair was generated successfully and the private key was stored in ciphertext; 2. The transaction was executed successfully and the transaction signature was verified successfully.
3 Account creation To validate DLT platform account creation ability. Test workflow:Step 1. Create a user account, the private key is stored in ciphertext; Step 2. Submit a transaction with the account created above, and verify the transaction execution result; Step 3. Deploy a smart contract with the account created above. Expected results:1. The account was created successfully, private key was stored in ciphertext; 2. The transaction was submitted and executed successfully; 3. The smart contract was deployed successfully.
4 Platform maturity To validate the DLT platform maturity status. Test workflow:Step 1. Check construction start time and calculate maintenance period of the DLT platform; Step 2. Check the network scale, the number of users, and the number of smart contracts of the DLT platform; Step 3. Evaluate the DLT platform values, including economic value and social value. Expected results:1. The DLT platform was constructed early; 2. The network scale of the DLT platform was large, the number of users was large, and the number of smart contracts was large; 3. The DLT platform has great economic value or social value.
5 Data storage sustainability To validate the data persistent storage and data query capabilities in the DLT platform. Test workflow:Step 1. Construct and submit a transfer transaction to validate the persistent storage capability in the DLT platform; Step 2. Construct and submit a query transaction to validate the data query capability in the DLT platform. Expected results:1. The transfer transaction was executed successfully; 2. The query transaction was executed successfully.
6 Forward compatibility of smart contract operating mechanism To validate the forward compatibility of the smart contract operating mechanism. Test workflow:Step 1. Compile and deploy a smart contract in the DLT platform; Step 2. Invoke the smart contract by submitting a transaction; Step 3. Upgrade the DLT platform, then invoke the smart contract again by submitting a transaction. Expected results:1. The smart contract was deployed successfully on the DLT platform; 2. The contract was invoked successfully before DLT platform upgraded; 3. The contract was invoked successfully after DLT platform upgraded.
7 Consensus process with no crash and no Byzantine nodes To validate the ability of reach consensus with no crash and no Byzantine nodes in the DLT platform Test workflow:Step 1. Construct and submit a valid transfer request; Step 2. Validate the transaction execution result; Step 3. Construct and send an invalid transfer request, such as the transfer token is more than the balance; Step 4. Validate the transaction execution result. Expected results :1. The consensus of the valid transfer request was reached successfully and the transaction was executed successfully; 2. The consensus of the invalid transfer request was reached unsuccessfully, but the transaction executed failed and reason for failure was given.
8 Query DLT account information To validate the ability to query the account information in the DLT platform. Test workflow:Step 1. Check the list of accounts in the DLT platform; Step 2. Check the account asset of an account address; Step 3. Check the contracts list of the DLT platform; Step 4. Check the details of a contract. Expected results:1. The account list and the account balance in the DLT platform were viewed successfully; 2. The contract list and the contract details in the DLT platform were viewed successfully.
9 Reduce the range of consensus To validate the stability of the DLT platform after reducing the number of consensus nodes. Test workflow:Step 1. Reduce the number of consensus nodes in the DLT platform or convert consensus nodes into non-consensus nodes; Step 2. Construct and submit a transaction, then check the transaction execution result. Expected results:1. The number of consensus nodes was reduced successfully; 2. The transaction was executed successfully.
10 Smart contract upgrade To validate the ability of smart contract upgrade in the DLT platform. Test workflow:Step 1. Compile and deploy a smart contract in the DLT platform; Step 2. Upgrade the smart contract, then invoke the upgraded smart contract by submitting a transaction. Expected results:1. The smart contract was deployed successfully; 2. The contract was upgraded successfully, and the smart contract invoked successfully.
11 Transaction processing flow To validate the transaction process in the DLT platform. Test workflow:Step 1. Construct and submit a transaction, and verify the transaction signature; Step 2. Validate the broadcast process of the transaction; Step 3. Validate the consensus and packaging process of the transaction; Step 4. Validate the transaction verification process of the transaction; Step 5. Validate the persistent storage of the transaction. Expected results:1. The transaction was constructed successfully and the transaction signature was correct; 2. The transaction was broadcasted to other nodes successfully; 3. The transaction was packaged and verified successfully; 4. The transaction was stored persistently.
12 User authentication To validate the user management and authentication of DLT platform. Test workflow:Step 1. Create a user account with the necessary information, such as public key, address, etc. Step 2. Login in the DLT platform using the account created above, then check the authentication result. Expected results:The user account was created and authenticated successfully.
13 Transaction origin To validate capabilities for identifying the origin of transactions of DLT platform. Test workflow:Step 1. Display the mechanism for identifying the origin node and account address of transactions; Step 2. Submit a transaction and verify the transaction execution result; Step 3. Identify the original node and account address of the transaction. Expected results:1. The transaction was submitted and executed successfully; 2. The original node and account address of the transaction were identified.
14 Privacy protection To validate the privacy protection algorithms of the DLT platform. Test workflow:Step 1. Display the types and details of the privacy protection algorithms of the DLT platform, such as zero-knowledge proofs, ring signatures, secure multi party computation and homomorphic encryption; Step 2. Check the privacy protection algorithms, including the key code and configuration files; Step 3. Invoke the algorithm interface of the DLT platform and encrypt the data. Expected results:1. The key code and configuration files of the privacy protection algorithms were valid and complete; 2. The interface was invoked and the data was encrypted successfully by the privacy protection algorithms.
15 Expand the range of consensus To validate the expansion capabilities of consensus scope. Test workflow:Step 1. Increase the number of consensus nodes in the DLT platform, such as by adding a new consensus node or converting a non-consensus node to consensus node; Step 2. Construct and submit a transaction, then validate the transaction execution result. Expected results:1. The new consensus node was added successfully, and the number of consensus nodes was increased successfully; 2. The transaction was executed successfully.
16 Encryption declaration To validate the encryption algorithms supported by the DLT platform. Test workflow:Step 1. Display the default supported encryption algorithms, including hash algorithms, symmetric encryption algorithms, and asymmetric encryption algorithms; Step 2. Construct and submit a transaction by the default algorithm, then check the transaction execution result. Expected results:The transaction was constructed and submitted successfully, and the transaction was executed successfully.
17 User interface To test the user interface provided by DLT platform. Test workflow:Step 1. Display the types of user interfaces provided by the DLT platform, such as HTTP, remote procedure call (RPC), etc.; Step 2. Check the key code of the user interfaces; Step 3. Invoke the user interface, submit a transaction and verify the transaction execution result. Expected results:1. The key code of the user interfaces was valid and complete; 2. The interface was invoked, with the transaction submitted and executed successfully.
18 Risk management and mitigation To validate the data backup and fault recovery capabilities in the DLT platform. Test workflow:Step 1. Make a data backup; Step 2. Trigger the data recovery mechanism manually or automatically; Step 3. Validate the effectiveness of the data recovery mechanism, including data integrity and consistency. Expected results:1. The data backup was executed successfully; 2. The data recovery mechanism was triggered successfully; 3. The data recovery mechanism was effective and the data was completely recovered.
19 Consensus process with crash nodes less than the threshold value To validate the consensus ability when the number of crash nodes is less than the threshold value. Test workflow:Step 1. Ensure that the number of crash nodes is less than the threshold value, the threshold value is the largest number of crash nodes that can be tolerated in the DLT platform; Step 2. Construct and submit a transfer transaction to a non-crash node, then check the transaction execution result; Step 3. Construct and submit a transfer transaction to a crash node, then check the transaction execution result. Expected results:1. The transaction submitted to the non-crash node was executed successfully and the consensus was reached successfully; 2. The transaction submitted to the crash node was executed failed and the reason for failure was given.
20 Restricted data access To validate the data access control and security protection mechanism of the DLT platform. Test workflow:Step 1. Display the data access control and security protection solutions of the DLT platform; Step 2. Verify the data access control and security protection capabilities of the DLT platform, including: a) Check the data encryption storage, such as symmetric passwords, asymmetric passwords, and hash algorithms; b) Check the secure management of keys; c) Verify the user rights to ensure that data access can be controlled. Expected results:1. The data was stored in the DLT platform encrypted; 2. The keys were managed securely in the DLT platform; 3. The data with rights are visible, and the data without rights are invisible.
21 Complete lifecycle management of smart contract To validate the complete lifecycle management of the smart contract. Test workflow:Step 1. Compile and deploy a smart contract on the DLT platform; Step 2. Invoke the smart contract by submitting a transaction; Step 3. Freeze the contract and submit a transaction to invoke the contract; Step 4. Unfreeze the contract and submit a transaction to invoke the contract; Step 5. Destroy the contract and submit a transaction to invoke the contract. Expected results:1. The smart contract was compiled and deployed successfully; 2. The contract was invoked successfully by the transaction; 3. The contract was frozen, unfrozen, and destroyed successfully.
22 Query DLT transaction information To validate the ability to query transaction information in the DLT platform. Test workflow:Step 1. Query the original information of the transaction by the transaction hash; Step 2. Query the list of transactions in a specified block. Expected results:1. The transaction original information was obtained successfully; 2. The list of transactions was obtained successfully.
23 Pluggable encryption algorithm To validate optional encryption algorithms supported in the DLT platform. Test workflow:Step 1. Display the optional encryption algorithms supported in the DLT platform, including hash algorithms, symmetric encryption algorithms, and asymmetric encryption algorithms; Step 2. Construct and submit a transaction by any optional algorithms displayed above, then check the transaction execution result; Step 3. Construct and submit a transaction by another algorithm, then check the transaction execution result. Expected results:1. The transaction constructed and submitted by any optional algorithms successfully, and the transaction executed successfully; 2. The transaction constructed and submitted by another algorithm successfully, and the transaction executed successfully.
24 System stability To test the stability of DLT platform. Test workflow:Step 1. Submit transactions to the DLT network with a certain pressure, then execute the following steps; Step 2. Create a new node and join the existing DLT network, then submit a transaction and verify the transaction execution result; Step 3. Exit a node from the existing DLT network, submit a transaction and verify the transaction execution result; Step 4. Upgrade a node from the existing DLT network, submit a transaction and verify the transaction execution result. Expected results:1. The node was joined successfully, and the transaction was executed successfully; 2. The node was exited successfully, and the transaction was executed successfully; 3. The node was upgraded successfully, and the transaction was executed successfully.
25 Economic mechanism design To validate the economic mechanism of DLT platform. Test workflow:Step 1. Display the economic mechanism of the DLT platform, including financial incentives and non-financial incentives; Step 2. Validate the lifecycle management mechanism of the token in the DLT platform, including token issuance, token transfer, token withdrawal, token settlement, as well as token querying. Expected results:1. The economic mechanism of the DLT platform was verified successfully, and incentives were provided when the process was completed; 2. The token was issued successfully, some of the token was transferred successfully, and the token balance was queried successfully.
26 Secure transmission To validate the secure transport protocols for information transmission in DLT platform. Test workflow:Step 1. Display the secure transmission protocols in the DLT platform, such as transport layer security (TLS), hypertext transfer protocol secure (HTTPS), etc.; Step 2. Check the secure transmission protocols, including the key codes and configuration files; Step 3. Check the information transmitted to verify the encrypted status. Expected results:1. The key codes and configuration files were valid; 2. The information was transmitted in ciphertext.
27 Query DLT basic information To validate the ability to query basic information in the DLT platform. Test workflow:Step 1. Check the current block height through a DLT browser or other methods; Step 2. Check the original data of a specific block through a DLT browser or other methods; Step 3. Check the block information by block hash or block height through a DLT browser or other methods. Expected results:The basic information of DLT platform was obtained successfully, including block height and block data.
28 Open source To validate the DLT platform open-source status, including license, code hosting platform, and repository address. This case is optional. Test workflow:Step 1. Display the open-source status, including the code hosting platform, repository address, and license; Step 2. Check the code repository and verify the license at the specified open-source address; Step 3. Go to the specified open-source address and check the consistency of the key code and the testing system. Expected results:1. Codes of the DLT platform have been open-sourced and hosted on the open source platform; 2. The repository address and open-source license were valid, codes hosted in the specified repository were consistent with the DLT platform.
29 Consensus process with crash nodes more than the threshold value To validate the consensus ability when the number of crash nodes is more than the theoretical value. Test workflow:Step 1. Ensure that the number of crash nodes is greater than the threshold value, the threshold value is the largest number of crash nodes can be tolerated in the DLT platform; Step 2. Construct and submit a valid transfer transaction to a non-crash node, then check the transaction execution result; Step 3. Construct and submit a valid transfer transaction to a crash node, then check the transaction execution result. Expected results:1. The transaction submitted to the non-crash node was executed failed and reason for failure was given; 2. The transaction sent to the crash node was executed failed and the reason for failure was given.
30 Maintenance To validate the maintainability of the DLT platform. Test workflow:Step 1. Check the update records of the code, including the code committing records, branch changing records, and version releasing records; Step 2. Check the discussion records of core issues, and check contributors changing records. Expected results:1. The core codes of the DLT platform were updated recently, and new version was released recently; 2. Core issues were discussed recently, and the core contributors were stable.
31 Consensus algorithm declaration To validate the consensus algorithms supported by the DLT platform. Test workflow:Step 1. Display the consensus algorithms supported by the DLT platform, such as crash fault tolerance (CFT) consensus or Byzantine fault tolerance (BFT) consensus; Step 2. Check the relevant codes and configuration files of the consensus algorithm; Step 3. Construct and submit a transaction to verify the consensus algorithm supported in the system. Expected results:1. The relevant codes and configuration files of the consensus algorithms supported by the system were displayed successfully; 2. The transaction was sent successfully and the supported consensus algorithms were verified correctly.
32 Multi-language software development kits To validate multi-language software development kits (SDK) supported by the DLT platform. Test workflow:Step 1. Display the multi-language SDK supported by the DLT platform, and the supported language of the SDK; Step 2. Check the key code of the multi-language SDK; Step 3. Invoke the multi-language SDK, submit a transaction and verify the transaction execution result. Expected results:1. The key code of the multi-language SDK was valid and complete; 2. The multi-language SDK was invoked, with the transaction submitted and executed successfully.
33 Network management To validate the node management and monitor capabilities in the DLT platform. Test workflow:Step 1. Add a new node in the DLT platform and check the new node in the DLT platform; Step 2. View the node monitoring. Expected results:1. The number of nodes was increased successfully according to the node management mechanism; 2. The node information was displayed according to the node monitoring mechanism.

分享: