CN117372050B - Method and system for verifying order verification of multiple platforms - Google Patents

Method and system for verifying order verification of multiple platforms Download PDF

Info

Publication number
CN117372050B
CN117372050B CN202311670390.9A CN202311670390A CN117372050B CN 117372050 B CN117372050 B CN 117372050B CN 202311670390 A CN202311670390 A CN 202311670390A CN 117372050 B CN117372050 B CN 117372050B
Authority
CN
China
Prior art keywords
contract
file
platform
deduction
signing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202311670390.9A
Other languages
Chinese (zh)
Other versions
CN117372050A (en
Inventor
叶飚
杨春
李健
王亚丽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chengdu Tianfutong Digital Technology Co ltd
Original Assignee
Chengdu Tianfutong Digital Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Chengdu Tianfutong Digital Technology Co ltd filed Critical Chengdu Tianfutong Digital Technology Co ltd
Priority to CN202311670390.9A priority Critical patent/CN117372050B/en
Publication of CN117372050A publication Critical patent/CN117372050A/en
Application granted granted Critical
Publication of CN117372050B publication Critical patent/CN117372050B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/21Design or setup of recognition systems or techniques; Extraction of features in feature space; Blind source separation
    • G06F18/214Generating training patterns; Bootstrap methods, e.g. bagging or boosting
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/24Classification techniques
    • G06F18/241Classification techniques relating to the classification model, e.g. parametric or non-parametric approaches
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/27Regression, e.g. linear or logistic regression
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/602Providing cryptographic facilities or services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/018Certifying business or products
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0633Lists, e.g. purchase orders, compilation or processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

The application discloses a method and a system for verifying order verification of multiple platforms. A method of multi-platform order verification, comprising: an initialization stage: the contract platforms and the signing platforms jointly provide at least one server to form a blockchain network; contract signing stage; contract verification phase: contract execution phase: transaction verification stage: and verifying each transaction according to the transaction data, the willingness file and the contract file stored on the blockchain network. In the technical scheme provided by the application, the task played by the contract platform is not only to send deduction information to the financial system, but also to monitor the execution condition of the contract, so as to actively generate a deduction instruction. Therefore, the contract platform does not cause the problem that the funds of the user are unknown because the contract platform issues the deduction instruction at will. Meanwhile, for each transaction of the intelligent contract, corresponding data can be found out on the blockchain network, so that traceability of the data is guaranteed.

Description

Method and system for verifying order verification of multiple platforms
Technical Field
The application relates to the technical field of blockchain networks, in particular to a method and a system for verifying order verification of multiple platforms.
Background
In the present internet life, there is often a case that after a user purchases a service on a certain service platform, the service platform deducts money in a customer bank account periodically and regularly through an intelligent contract. In general, each existing service platform operates independently, after the service platform signs some intelligent contracts, the user generates an instruction for drawing funds by himself/herself, and then sends the instruction to the intelligent contract platform, and then the intelligent contract platform completes the deduction.
In this mode, the specific deduction instruction is only generated unilaterally by the service platform, and the user and the contract platform cannot play any role in supervision on the generation of the deduction instruction. Therefore, the business platform can easily issue the deduction instruction illegally, the intelligent contract platform is complained, and the deduction situation cannot be traced, so that when the deduction behavior of the user is disagreeable, the intelligent platform cannot correctly judge the dispute because the intelligent platform cannot trace the source.
Disclosure of Invention
The content of the present application is intended to introduce concepts in a simplified form that are further described below in the detailed description. The section of this application is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
As a first aspect of the present application, in order to solve the problem that the existing intelligent contract platform cannot trace the transaction and cannot supervise the generation of the deduction instruction in the service platform when performing service deduction, a method for verifying order verification of multiple platforms is provided, including:
an initialization stage: the contract platforms and the signing platforms jointly provide at least one server to form a blockchain network;
contract signing stage: the user sends a contract signing request to any platform, the contract signing platform generates a contract file according to the contract signing request and sends the contract file to the user, after the user determines the contract file, the user generates a willingness file and payment information, then sends the willingness file, the contract file and payment information to the signing platform, and simultaneously sends the willingness file, the payment information and the contract file to the intelligent contract platform;
contract verification phase: after receiving the willingness file and the contract file, the contract platform checks the willingness file, generates an intelligent contract after successful check, and then sends the intelligent contract, the willingness file and the contract file to the contract platform; the signing platform determines the authenticity of the contract file and the willingness file according to the same contract file and willingness file sent by the contract platform and the user, then operates the intelligent contract, and uploads the intelligent contract to the blockchain network;
contract execution phase: after the intelligent combination in the signing platform reaches the triggering condition, generating a deduction instruction, then sending payment information to a financial system according to the deduction instruction, and dividing funds according to the payment information by the financial system; meanwhile, uploading transaction data to a blockchain network;
transaction verification stage: and verifying each transaction according to the transaction data stored on the blockchain network, the willingness file and the contract file.
In the technical scheme provided by the application, the task played by the contract platform is not only to send deduction information to the financial system, but also to monitor the execution condition of the contract, so as to actively generate a deduction instruction. Therefore, the contract platform does not cause the problem that the funds of the user are unknown because the contract platform issues the deduction instruction at will. Meanwhile, for each transaction of the intelligent contract, corresponding data can be found out on the blockchain network, so that traceability of the data is guaranteed.
The information uploaded into the blockchain network has the characteristics of being decentralised and non-tamperable, but when the servers making up the blockchain network are in the hands of an organization, the organization can still change the information stored on the blockchain network. Therefore, to solve the problem, the following technical scheme is provided in the application:
further, the initialization stage includes the steps of:
step 11: the contract signing platform has M contract platforms, which are M respectively 1 、M 2 、…M j …M m Wherein the jth contract platform is M j Each contract platform and the contract platform are provided with at least one server to form a blockchain network;
step 12: the signing platform is pre-configured with an encryption algorithm and a hash algorithm, and broadcasts the encryption algorithm and the hash algorithm to the blockchain network;
step 13: the signing platform generates a pair of public and private key pairs (Pe, pu) according to an encryption algorithm, wherein Pe is a private key and Pu is a public key; each contract platform generates a public-private key pair (M j He,M j Hu), wherein M j He is a private key, M j Hu is the public key.
According to the technical scheme, the blockchain network is a alliance blockchain network with stable internal members, and non-alliance members cannot access the blockchain network, so that the safety of information uploaded to the blockchain network is guaranteed. Meanwhile, when the blockchain network is formed, each contract platform and the contract platform are provided with a server together to form the blockchain network, so that the phenomenon that a single platform controls the whole blockchain network is avoided.
The signing platform is relatively an open platform, and the information sent to the signing platform by the user comprises payment information, so that hidden danger is easily caused to fund safety of the user when the information sent to the signing platform by the user is intercepted, and the public record of the information on the signing platform can also lead to the fact that the real business condition of the signing platform is disclosed, which is extremely unfavorable for both the user and the signing party.
Further, the contract signing phase includes the steps of:
step 21: k users under the subscription platform are respectively U 1 、U 2 、…U i 、…U k ,U i Representing the ith user;
step 22: u (U) i To M j Sending contract signing request, M j Generating a contract file according to the contract signing request, wherein the contract file at least comprises contract clauses and deduction modes;
step 23: m is M j Sending contract files to U i ,U i Verifying the contract file, and generating a willingness file after the contract file passes verification; u (U) i Transmitting willingness files and contract files to M j The method comprises the steps of carrying out a first treatment on the surface of the And then, calculating hash values of the willingness file and the contract file, encrypting the hash values of the willingness file, the hash values of the contract file and the payment information into a first key file by Pu, and then, transmitting the first key file to the signing platform.
In the technical scheme provided by the application, the files sent to the signing platform by the user are encrypted by the public key of the signing platform. Therefore, other illegal persons can not acquire the related information in the first key file except the contract platform, so that the fund safety of the user is ensured, and the real business condition of the contract platform is not disclosed.
Further, in step 22, the deduction mode includes deducting money by using time as a node and deducting money by using a triggering condition as a node.
The smart contract is generally used for triggering deduction, and from the aspect of deduction, the current deduction mode generally comprises two modes, namely, deduction is performed by taking time as a node, for example, 10 days, 20 days and 30 days after signing, or some preset conditions are met, for example, a certain event is completed. Therefore, in the scheme, the deduction modes comprise the two modes, and the deduction modes required by most service platforms in the operation process are covered.
The subscription platform is rather a service platform, as opposed to a contract platform, for dividing the funds of the user as a third party. Therefore, it is not accepted that the corresponding contract file needs to be under its supervision, or in particular the details of the contract in the contract, and is not intended to be received by the contracting platform. Therefore, in order to ensure the concealment of the user and the contract platform during the transaction, the application provides the following technical scheme:
further, the contract verification phase includes the steps of:
step 31: m is M j Receiving willingness files and contract files, M j Checking the willingness file to determine U i A real willingness to sign a contract;
step 32: m is M j Checking the received contract file, and judging whether the contract clause and deduction mode in the contract file are tampered; if there is no tampering, M j Generating intelligent contracts K from contract files ji And a deduction file, then M j Hash value of contract file, hash value of willingness file, intelligent contract K ji The deduction file is encrypted into a second key file by Pu and then sent to the signing platform;
step 33: the signing platform decrypts the first key file and the second key file respectively, compares the hash value of the willingness file, the hash value of the contract file and the deduction file in the first key file and the second key file, and if the hash values of the intelligent contract, the hash value of the willingness file and the hash value of the contract file are the same, the hash values of the intelligent contract and the willingness file are uploaded to the blockchain network, and meanwhile the intelligent contract is operated; meanwhile, generating successful authorization files by using Pe respectively, and then respectively sending the authorization files to M j And U i
In the technical scheme provided by the application, the contract platform can not receive the complete contract file and willingness file, but only the hash values of the contract file and willingness file, so that the contract platform can know the real contract content without knowing the contract signing process of the contract by both the contract signing party and the contract signing party. The authenticity of both parties to the transaction is ensured.
Because the smart contracts and deduction files are generated separately by the contract platform, there is a contract platform that generates smart contracts and deduction files that are significantly out of compliance with the regulatory regulations in the contract file. Thereby resulting in damage to the interests of the user; aiming at the problem, the application provides the following technical scheme:
further, the authorization file includes at least an intelligent contract and a deduction file.
Because the authorization file at least comprises the intelligent contract and the deduction file, the user can check the intelligent contract and the deduction file. When a problem occurs, timely reaction to the subscription platform is performed to prevent the performance of the contract.
The contract execution phase includes the steps of:
step 41: the signing platform determines triggering conditions of the deduction instruction according to the deduction file; when the triggering condition is related to time, generating a deduction instruction based on the time of the signing platform; when the triggering condition is related to the condition node, the user and the contract platform provide the same instruction file to generate a deduction instruction;
step 42: the signing platform operates the intelligent contract according to the deduction instruction, and then funds deduction of the user on the financial system is completed through payment information, and meanwhile transaction data are uploaded to the blockchain network.
In the technical scheme provided by the application, when the triggering condition is related to time, the time of the signing platform is directly used as the standard, so that the generation of the deduction instruction is only related to the signing platform, is not related to the signing platform, and the signing platform cannot independently generate the deduction instruction, so that the fund safety of a user is ensured.
Most of service platforms are used as nodes according to time when intelligent contracts are signed. For example, most members of the service platform pay a fee according to time. However, there are also some service platforms, which are debited by corresponding conditions; and the establishment of these deduction conditions can only be generated by contract platform and user; therefore, if the deduction is performed only by means of the deduction instruction generated by the contract platform, the user's interest is damaged, and if the deduction instruction is based on the user's interest, the interest of the contract platform is damaged. Aiming at the problem, the application provides the following technical scheme:
in step 41, when the triggering condition is related to the condition node, the contract platform sends an instruction file to the contract platform, the contract platform sends a deduction notification to the user after receiving the instruction file, and the contract platform generates a deduction instruction when no refusal of deduction is received in a preset period.
In the technical scheme provided by the application, the generation of the deduction instruction needs the participation of the contract platform and the user, so that the common rights and interests of the contract platform and the user are ensured as much as possible.
Further, the transaction verification stage comprises the following steps:
step 51: the signing platform finds corresponding transaction data in the blockchain network according to the verification request sent by the user;
step 52: finding out an intelligent contract for generating deduction according to corresponding transaction data in the blockchain network;
step 53: checking a deduction instruction triggering the intelligent contract, and if the deduction instruction is correct but the financial amount is incorrect, checking the intelligent contract;
step 54: if the intelligent contract examination passes, the financial data pair is not up, and then M is allowed to be continued according to the hash value of the contract file on the blockchain network j And U i A contract file is provided that is capable of respectively satisfying the hash values recorded in the blockchain network to complete the final verification.
In the technical scheme provided by the application, although the contract signing platform does not store the corresponding contract file, the whole transaction process and the contract signing process can be verified when the subsequent verification is carried out, so that the whole process is ensured to be verifiable.
As a second aspect of the present application, in practice, although most of the intelligent contracts uploaded to the blockchain network by the contract platforms are legal intelligent contracts, some malicious intelligent contracts are uploaded by some contract platforms, so that improper interests are obtained for the contract platforms, and further, the subsequent transaction verification stage has long verification period because of frequent transaction problems, and legal rights of users and other contract platforms are affected. Aiming at the problem, the application provides the following technical scheme: some embodiments of the present application provide a method of multi-platform order verification and verification, further comprising an intelligent contract monitoring phase, comprising the steps of:
step 61: the signing platform collects source codes which are predefined as malicious intelligent contracts and non-malicious intelligent contracts, and preprocesses the source codes to decompose the source codes into identifiers and operators;
step 62: extracting grammar information in source codes;
step 63: converting a source code into an abstract syntax tree, searching in an AST (automatic test) by using a known security vulnerability pattern through a regular expression or sub-graph matching technology, and marking a part of code as a potential risk area if the AST of a part is matched with the vulnerability pattern, otherwise, the code is a security area;
step 64: the goal of statistical analysis is to understand the relationship between risk code segments and different functional categories;
step 65: training a prediction model based on the characteristics and the risk association information;
step 66: and predicting the risk of the intelligent contract by using the prediction model.
According to the technical scheme, the signing platform can collect source codes of intelligent contracts with the properties confirmed before, then extract grammar information of the source codes, establish a prediction model by utilizing a logic algorithm, and find intelligent contracts with high risk threshold values by utilizing the prediction model after the model is revised, so that the intelligent contracts and corresponding contract platforms can be processed timely.
In step 61: the collected source codes are cleaned, notes, spaces and special characters are removed, and finally standardized processing is carried out.
Further, step 62 includes the steps of:
step 621: performing word segmentation on the source code by using a specific word segmentation tool, and splitting the code into a series of identifiers and operators;
step 622: generating an Abstract Syntax Tree (AST) of the source code using a specialized tool; traversing the AST to extract features related to the grammar therefrom;
step 623: identifiers in the source code are mapped to dense vectors using word embedding techniques.
In the technical scheme provided by the application, the grammar features and the semantic features of the source codes are collected, different views of the codes are provided, and better results can be obtained by combining the grammar features and the semantic features, so that the obtained grammar features and semantic features are combined, and a more comprehensive and rich feature set is provided for subsequent model training.
Further, step 64 includes the steps of:
step 641: classifying the identified risk code segments according to the functional category;
step 642: analyzing co-occurrence relations between risk code segments of different functional categories and specific vulnerability patterns, wherein the co-occurrence frequencies and conditional probabilities between the risk code segments and the specific vulnerability patterns can be calculated;
wherein, co-occurrence frequency formula:
the conditional probability formula is:wherein N (a, B) is the number of times a and B occur simultaneously, P (a, B) represents the probability of a and B occurring simultaneously, and N is the total number of samples; a represents a risk code segment, and B represents a specific vulnerability pattern; p (a|b) represents the probability that a occurs in the case where B occurs, P (a, B) is the probability that a and B occur simultaneously, and P (B) is the probability that B occurs.
Wherein, the function category is divided into the following categories: transaction setup category, transaction verification category, transaction execution category, transaction record and audit category.
This division of the solution provided by the present application may help us better understand and monitor the risk of a transactional smart contract, as each functional class may have its specific risk pattern. For example, a transaction verification category may risk a verification logic vulnerability, while a transaction execution category may risk an asset error transfer. By statistically analyzing the relationship of these risk code segments to specific functional categories, we can more accurately assess and prevent these risks.
Step 65 comprises the steps of:
step 651: selecting proper characteristics, including characteristics extracted from AST and risk associated characteristics;
step 652: model training: model training is carried out by using the selected algorithm and characteristics, and model parameters are adjusted to obtain the optimal prediction performance;
wherein the loss function for the predictive model in advance is:
where J (w) is a loss function representing the difference between the model predictions and the actual results. m is the number of training samples, i represents the i-th training sample being processed, y i Representing the true tag value, x i Is the eigenvector of the ith sample, ω is the weight parameter of the model, lambda is the regularization coefficient and, I omega I 2 This is the square of the L2 norm of the weight parameter ω, which appears as a regularization term in the loss function.
In the scheme provided by the application, the accuracy of model prediction is measured by the first part of the loss function (cross entropy loss): if the prediction score of the model is consistent with the real label, the loss value is smaller; if the prediction score is far from the true label, the penalty is large. The second part (L2 regularization term) is used to prevent model overfitting: if the L2 norm of the weight parameter ω is large, the loss value will increase, so the model will choose smaller weight parameters to reduce the risk of overfitting.
As a third aspect of the present application, some embodiments of the present application provide a system for multi-platform order verification, including a contracted platform and a contracted platform, the contracted platform and the contracted platform together forming a blockchain network; and the order is checked out according to the multi-platform order checking and verifying method.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, are included to provide a further understanding of the application and to provide a further understanding of the application with regard to the other features, objects and advantages of the application. The drawings of the illustrative embodiments of the present application and their descriptions are for the purpose of illustrating the present application and are not to be construed as unduly limiting the present application.
In addition, the same or similar reference numerals denote the same or similar elements throughout the drawings. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.
In the drawings:
FIG. 1 is a flow chart of a method of multi-platform order verification.
FIG. 2 is a schematic diagram of a system for multi-platform order verification.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.
It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings. Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.
The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Referring to fig. 1: a method of multi-platform order verification includes: an initialization stage: several contract platforms and subscription platforms together provide at least one server to compose a blockchain network.
The initialization phase comprises the following steps:
step 11: the contract signing platform has M contract platforms, which are M respectively 1 、M 2 、…M j …M m Wherein the jth contract platform is M j Each contract platform and subscription platform provides at least one server to form a blockchain network.
The contract platform and the subscription platform are essentially operated by different companies. Therefore, in step 11, each platform provides a server, essentially the company represented by each platform, and a server is provided for building the blockchain network. After the blockchain network is established, the blockchain network belongs to a relatively closed blockchain network, and only corresponding members or visitors authorized by the members can access the information on the blockchain network, namely, a contract platform and a signing platform can access the blockchain network through servers provided by the contract platform and the signing platform.
Step 12: the signing platform is pre-configured with an encryption algorithm and a hash algorithm, and broadcasts the encryption algorithm and the hash algorithm to the blockchain network.
The encryption algorithm may be an elliptic algorithm, or a RAN algorithm. The specific arrangement is not described here in detail. The hash algorithm is mainly used for calculating the hash value, and can enable the hash value to be in one-to-one correspondence with the corresponding file under the condition that the hash algorithm is specified.
Step 13: the signing platform generates a pair of public and private key pairs (Pe, pu) according to an encryption algorithm, wherein Pe is a private key and Pu is a public key; each contract platform generates a public-private key pair (M j He,M j Hu), wherein M j He is a private key, M j Hu is the public key.
The method for generating the public-private key pair is preconfigured, that is, the encryption algorithm set in step 12. After the public-private key pair is set, the sender of the file, and the privacy of the question, can be determined by means of the public key and the private key.
Contract signing stage: the user sends a contract signing request to any platform, the contract signing platform generates a contract file according to the contract signing request and sends the contract file to the user, after the user determines the contract file, the user generates a willingness file and payment information, then sends the willingness file, the contract file and payment information to the signing platform, and simultaneously sends the willingness file, the payment information and the contract file to the intelligent contract platform.
The contract signing phase includes the steps of:
step 21: k users under the subscription platform are respectively U 1 、U 2 、…U i 、…U k ,U i Representing the ith user.
The contracting platform is combined with a plurality of contract platforms to form a platform with multiple platforms for automatically fulfilling order reimbursement. Therefore, users of these contract platforms can, to some extent, be counted as users of the contract platform. In this solution, the user is directly defined as a user of the contract platform for easy understanding. In the case where one user signs up for a service with a plurality of contract platforms, the user is understood as a plurality of users. For example, a opens accounts 1, 2, and 3 on contract platform, contract platform 2, and contract platform 3, and these 3 accounts, while all actually belonging to a, should be treated as one user for account 1, account 2, and account 3, respectively.
Step 22: u (U) i To M j Sending contract signing request, M j And generating a contract file according to the contract signing request, wherein the contract file at least comprises contract clauses and deduction modes.
In step 22, the deduction mode includes deducting money by using time as a node and deducting money by using a triggering condition as a node.
Step 23: m is M j Sending contract files to U i ,U i Verifying contract filesGenerating a willingness file after passing through; u (U) i Transmitting willingness files and contract files to M j The method comprises the steps of carrying out a first treatment on the surface of the And then, calculating hash values of the willingness file and the contract file, encrypting the hash values of the willingness file, the hash values of the contract file and the payment information into a first key file by Pu, and then, transmitting the first key file to the signing platform.
The willingness file is derived by a user in the process of determining the contract file and is used for proving that the user has determined that the content in the contract file is correct. Such as a digital signature of the user, or a video information of the user reading the contract file.
Contract verification phase: after receiving the willingness file and the contract file, the contract platform checks the willingness file, generates an intelligent contract after successful check, and then sends the intelligent contract, the willingness file and the contract file to the contract platform; the signing platform determines the authenticity of the contract file and the willingness file according to the same contract file and willingness file sent by the contract platform and the user, then operates the intelligent contract, and uploads the intelligent contract to the blockchain network.
The contract verification phase includes the steps of:
step 31: m is M j Receiving willingness files and contract files, M j Checking the willingness file to determine U i The actual willingness to contract.
Step 32: m is M j Checking the received contract file, and judging whether the contract clause and deduction mode in the contract file are tampered; if there is no tampering, M j Generating intelligent contracts K from contract files ji And a deduction file, then M j Hash value of contract file, hash value of willingness file, intelligent contract K ji And the deduction file is encrypted into a second key file by Pu and then is sent to the signing platform.
In step 32, to ensure the smart contract K ji The source of the deduction file, M is also needed j M of (2) j He vs. Intelligent contract K ji And the deduction file is encrypted for the first time.
Step 33: signing platformDecrypting the first key file and the second key file respectively, comparing the hash values of the wishle files, the hash values of the contract files and the deduction files in the first key file and the second key file, if the hash values of the intelligent contract, the hash values of the wishle files and the hash values of the contract files are the same, uploading the hash values of the intelligent contract and the wishle files to a blockchain network, and running the intelligent contract at the same time; meanwhile, generating successful authorization files by using Pe respectively, and then respectively sending the authorization files to M j And U i . The authorization files include at least smart contracts and deduction files.
After decrypting the second key, for the smart contract K ji And the deduction file also needs to use M j Hu decrypts to prove its origin.
Contract execution phase: after the intelligent combination in the signing platform reaches the triggering condition, generating a deduction instruction, then sending payment information to a financial system according to the deduction instruction, and dividing funds according to the payment information by the financial system; at the same time, transaction data is uploaded to the blockchain network.
The contract execution phase includes the steps of:
step 41: the signing platform determines triggering conditions of the deduction instruction according to the deduction file; when the triggering condition is related to time, generating a deduction instruction based on the time of the signing platform; when the trigger condition is related to the condition node, the user and the contract platform provide the same instruction file to generate the deduction instruction.
In step 41, when the triggering condition is related to the condition node, the contract platform sends an instruction file to the contract platform, the contract platform sends a deduction notification to the user after receiving the instruction file, and the contract platform generates a deduction instruction when no refusal of deduction is received in a preset period.
Step 42: the signing platform operates the intelligent contract according to the deduction instruction, and then funds deduction of the user on the financial system is completed through payment information, and meanwhile transaction data are uploaded to the blockchain network.
Transaction verification stage: and verifying each transaction according to the transaction data stored on the blockchain network, the willingness file and the contract file.
The transaction verification phase includes the steps of:
step 51: the signing platform finds corresponding transaction data in the blockchain network according to the verification request sent by the user;
step 52: finding out an intelligent contract for generating deduction according to corresponding transaction data in the blockchain network;
step 53: checking a deduction instruction triggering the intelligent contract, and if the deduction instruction is correct but the financial amount is incorrect, checking the intelligent contract;
step 54: if the intelligent contract examination passes, the financial data pair is not up, and then M is allowed to be continued according to the hash value of the contract file on the blockchain network j And U i A contract file is provided that is capable of respectively satisfying the hash values recorded in the blockchain network to complete the final verification.
The method for verifying the verification of the order verification of the multiple platforms further comprises an intelligent contract monitoring stage, and the method comprises the following steps of:
step 61: the subscription platform collects source code pre-defined as malicious and non-malicious intelligent contracts and pre-processes the source code to break the source code into identifiers and operators.
The signing platform collects a large number of intelligent contracts uploaded to the blockchain network by the contract platform, so that the contracts can be used as non-malicious intelligent contracts only after the contracts stably run for a set time if no problem or dispute occurs, and the contracts which are in dispute after corresponding running are used as malicious intelligent contracts.
In step 61: the collected source codes are cleaned, notes, spaces and special characters are removed, and finally standardized processing is carried out.
Step 62: grammar information in the source code is extracted.
Specifically, step 62 includes the steps of:
step 621: the source code is segmented using a specific segmentation tool to split the code into a series of identifiers and operators.
In step 621, a particular word segmentation tool is associated with the programming language of the smart contract. In the field of source code processing, some common word segmentation tools include a lexical analyzer (Lexer) and a corresponding parsing library.
Step 622: generating Abstract Syntax Trees (AST) of source code using specialized tools (e.g., ANTLR, eclipse JDT, etc.); traversing the AST to extract features related to the grammar therefrom; such as function call structures, variable declaration locations, statement nesting levels, etc. These features are well indicative of the syntactic structure and organization of the code.
Step 623: identifiers in the source code are mapped to dense vectors using Word embedding techniques (e.g., word2Vec, gloVe, etc.). These vectors are pre-trained on a large corpus, enabling capture of semantic similarity and relevance between identifiers.
Step 63: converting the source code into an Abstract Syntax Tree (AST), searching in the AST by using a known security vulnerability pattern through a regular expression or sub-graph matching technology, and marking a part of code as a potential risk area if the AST of the part is matched with the vulnerability pattern, otherwise, the code is a security area.
Step 64: the goal of statistical analysis is to understand the relationship between risk code segments and different functional categories.
Step 641: classifying the identified risk code segments according to the functional category;
step 642: analyzing co-occurrence relations between risk code segments of different functional categories and specific vulnerability patterns, wherein the co-occurrence frequencies and conditional probabilities between the risk code segments and the specific vulnerability patterns can be calculated;
wherein, co-occurrence frequency formula:
the conditional probability formula is:wherein, N (A, B) is the number of times A and B occur simultaneously, P (A,b) Representing the probability of simultaneous occurrence of A and B, N being the total number of samples; a represents a risk code segment, and B represents a specific vulnerability pattern; p (a|b) represents the probability that a occurs in the case where B occurs, P (a, B) is the probability that a and B occur simultaneously, and P (B) is the probability that B occurs.
Wherein, the function category divides:
transaction setting category: such contract codes are responsible for initializing transaction parameters such as identity of the transaction parties, asset type of transaction, periodic time of transaction, etc.
Transaction verification category: verifying the validity and legitimacy of the transaction, e.g., verifying whether both parties to the transaction have rights to conduct the transaction, whether the assets of the transaction are sufficient, etc.
Transaction execution category: at regular points in time, it is responsible for executing transactions that have been validated, including transfer of assets, updating of both accounts, and so forth.
Transaction records and audit categories: information for each transaction is stored and recorded, providing historical record and audit functions for the transaction.
Step 65: based on the characteristics and the risk association information, a prediction model is trained.
Step 651: suitable features are selected, including features extracted from the AST, risk-related features.
Step 652: model training: model training is carried out by using the selected algorithm and characteristics, and model parameters are adjusted to obtain the optimal prediction performance;
wherein the loss function for the predictive model in advance is:
where J (w) is a loss function representing the difference between the model predictions and the actual results.
m is the number of training samples. It appears as a denominator in order to average the loss function so that the loss value is independent of the number of training samples.
i, which is an index under the summation symbol, represents that we are processing the i-th training sample.
y i This is the true tag value, which is typically 0 or 1 for binary classification problems.
x i This is the eigenvector of the ith sample. It multiplies the weight parameter w to obtain the prediction score of the model for the sample.
ω, which is the weight parameter of the model. We want to find the best ω value by an optimization algorithm so that the loss function J (w) is minimized.
Lambda this is a regularization coefficient to prevent model overfitting. If λ is set larger, the model will have a greater tendency to choose a smaller weight to reduce the risk of overfitting.
||ω|| 2 This is the square of the L2 norm of the weight parameter ω, which appears as a regularization term in the loss function.
In step 65, a predictive model is described that is built using logistic regression, and the specific training mode of the predictive model is not discussed here, and the general scheme is to divide the training data set and the verification data set, and train and verify the model. The following process can be summarized in general:
setting a logistic regression model: parameters of the logistic regression model, including weights and biases, are set.
Calculating loss: and calculating the loss value under the current model parameters by using the loss function formula of the logistic regression.
Gradient decrease: model parameters are adjusted to minimize the loss function using gradient descent or other optimization algorithms. This step is typically iterated a number of times until the loss value converges or reaches a preset number of iterations.
Regularization: to prevent overfitting, the model may be constrained using L1 or L2 regularization.
Evaluation and tuning: and performing model evaluation and tuning by using methods such as cross validation, regularization coefficient adjustment and the like.
In this scheme, the logistic regression model is selected because the types of intelligent contracts recorded in the contract signing platform are relatively single and are payment contracts of both parties of the transaction, so that the interpretation of the prediction model is paid more attention to.
Step 66: and predicting the risk of the intelligent contract by using the prediction model.
Example 2: the system comprises a contract platform and a contract platform, wherein the contract platform and the contract platform form a blockchain network together; and validating the order according to the multi-platform order validation method.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above technical features, but encompasses other technical features formed by any combination of the above technical features or their equivalents without departing from the spirit of the invention. Such as the above-described features, are mutually substituted with (but not limited to) the features having similar functions disclosed in the embodiments of the present disclosure.

Claims (5)

1. A method of multi-platform order verification, comprising:
an initialization stage: the contract platforms and the signing platforms jointly provide at least one server to form a blockchain network;
contract signing stage: the user sends a contract signing request to any one contract platform, the contract platform generates a contract file according to the contract signing request, the contract file is sent to the user, after the user determines the contract file, the willingness file and the payment information are generated, then the willingness file, the contract file and the payment information are sent to the contract platform, and meanwhile the willingness file, the payment information and the contract file are sent to the contract platform;
contract verification phase: after receiving the willingness file and the contract file, the contract platform checks the willingness file, generates an intelligent contract after successful check, and then sends the intelligent contract, the willingness file and the contract file to the contract platform; the signing platform determines the authenticity of the contract file and the willingness file according to the same contract file and willingness file sent by the contract platform and the user, then operates the intelligent contract, and uploads the intelligent contract to the blockchain network;
contract execution phase: after the intelligent combination in the signing platform reaches the triggering condition, generating a deduction instruction, then sending payment information to a financial system according to the deduction instruction, and dividing funds according to the payment information by the financial system; meanwhile, uploading transaction data to a blockchain network;
transaction verification stage: verifying each transaction according to transaction data stored on the blockchain network, the willingness file and the contract file;
the initialization phase comprises the following steps:
step 11: the contract signing platform has M contract platforms, which are M respectively 1 、M 2 、…M j …M m Wherein the jth contract platform is M j Each contract platform and subscription platform is provided with at least one server to form a blockchain network;
step 12: the signing platform is pre-configured with an encryption algorithm and a hash algorithm, and broadcasts the encryption algorithm and the hash algorithm to the blockchain network;
step 13: the signing platform generates a pair of public and private key pairs (Pe, pu) according to an encryption algorithm, wherein Pe is a private key and Pu is a public key; each contract platform generates a public-private key pair (M j He,M j Hu), wherein M j He is a private key, M j Hu is a public key;
the contract signing phase includes the steps of:
step 21: k users under the subscription platform are respectively U 1 、U 2 、…U i 、…U k ,U i Representing the ith user;
step 22: u (U) i To M j Sending contract signing request, M j Generating a contract file according to the contract signing request, wherein the contract file at least comprises contract clauses and deduction modes;
step 23: m is M j Sending contract files to U i ,U i Verifying the contract file, and generating a willingness file after the contract file passes verification; u (U) i Transmitting willingness files and contract files to M j The method comprises the steps of carrying out a first treatment on the surface of the Then, calculating hash values of the willingness file and the contract file, encrypting the hash values of the willingness file, the contract file and the payment information into a first key file by Pu, and then sending the first key file to a signing platform;
the contract verification phase includes the steps of:
step 31: m is M j Receiving willingness files and contract files, M j Checking the willingness file to determine U i A real willingness to sign a contract;
step 32: m is M j Checking the received contract file, and judging whether the contract clause and deduction mode in the contract file are tampered; if there is no tampering, M j Generating intelligent contracts K from contract files ji And a deduction file, then M j Hash value of contract file and hash value of willingness file and intelligent contract K ji The deduction file is encrypted into a second key file by Pu and then sent to the signing platform;
step 33: the signing platform decrypts the first key file and the second key file respectively, compares the hash value of the willingness file, the hash value of the contract file and the deduction file in the first key file and the second key file, and if the hash values of the intelligent contract and the willingness file are the same, uploads the hash values of the contract file and the contract file to the blockchain network, and simultaneously runs the intelligent contract; meanwhile, generating successful authorization files by using Pe respectively, and then sending the authorization files to M respectively j And U i
The contract execution phase includes the steps of:
step 41: the signing platform determines triggering conditions of the deduction instruction according to the deduction file; when the triggering condition is related to time, generating a deduction instruction based on the time of the signing platform; when the triggering condition is related to the condition node, the user and the contract platform provide the same instruction file to generate a deduction instruction;
step 42: the signing platform operates the intelligent contract according to the deduction instruction, so that fund deduction of a user on a financial system is completed through payment information, and transaction data are uploaded to a blockchain network;
the transaction verification phase includes the steps of:
step 51: the signing platform finds corresponding transaction data in the blockchain network according to the verification request sent by the user;
step 52: finding out an intelligent contract for generating deduction according to corresponding transaction data in the blockchain network;
step 53: checking the deduction instruction triggering the intelligent contract, and if the deduction instruction is correct, checking the intelligent contract if the financial amount is incorrect;
step 54: if the intelligent contract examination passes the financial amount pair, continuing to let M according to the hash value of the contract file on the blockchain network j And U i A contract file is provided that is capable of respectively satisfying the hash values recorded in the blockchain network to complete the final verification.
2. The multi-platform order verification method of claim 1, wherein: in step 22, the deduction mode includes deducting money by using time as a node and deducting money by using a triggering condition as a node.
3. The multi-platform order verification method of claim 1, wherein: the authorization files include at least smart contracts and deduction files.
4. The multi-platform order verification method of claim 1, wherein: in step 41, when the triggering condition is related to the condition node, the contract platform sends an instruction file to the contract platform, the contract platform sends a deduction notification to the user after receiving the instruction file, and the contract platform generates a deduction instruction when no refusal of deduction is received in a preset period.
5. The system for verifying and verifying the order form of multiple platforms is characterized by comprising a contract signing platform and a contract signing platform, wherein the contract signing platform and the contract signing platform form a blockchain network together; and validating orders according to the multi-platform order validation method of any one of claims 1-4.
CN202311670390.9A 2023-12-07 2023-12-07 Method and system for verifying order verification of multiple platforms Active CN117372050B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311670390.9A CN117372050B (en) 2023-12-07 2023-12-07 Method and system for verifying order verification of multiple platforms

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311670390.9A CN117372050B (en) 2023-12-07 2023-12-07 Method and system for verifying order verification of multiple platforms

Publications (2)

Publication Number Publication Date
CN117372050A CN117372050A (en) 2024-01-09
CN117372050B true CN117372050B (en) 2024-02-20

Family

ID=89406301

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311670390.9A Active CN117372050B (en) 2023-12-07 2023-12-07 Method and system for verifying order verification of multiple platforms

Country Status (1)

Country Link
CN (1) CN117372050B (en)

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109377198A (en) * 2018-12-24 2019-02-22 上海金融期货信息技术有限公司 A kind of signing system known together in many ways based on alliance's chain
CN110941857A (en) * 2019-12-12 2020-03-31 合肥都市链情商务有限公司 Privacy management system and method of block chain intelligent contract platform
CN112487778A (en) * 2020-11-16 2021-03-12 中信银行股份有限公司 Multi-user online signing system and method
CN114266681A (en) * 2021-12-23 2022-04-01 杭州时戳信息科技有限公司 Electronic contract signing method, system, storage medium and computing equipment
CN114491436A (en) * 2021-12-24 2022-05-13 彩讯科技股份有限公司 Contract signing method and device, electronic equipment and storage medium
CN115664867A (en) * 2022-12-27 2023-01-31 成都天府通数字科技有限公司 Electronic contract signing device and method based on third party authentication
CN115688191A (en) * 2022-08-29 2023-02-03 北京航空航天大学 Block chain-based electronic signature system and method
CN115953244A (en) * 2022-12-28 2023-04-11 中国人民银行数字货币研究所 Transaction supervision method and device based on block chain, electronic equipment and storage medium
WO2023091082A1 (en) * 2021-11-16 2023-05-25 Dbs Bank Ltd. Methods and systems for transaction processing using a blockchain
CN116402605A (en) * 2023-03-03 2023-07-07 华南理工大学 Subscription transaction system of user-defined network based on blockchain and interaction method thereof
CN116579890A (en) * 2023-04-13 2023-08-11 中国银行股份有限公司 Online signing system based on block chain
CN116703389A (en) * 2023-06-02 2023-09-05 中国工商银行股份有限公司 Prepaid card transaction method based on blockchain, prepaid card transaction device based on blockchain and electronic equipment
CN116739596A (en) * 2023-04-28 2023-09-12 中国工商银行股份有限公司 Blockchain-based transaction supervision method, device, equipment, medium and product
CN117009943A (en) * 2023-06-30 2023-11-07 厦门历思科技服务有限公司 Information acquisition security and fixing method, system, electronic equipment and storage medium for contract multiparty authorization signing process

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111985938A (en) * 2020-08-18 2020-11-24 支付宝(杭州)信息技术有限公司 Method, device and equipment for verifying authenticity of cross-border transaction

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109377198A (en) * 2018-12-24 2019-02-22 上海金融期货信息技术有限公司 A kind of signing system known together in many ways based on alliance's chain
CN110941857A (en) * 2019-12-12 2020-03-31 合肥都市链情商务有限公司 Privacy management system and method of block chain intelligent contract platform
CN112487778A (en) * 2020-11-16 2021-03-12 中信银行股份有限公司 Multi-user online signing system and method
WO2023091082A1 (en) * 2021-11-16 2023-05-25 Dbs Bank Ltd. Methods and systems for transaction processing using a blockchain
CN114266681A (en) * 2021-12-23 2022-04-01 杭州时戳信息科技有限公司 Electronic contract signing method, system, storage medium and computing equipment
CN114491436A (en) * 2021-12-24 2022-05-13 彩讯科技股份有限公司 Contract signing method and device, electronic equipment and storage medium
CN115688191A (en) * 2022-08-29 2023-02-03 北京航空航天大学 Block chain-based electronic signature system and method
CN115664867A (en) * 2022-12-27 2023-01-31 成都天府通数字科技有限公司 Electronic contract signing device and method based on third party authentication
CN115953244A (en) * 2022-12-28 2023-04-11 中国人民银行数字货币研究所 Transaction supervision method and device based on block chain, electronic equipment and storage medium
CN116402605A (en) * 2023-03-03 2023-07-07 华南理工大学 Subscription transaction system of user-defined network based on blockchain and interaction method thereof
CN116579890A (en) * 2023-04-13 2023-08-11 中国银行股份有限公司 Online signing system based on block chain
CN116739596A (en) * 2023-04-28 2023-09-12 中国工商银行股份有限公司 Blockchain-based transaction supervision method, device, equipment, medium and product
CN116703389A (en) * 2023-06-02 2023-09-05 中国工商银行股份有限公司 Prepaid card transaction method based on blockchain, prepaid card transaction device based on blockchain and electronic equipment
CN117009943A (en) * 2023-06-30 2023-11-07 厦门历思科技服务有限公司 Information acquisition security and fixing method, system, electronic equipment and storage medium for contract multiparty authorization signing process

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
A Blockchain-based Scalable Electronic Contract Signing System;Kaicheng Yang etal;《022 IEEE International Conferences on Internet of Things (iThings) and IEEE Green Computing & Communications (GreenCom) and IEEE Cyber, Physical & Social Computing (CPSCom) and IEEE Smart Data (SmartData) and IEEE Congress on Cybermatics (Cybermatics)》;343-348 *
区块链智能合约在应收账款管理中的应用研究;皮珊等;《湖南财政经济学院学报》;第39卷(第03期);98-106 *

Also Published As

Publication number Publication date
CN117372050A (en) 2024-01-09

Similar Documents

Publication Publication Date Title
US11526614B2 (en) Continuous vulnerability management system for blockchain smart contract based digital asset using sandbox and artificial intelligence
US10984423B2 (en) Method of operating artificial intelligence machines to improve predictive model training and performance
US10846623B2 (en) Data clean-up method for improving predictive model training
CN109347801B (en) Vulnerability exploitation risk assessment method based on multi-source word embedding and knowledge graph
US7693767B2 (en) Method for generating predictive models for a business problem via supervised learning
Zhou et al. Spi: Automated identification of security patches via commits
CA3192143A1 (en) Predicting data tampering using augmented machine learning models
CN109074563A (en) Agent-based graph-based transaction-intensive integrated feedback within blockchain systems
CN109993233B (en) Method and system for predicting data auditing objective based on machine learning
US20200143242A1 (en) System and method for creating and providing crime intelligence based on crowdsourced information stored on a blockchain
CN110348528A (en) Method is determined based on the user credit of multidimensional data mining
CN113628049B (en) Conflict arbitration method of blockchain intelligent contracts based on group intelligence
CN116361815B (en) Code sensitive information and hard coding detection method and device based on machine learning
CN116150349A (en) Data product security compliance checking method, device and server
CN110929525A (en) Network loan risk behavior analysis and detection method, device, equipment and storage medium
Diadiushkin et al. Fraud detection in payments transactions: Overview of existing approaches and usage for instant payments
CN115204886A (en) Account identification method and device, electronic equipment and storage medium
CN113505393A (en) Block chain payment data processing method applied to big data and cloud server
CN108846292B (en) Desensitization rule generation method and device
KR102259838B1 (en) Apparatus and method for building a blacklist of cryptocurrencies
CN112199480B (en) BERT model-based online dialog log violation detection method and system
CN117372050B (en) Method and system for verifying order verification of multiple platforms
CN116245669B (en) Homomorphic encryption and classification optimization-based financial audit method and system
CN110457009B (en) Method for realizing software security requirement recommendation model based on data analysis
Gehrmann et al. Metadata filtering for user-friendly centralized biometric authentication

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant