Government system-based cloud computing operation settlement platform intelligent contract processing system

Abstract

The application provides a cloud computing operation settlement platform intelligent contract processing system based on a government system, relates to the technical field of financial technology, and comprises the following steps: a user terminal submits structured business data containing a business type identifier, amount information and an electronic voucher to a cloud intelligent contract; based on the structured business data received by the cloud intelligent contract, a standardized conversion is performed to generate an XBRL language data package; the generated XBRL data package is encrypted and stored in a distributed storage node, and a unique data index is generated; based on the unique data index, the intelligent contract calls a rule engine to retrieve and analyze the corresponding XBRL data package; and according to the business type identifier in the analysis result, the amount compliance and the authenticity of the electronic voucher are automatically checked. Through full-process automatic execution, standardized conversion, encryption and blockchain security technology, the application realizes shortening of a business cycle, data security guarantee and precise settlement.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of financial technology, and in particular to an intelligent contract processing system of a cloud computing operation settlement platform based on a government system. BACKGROUND

[0002] With the rapid development of financial technology, cloud computing and blockchain technology are increasingly widely applied in the settlement field, but the existing settlement processing methods have the following pain points:

[0003] The data formats of different business platforms may be seriously heterogeneous, core data such as electronic vouchers and amount information may lack unified semantic specifications, a large amount of manual adaptation is required for cross-platform cooperation, which may lead to low data circulation efficiency; in the traditional settlement process, the amount compliance verification, the authenticity audit of electronic vouchers, the approval level transfer and the like depend on manual operation, which not only takes a long time, but also may cause risks due to subjective bias or operation errors; the storage of business data depends on centralized servers, which may have single-point failure risks, and the data may be tampered with in the process of data transmission and storage, so that the credibility of key information such as electronic vouchers and payment instructions cannot be ensured; the key nodes (such as data submission, approval passing and fund transfer) of the whole settlement process lack tamper-proof records, and it may be difficult to quickly trace the responsibility in case of disputes; the matching of payment rules and business types depends on manual configuration, which may cause settlement condition mismatch, and the account status is not updated in time after fund transfer, which may lead to inconsistent accounts. SUMMARY

[0004] The technical problem to be solved by the application is to provide an intelligent contract processing system of a cloud computing operation settlement platform based on a government system, which realizes shortening of a business cycle, data security guarantee and accurate settlement through full-process automatic execution, standardized conversion, encryption and blockchain security technology.

[0005] To solve the above technical problems, the technical scheme of the application is as follows:

[0006] In a first aspect, an intelligent contract processing method of a cloud computing operation settlement platform based on a government system, the method comprising:

[0007] Step 1: a user terminal submits structured business data containing a business type identifier, amount information and an electronic voucher to a cloud intelligent contract;

[0008] Step 2: performing standardized conversion based on the structured business data received by the cloud intelligent contract to generate an XBRL language data package; encrypting and storing the generated XBRL data package to a distributed storage node, and generating a unique data index;

[0009] Step 3, based on the unique data index, the smart contract calls the rule engine to retrieve and parse the corresponding XBRL data package; according to the business type identification in the parsing result, the amount compliance and electronic voucher authenticity are automatically checked; when the verification is passed, the approval instruction containing the data index is generated according to the preset approval level and pushed to the terminal of the approval party;

[0010] Step 4, in response to the pass instruction returned by the terminal of the approval party, the smart contract obtains the corresponding XBRL data package through the data index; the obtained XBRL data package is subjected to block processing, and a Merkle tree structure including leaf nodes, intermediate nodes and root nodes is constructed based on the block data, wherein: the leaf node is the encrypted hash value of each data block, and the electronic voucher metadata is associated; the root node is the Merkle root hash value, which is anchored to the blockchain;

[0011] Step 5, the Merkle root hash value anchored to the blockchain is obtained and compared with the local calculation value submitted by the terminal of the approval party; when the consistency verification is passed, the encrypted payment voucher is generated according to the settlement rule matched according to the business type identification; the encrypted payment voucher is sent to the payment execution component to trigger fund transfer and update the distributed ledger state.

[0012] Further, step 1, the user terminal submits a structured business data body containing a business type identification, an amount of information and an electronic voucher to a cloud-side smart contract, including:

[0013] The user terminal extracts a set of voucher feature values of the electronic voucher, including an encoding sequence value of the invoice code, a binary representation of the amount value, and a gray scale feature value of the voucher image; the set of voucher feature values is bound to the business type identification and the amount of information as a structured business data body;

[0014] Based on the structured business data body, the anti-fake weight level distribution coefficient is allocated: the invoice code feature is allocated the highest anti-fake level coefficient, the amount value feature is allocated the medium anti-fake level coefficient, and the image gray scale feature is allocated the basic anti-fake level coefficient; the invoice code feature, the amount value feature and the image gray scale feature are subjected to weighted processing with corresponding level coefficients respectively to generate three types of weighted feature values;

[0015] The three types of weighted feature values are subjected to XOR operation in a fixed order, the invoice code feature value with the highest anti-fake level weighting is subjected to XOR operation with the amount value feature value with the medium anti-fake level weighting, an operation result is obtained, the operation result is subjected to XOR operation with the image gray scale feature value with the basic anti-fake level weighting, and finally a checksum is generated; when the deviation rate of the checksum and the pre-stored registration value is in an acceptable risk interval, a data validity flag is generated;

[0016] In response to the data validity flag, the structured business data body is transmitted to the cloud-side smart contract through an encryption channel;

[0017] The cloud intelligent contract parses the meta attribute of the received data, generates a submission credential hash containing a timestamp and a data fingerprint, and writes it into a blockchain ledger.

[0018] Further, in step 2, based on the structured business data body received by the cloud intelligent contract, a standardized conversion is performed to generate an XBRL language data package; the generated XBRL data package is stored in encrypted form in a distributed storage node, and a unique data index is generated, including:

[0019] Based on the submission credential hash, the corresponding structured business data body is retrieved from the blockchain ledger; XBRL format conversion is performed on the structured business data body: the business type identifier is mapped to the XBRL classification standard element, the amount information is converted to the XBRL numerical fact value, and the electronic voucher feature value set is encoded as the XBRL context entity, generating a standardized data package conforming to the XBRL2.1 specification;

[0020] Based on the standardized data package, a grouping encryption algorithm is used to generate an encrypted data stream; the encrypted data stream is stored in segments in a distributed storage node cluster, and the storage location identifier returned by each node is received; all storage location identifiers are fused to generate a global location hash value;

[0021] Based on the global location hash value and the submission credential hash, an index source string is generated by sequential splicing, and the string is subjected to two consecutive hash operations, and the operation result is written into the smart contract state database as an index value, forming a unique data index of the XBRL data package.

[0022] Further, in step 3, based on the unique data index, the smart contract calls the rule engine to retrieve and parse the corresponding XBRL data package; according to the business type identifier in the parsing result, the amount compliance and the authenticity of the electronic voucher are automatically checked; when the verification is passed, an approval instruction containing the data index is generated according to the pre-set approval level, and is pushed to the approval terminal, including:

[0023] Based on the unique data index, the smart contract queries the state database to obtain the XBRL data package storage location identifier; according to the location identifier, the encrypted data stream is downloaded from the distributed storage node cluster, and the XBRL data package is reconstructed after decryption using the symmetric key;

[0024] Based on the reconstructed XBRL data package, the business type identifier is matched to the pre-set rule library matching classification standard; according to the matching result, the compliance threshold of the corresponding business type is dynamically called;

[0025] Based on the compliance threshold, boundary verification is performed on the amount information in the data package; when the amount verification is passed, the feature value overall deviation rate of the electronic voucher feature value set and the pre-stored registration value is calculated, and a verification result code is generated, including a verification pass code and a verification fail code;

[0026] When the verification result code indicates that the verification is passed, the approval path and time constraint are determined according to the business type identification query approval level configuration table, and the approval instruction containing the data index, the approval path and the time constraint are encapsulated; the approval instruction is pushed to the approval terminal through the block chain event log; when the verification result code indicates that the verification fails, the process is terminated and the abnormal state code is stored in the smart contract.

[0027] Further, in step 4, in response to the pass instruction returned by the approval terminal, the smart contract obtains the corresponding XBRL data package through the data index, including:

[0028] Based on the pass instruction returned by the approval terminal, the smart contract verifies the validity of the digital signature of the instruction; when the signature is valid, the data index is extracted from the instruction; the distributed storage location identifier and the symmetric key of the XBRL data package are obtained by querying the state database through the data index;

[0029] According to the storage location identifier, the encrypted data block set is downloaded from the distributed storage node cluster; the complete XBRL data package is reconstructed by using the symmetric key to decrypt block by block.

[0030] Further, the obtained XBRL data package is subjected to block processing, and a Merkle tree structure including leaf nodes, intermediate nodes and root nodes is constructed based on the block data, wherein: the leaf nodes are encrypted hash values of each data block, and the metadata of the associated electronic certificate; the root node is a Merkle root hash value, which is anchored to the block chain, including:

[0031] For the reconstructed XBRL data package, data segmentation is performed according to the pre-defined block size, an independent data block set is generated, and a unique location identifier is assigned to each data block;

[0032] Based on the data block set, the first hash value of the original content of each data block is calculated block by block; the first hash value and the associated electronic certificate metadata are spliced to generate the leaf node value of the data block; after all the data blocks are processed, a set of leaf node values is formed;

[0033] Based on the set of leaf node values, adjacent node splicing hash operations are recursively performed to generate intermediate nodes until they are aggregated into a single root node value;

[0034] The root node value is bound with the block metadata to generate an anchored data package; the anchored data package is written into the distributed ledger through a block chain transaction initiated by the smart contract.

[0035] Further, step 5, obtain the Merkle root hash anchored to the blockchain, and compare it with the local calculation value submitted by the terminal of the approval party; when the consistency verification is passed, generate an encrypted payment voucher according to the settlement rule matched according to the business type identifier; send the encrypted payment voucher to the payment execution component to trigger fund transfer and update the distributed ledger state, including:

[0036] Based on the ledger record anchored in the blockchain, read the on-chain Merkle root hash value from the smart contract state database; after successful acquisition, request and receive the local Merkle root hash value from the terminal of the approval party; convert the on-chain hash value and the local hash value into equal-length binary strings; compare the binary strings bit by bit, count the number of different bits to generate the Hamming distance value; when the Hamming distance value is zero, generate a consistency pass signal;

[0037] In response to the consistency pass signal, extract the business type identifier from the reconstructed XBRL data packet; query the settlement rule library according to the business type identifier to match the payment condition parameters;

[0038] Based on the payment condition parameters, generate structured payment instructions; based on the structured payment instructions, use the public key registered by the payee in the blockchain to perform asymmetric encryption and generate an encrypted payment voucher; based on the encrypted payment voucher, submit the voucher to the clearing network through the standardized interface protocol of the payment execution component; listen to the fund transfer state event returned by the clearing network, and generate a settlement confirmation signal when the event type is successful;

[0039] In response to the settlement confirmation signal, mark the original transaction state as completed in the smart contract, write the settlement completion timestamp and the clearing network transaction ID, and update the associated account balance state.

[0040] In a second aspect, the smart contract processing system of the cloud computing operation settlement platform based on the government system includes:

[0041] The submission module is configured to submit structured business data including a business type identifier, amount information, and an electronic voucher to the cloud-side smart contract by the user terminal;

[0042] The preprocessing module is configured to perform standardized conversion based on the structured business data received by the cloud-side smart contract to generate an XBRL language data packet; encrypt the generated XBRL data packet and store it in a distributed storage node, and generate a unique data index;

[0043] The processing module is configured to retrieve and parse the corresponding XBRL data packet based on the unique data index by calling the rule engine of the smart contract; according to the business type identifier in the parsing result, automatically verify the amount compliance and the authenticity of the electronic voucher; when the verification is passed, generate an approval instruction containing the data index according to the pre-set approval level, and push it to the terminal of the approval party;

[0044] The anchoring module is configured to, in response to the pass instruction returned by the approval terminal, obtain a corresponding XBRL data package by the smart contract through data indexing; perform block processing on the obtained XBRL data package, and construct a Merkle tree structure including leaf nodes, intermediate nodes and a root node based on the block data, wherein the leaf nodes are encrypted hash values of the data blocks and are associated with electronic voucher metadata; and the root node is a Merkle root hash value and is anchored to a blockchain;

[0045] The settlement module is configured to obtain the Merkle root hash value anchored to the blockchain, and compare the Merkle root hash value with a local calculation value submitted by the approval terminal; when consistency verification is passed, generate an encrypted payment voucher according to a settlement rule matched according to a business type identifier; and send the encrypted payment voucher to a payment execution component to trigger fund transfer and update a distributed ledger state.

[0046] In a third aspect, a computing device includes:

[0047] one or more processors;

[0048] a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the method.

[0049] In a fourth aspect, a computer-readable storage medium stores a program, which, when executed by a processor, implements the method.

[0050] The above-mentioned scheme of the present application at least has the following beneficial effects:

[0051] Through data submission, standardized conversion, verification and approval, and payment transfer, the whole process is automatically executed, the business cycle is shortened, and the labor and time cost is reduced; through XBRL format conversion to unify data semantics and format, the cross-platform data barrier is broken, and the multi-platform and multi-agency collaboration efficiency is improved; by using encryption storage, distributed storage, Merkle tree verification and blockchain anchoring technology, data leakage and tampering are prevented, and the integrity of core data such as electronic vouchers and payment information is ensured; the rule engine automatically verifies the compliance of the amount and the authenticity of the voucher, the approval process is automatically transferred based on the preset level, the key node record is written into the blockchain, the whole process is traceable and transparent, and the operation risk is reduced; based on the business type identifier, the settlement rule is dynamically matched to generate an encrypted payment voucher and automatically trigger fund transfer, so as to ensure the accurate adaptation of payment conditions and business characteristics, and the distributed ledger is updated in real time to ensure the consistency of accounts and facts; the distributed storage and the decentralized architecture of the blockchain avoid single point failure and enhance the fault tolerance of the platform. BRIEF DESCRIPTION OF DRAWINGS

[0052] Figure 1A flowchart of an intelligent contract processing method of a cloud computing operation settlement platform based on a government affair system is provided by an embodiment of the present application.

[0053] Figure 2 A schematic diagram of an intelligent contract processing system of a cloud computing operation settlement platform based on a government affair system is provided by an embodiment of the present application. DETAILED DESCRIPTION

[0054] Exemplary embodiments of the present disclosure will be described in greater detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be accurately conveyed to those skilled in the art.

[0055] As shown in Figure 1 An intelligent contract processing method of a cloud computing operation settlement platform based on a government affair system is provided by an embodiment of the present application, and the method comprises the following steps:

[0056] Step 1: A user terminal submits a structured business data body containing a business type identifier, an amount of money information and an electronic voucher to a cloud intelligent contract;

[0057] Step 2: Based on the structured business data body received by the cloud intelligent contract, a standardized conversion is performed to generate an XBRL language data package; the generated XBRL data package is encrypted and stored in a distributed storage node, and a unique data index is generated;

[0058] Step 3: Based on the unique data index, the intelligent contract calls a rule engine to retrieve and parse the corresponding XBRL data package; according to the business type identifier in the parsing result, the amount of money compliance and the authenticity of the electronic voucher are automatically checked; when the verification is passed, an approval instruction containing the data index is generated according to a preset approval level, and is pushed to an approval terminal;

[0059] Step 4: In response to the pass instruction returned by the approval terminal, the intelligent contract obtains the corresponding XBRL data package through the data index; the obtained XBRL data package is subjected to block processing, and a Merkle tree structure containing leaf nodes, intermediate nodes and a root node is constructed based on the block data, wherein: the leaf nodes are encrypted hash values of each data block, and are associated with electronic voucher metadata; the root node is a Merkle root hash value, which is anchored to a blockchain;

[0060] Step 5: The Merkle root hash value anchored to the blockchain is obtained, and is compared with a local calculation value submitted by the approval terminal; when the consistency verification is passed, an encrypted payment voucher is generated according to the settlement rule matched by the business type identifier; the encrypted payment voucher is sent to a payment execution component to trigger fund transfer and update a distributed ledger state.

[0061] In the embodiments of the present application, the structured business data body is taken as input, the core elements are ensured to be complete, and the loss of key information is avoided; the semantic barriers between different carriers are broken through XBRL standardized conversion; the distributed storage is encrypted, and a unique data index is generated, facilitating subsequent retrieval and tracing; the corresponding data package is quickly retrieved based on the unique data index, the data calling efficiency is improved, the approval instruction containing the data index is generated according to the preset approval level, and the approval process is ensured to be standardized and orderly; the XBRL data package is processed in blocks and a Merkle tree is constructed, the data fine-grained verification is realized through the leaf nodes, any tampering of the data blocks will cause the change of the hash value, which can be accurately identified; the Merkle root hash is anchored to the blockchain, the data final state is solidified by using the tamper-proof property of the blockchain, and a reliable data benchmark is provided for subsequent settlement; the hash value comparison verifies that the root hash stored in the blockchain is consistent with the local calculation value of the approval party, ensuring that the data is not tampered from the approval to the settlement link, and guaranteeing the authenticity of the payment basis; the encrypted payment voucher is generated according to the settlement rules matched according to the business type, avoiding the mismatch of the payment rules; the fund transfer is automatically triggered, and the distributed ledger is updated, improving the payment efficiency.

[0062] In a preferred embodiment of the present application, step 1, the user terminal submits the structured business data body containing the business type identifier, the amount of information and the electronic voucher to the cloud intelligent contract, which can include:

[0063] Step 11, the user terminal extracts the voucher feature value set of the electronic voucher, including the coding sequence value of the invoice code, the binary representation of the amount of value and the gray feature value of the voucher image; the voucher feature value set is bound with the business type identifier and the amount of information as a structured business data body;

[0064] Step 12, based on the structured business data body, the anti-fake weight level distribution coefficient is allocated: the invoice code feature is allocated the highest anti-fake level coefficient, the amount of value feature is allocated the medium anti-fake level coefficient, and the image gray feature is allocated the basic anti-fake level coefficient; the invoice code feature, the amount of value feature and the image gray feature are subjected to weighted processing of the corresponding level coefficients respectively, generating three types of weighted feature values;

[0065] Step 13, the three types of weighted feature values are subjected to XOR operation in a fixed order, the invoice code feature value weighted with the highest anti-fake level is subjected to XOR operation with the amount of value feature value weighted with the medium anti-fake level, the operation result is obtained, the operation result is subjected to XOR operation with the image gray feature value weighted with the basic anti-fake level, and finally a checksum is generated; when the deviation rate of the checksum and the pre-stored registration value is in the acceptable risk interval, a data validity flag is generated;

[0066] Step 14, in response to the data validity flag, the structured business data body is transmitted to the cloud intelligent contract through an encrypted channel;

[0067] Step 15, the cloud intelligent contract parses the meta attribute of the received data, generates a submission certificate hash containing a timestamp and a data fingerprint, and writes it into a blockchain ledger.

[0068] In the embodiments of the present application, the core features of the electronic certificate are extracted in multiple dimensions to provide comprehensive basis for subsequent anti-fake verification, avoiding missing key information by single feature; structured binding ensures that business data and certificate features correspond one by one, laying a foundation for full-process data tracing; the anti-fake priority of features is distinguished by weight level, so that key features such as invoice code play a dominant role in subsequent verification; the multiple dimensional features are integrated into a single verification sum through XOR operation, which simplifies the verification logic, and the characteristics of XOR operation can quickly detect whether the feature value has been tampered with; the deviation rate judgment mechanism provides a fault tolerance space for small errors, avoids misjudgment, and improves the reliability of verification; only the verified valid data is transmitted, avoiding invalid data occupying network resources and improving transmission efficiency; the encrypted channel ensures that the data is not stolen or tampered with during transmission, ensuring the security of data from the user terminal to the cloud; the timestamp records the accurate time of data submission, and the data fingerprint ensures the uniqueness of the data, and the submission certificate hash generated by combining the two can be used as digital evidence of data submission; after writing into the blockchain, the permanent traceability of data submission behavior is realized by using the tamper-proof nature of the blockchain.

[0069] In the embodiments of the present application, when specifically applied, the following technical solutions can be used to achieve, for example:

[0070] The above step 11, the user terminal extracts three types of feature values from the electronic certificate: by reading the text information of the electronic certificate, the character / number sequence of the invoice code (such as “10-digit code composed of sequences in order”) is extracted in order; the specific value of the amount information (such as “1000 yuan”) is converted into binary form (i.e. a string of numbers composed of 0 and 1); the image of the certificate is subjected to grayscale processing, the grayscale value (such as “0-255 value”) of each pixel point in the image is extracted and a continuous feature sequence is formed; the three types of certificate feature value sets are associated and integrated with the business type identifier (such as “business trip reimbursement” “equipment procurement”), the original amount information (such as “1000 yuan”) in a fixed format to form a structured business data body (i.e. each information element is bound according to the preset field to ensure mutual association).

[0071] Step 12: According to the importance of the characteristics, the weight coefficients are set: the invoice code feature is assigned the highest anti-counterfeiting level coefficient (the coefficient value is higher than the other two types, which reflects its core position as the unique identifier), the amount value feature is assigned the medium anti-counterfeiting level coefficient (the coefficient value is between the highest and the basic), and the image gray scale feature is assigned the basic anti-counterfeiting level coefficient (the coefficient value is the lowest); the invoice code feature value is weighted with the highest level coefficient (such as multiplying the numerical value to strengthen its weight in subsequent verification), generating the invoice code weighted feature value; similarly, the amount value feature value is multiplied by the medium coefficient, and the image gray scale feature value is multiplied by the basic coefficient, respectively generating two other types of weighted feature values.

[0072] Step 13: Perform XOR operation in a fixed order: XOR process the invoice code weighted feature value of the highest anti-counterfeiting level with the amount value weighted feature value of the medium anti-counterfeiting level (such as comparing the two feature values bit by bit, the same bit result is 0, and the different bit result is 1, obtaining the intermediate operation result); then perform XOR operation on the intermediate result and the image gray scale weighted feature value of the basic anti-counterfeiting level, finally obtain a comprehensive checksum; calculate the deviation ratio between the checksum and the pre-stored registration value (i.e. the standard feature verification reference value of this type of electronic voucher) on the platform, if the deviation rate is within the pre-set acceptable risk interval (such as ≤1%), it is determined that the data is valid, and a data validity flag is generated.

[0073] Step 14: After receiving the data validity flag (i.e. step 13 confirms that the data is compliant), the user terminal establishes a secure transmission channel through an encryption protocol (such as SSL / TLS), and transmits the structured business data body (including feature values, business identifiers, amounts, etc.) in the form of ciphertext to the cloud smart contract through the channel (i.e. the data is encrypted during transmission, only the cloud smart contract can decrypt and read).

[0074] Step 15: After receiving the data, the cloud smart contract parses its meta-attributes (such as the generation time of the data, the source terminal identifier, the data format, etc.); based on the parsing result, generate a timestamp of the current time (such as a time record accurate to milliseconds) and a data fingerprint (i.e. a unique identifier obtained by hashing the structured business data body, used to distinguish different data); integrate the timestamp and the data fingerprint to generate a submission certificate hash (i.e. a unique hash value obtained by hashing the timestamp and the data fingerprint); finally, write the submission certificate hash to the blockchain ledger (i.e. stored in multiple nodes of the blockchain, forming an unalterable record).

[0075] In a preferred embodiment of the present application, step 2: based on the structured business data body received by the cloud smart contract, the standardized conversion is performed to generate an XBRL language data package; the generated XBRL data package is encrypted and stored in a distributed storage node, and a unique data index is generated, which can include:

[0076] Step 21, based on the submission credential hash, retrieve the corresponding structured business data body from the blockchain ledger; perform XBRL format conversion on the structured business data body: map the business type identifier to the XBRL taxonomy element, convert the amount information to the XBRL numerical fact value, and encode the electronic voucher feature value set as the XBRL context entity, to generate a standardized data package conforming to the XBRL2.1 specification;

[0077] Step 22, based on the standardized data package, generate an encrypted data stream using a group encryption algorithm; store the encrypted data stream in segments to a distributed storage node cluster, receive the storage location identifiers returned by each node; fuse all storage location identifiers to generate a global location hash value;

[0078] Step 23, based on the global location hash value and the submission credential hash, generate an index source string by sequential concatenation and perform two consecutive hash operations on the string, write the operation result as an index value to the smart contract state database, forming a unique data index for the XBRL data package.

[0079] In the embodiments of the present application, the submission credential hash is used to accurately retrieve data from the blockchain, ensuring that the original data converted is consistent with the user's submission and avoiding data tampering; XBRL standardized conversion unifies data format and semantics, improving data recognition and processing efficiency between different platforms; group encryption ensures that sensitive information in the standardized data package cannot be accessed by unauthorized access when stored, protecting data privacy; the distributed storage node cluster stores data blocks in a decentralized manner, avoiding data loss caused by single node failure; the global location hash value integrates all storage location information, providing a unified identifier for subsequent rapid positioning of complete data, improving data retrieval efficiency; two hash operations strengthen the uniqueness of the index value through multi-level processing; the index value is associated with the global location hash and the submission credential hash, enabling accurate tracing from the index to the data package; writing to the smart contract state database ensures that the index value is reliably stored and can be efficiently called by the smart contract.

[0080] In the embodiments of the present application, when applied specifically, the following technical solutions can be used to achieve the above-mentioned technical effects, for example:

[0081] The above step 21, based on the submission voucher hash (i.e. "digital evidence" recorded in the blockchain), matches and retrieves the corresponding structured business data body in the blockchain ledger (i.e. accurately locates the storage location of the data body in the blockchain through the hash value and extracts it); performs XBRL format conversion on the extracted structured business data body: maps the business type identifier (such as "purchase reimbursement") to the pre-defined element in the XBRL classification standard (such as "PurchaseReimbursement" element); converts the amount information (such as the specific amount value) into the numerical fact value in XBRL that meets the format requirements (i.e. records in the numerical format according to XBRL specifications, including unit, precision, etc.); encode the feature value set of the electronic voucher (such as invoice code sequence, amount binary value, etc.) as XBRL context entity (i.e. associate feature values with business scenario description information to ensure the context of feature values is traceable); finally integrate the above conversion results to generate a standardized data package that meets the XBRL2.1 specification (i.e. a data package that meets the industry standard in terms of format and semantics).

[0082] The above step 22, based on the standardized data package, uses a grouping encryption algorithm (i.e. splits the data package into fixed data block sizes and encrypts each block) to process the entire data package, generating a continuous encrypted data stream (i.e. the data package is converted into a ciphertext sequence that cannot be directly read after encryption); segment the encrypted data stream into segments of a predetermined size (such as multiple data blocks), and store them in different nodes (such as node 1 stores the first segment, node 2 stores the second segment, etc.) in the distributed storage node cluster; after each node completes storage, it returns its storage location identifier (such as node unique ID, data block storage path in the node, etc.); collect all node storage location identifiers and generate a global location hash value (i.e. a hash result that uniquely represents all storage locations) by hashing (such as hashing the combined information of all identifiers).

[0083] The above step 23, concatenates the global location hash value and the submission voucher hash in a fixed order (such as concatenating the global location hash value first, then the submission voucher hash), forming a continuous index source string; perform the first hash operation on the index source string (i.e. convert the string to a fixed length hash value through the hash algorithm), and perform the second hash operation on the result of the first operation (i.e. hash the hash value again), to get the final operation result; write the result as an index value to the state database of the smart contract (i.e. the database in the smart contract used to store key state information), forming a unique data index for the corresponding XBRL data package (i.e. the index value can be uniquely associated with the data package).

[0084] In a preferred embodiment of the present application, step 3 above, based on the unique data index, the smart contract calls the rule engine to retrieve and parse the corresponding XBRL data package; according to the business type identifier in the parsing result, the amount compliance and the authenticity of the electronic voucher are automatically checked; when the verification is passed, the approval instruction containing the data index is generated according to the preset approval level and pushed to the terminal of the approval party, which can include:

[0085] Step 31, based on the unique data index, the smart contract queries the state database to obtain the XBRL data package storage location identifier; according to the location identifier, the encrypted data stream is downloaded from the distributed storage node cluster, and the XBRL data package is reconstructed after being decrypted using the symmetric key;

[0086] Step 32, based on the reconstructed XBRL data package, the business type identifier is extracted and mapped to the matching classification standard of the preset rule library; according to the matching result, the compliance threshold of the corresponding business type is dynamically called;

[0087] Step 33, based on the compliance threshold, the boundary verification is performed on the amount information in the data package; when the amount verification is passed, the overall deviation rate of the feature value set of the electronic voucher and the pre-stored registration value is calculated, and the verification result code is generated, including the pass code and the fail code;

[0088] Step 34, when the verification result code indicates that the verification is passed, the approval path and time constraint are determined by querying the approval level configuration table according to the business type identifier, and the approval instruction containing the data index, the approval path and the time constraint are encapsulated; the approval instruction is pushed to the terminal of the approval party through the blockchain event log; when the verification result code indicates that the verification fails, the process is terminated and the exception state code is stored persistently in the smart contract.

[0089] In the embodiment of the present application, the unique data index is used to accurately locate the storage location, ensuring that the data segments downloaded from the distributed nodes accurately correspond to the target data package; symmetric key decryption ensures the security of the data before parsing, preventing unauthorized access; reconstructing the complete data package provides a complete data basis for subsequent verification and parsing; accurate matching of business type and rule library ensures that the called compliance threshold conforms to the characteristics of the business, and the dynamic calling mechanism enables the platform to flexibly adapt to rule updates of different business types, improving the adaptability and expansibility of the verification; the amount boundary verification ensures that the business amount conforms to the preset rules, preventing excessive violations; the overall deviation rate calculation of the feature value realizes multi-dimensional verification of the authenticity of the electronic voucher, and the result code clearly quantifies the verification result, providing a clear basis for subsequent processes; matching the approval level according to the business type ensures that the approval process conforms to the business characteristics, avoiding process redundancy or omission; the blockchain event log push ensures that the approval instruction is traceable and tamper-proof; the exception state code is persistent, which facilitates subsequent tracing of failure causes, and the process is terminated to avoid invalid operations.

[0090] In the embodiments of the present application, when specifically applied, the technical solutions can be implemented, for example:

[0091] The step 31, the smart contract uses a unique data index to query and obtain the XBRL data package storage location identifier (i.e. the global location hash value associated with each node storage location information) corresponding to the index in the state database; according to the location identifier, the corresponding encrypted data stream segments (i.e. the ciphertext data stored in step 22) are downloaded from the distributed storage node cluster, and each segment is decrypted by using the preset symmetric key (i.e. the same key used in encryption), and all decrypted data segments are spliced and integrated in the original order to reconstruct the complete XBRL data package (i.e. the standardized data package generated in step 21).

[0092] The step 32, the business type identifier (such as "service settlement") is extracted from the reconstructed XBRL data package, and the identifier is matched with the classification standard stored in the preset rule library (i.e. the classification standard corresponding to the business types such as "service settlement" and "purchase reimbursement" is pre-stored in the rule library); according to the matched classification standard (such as the industry standard corresponding to "service settlement"), the compliance threshold (such as the upper limit of the amount, the requirement of the voucher format, etc., which is different for different business types, such as "single not more than 50,000 yuan" for service settlement) of the business type is dynamically called.

[0093] The step 33, based on the compliance threshold (such as "single not more than 50,000 yuan"), the boundary verification of the amount information in the XBRL data package is performed (i.e. whether the actual amount is within the threshold range, such as 30,000 yuan is qualified, and 60,000 yuan is not qualified); if the amount verification is passed, the total deviation rate (i.e. the difference proportion of all characteristics, such as invoice code completely matched, amount value deviation 0.1%, image gray deviation 0.5%, and comprehensive deviation rate 0.3%) of the electronic voucher feature value set (such as invoice code sequence, image gray value, etc.) and the pre-stored registration value (i.e. the standard feature value recorded by the platform) is further calculated. According to whether the deviation rate is within the acceptable range (such as ≤1%), the verification result code (such as "00" for pass, and "01" for failure) is generated.

[0094] If the verification result code is pass (e.g. "00"), the smart contract queries the approval level configuration table (i.e. pre-stored approval nodes and order corresponding to each business type, such as "department manager -> financial director" two-level approval for service settlement) according to the business type identifier (e.g. "service settlement") to determine the specific approval path (e.g. node order) and time constraint (e.g. each level of approval needs to be completed within 24 hours); the data index, approval path and time constraint are integrated and packaged as an approval instruction, which is pushed to the corresponding approval terminal (e.g. the terminal of the department manager and the financial director) through the blockchain event log (i.e. the log record in the blockchain that can be monitored by the approval terminal); if the verification result code is fail (e.g. "01"), the current process is terminated immediately, and the exception code (e.g. "1001" represents that the amount is out of limit, and "1002" represents that the voucher feature is inconsistent) is stored in the smart contract and is persistent (i.e. permanent record, cannot be deleted or modified).

[0095] In a preferred embodiment of the application, in response to the pass instruction returned by the approval terminal, the smart contract obtains the corresponding XBRL data package through the data index; performs block processing on the obtained XBRL data package, and constructs a Merkle tree structure including leaf nodes, intermediate nodes and root nodes based on the block data, wherein: the leaf nodes are the encrypted hash values of the data blocks, and are associated with the electronic voucher metadata; the root node is the Merkle root hash value, which is anchored to the blockchain and can include:

[0096] Step 41, based on the pass instruction returned by the approval terminal, the smart contract verifies the validity of the digital signature of the instruction; when the signature is valid, the data index is extracted from the instruction; the distributed storage location identifier and the symmetric key of the XBRL data package are obtained by querying the state database through the data index;

[0097] Step 42, according to the storage location identifier, download the encrypted data block set from the distributed storage node cluster; use the symmetric key to decrypt each block and reconstruct the complete XBRL data package.

[0098] Step 43, for the reconstructed XBRL data package, perform data segmentation according to the pre-defined block size, generate a set of independent data blocks and assign a unique location identifier to each data block;

[0099] Step 44, based on the data block set, perform first hash value calculation on the original content of each data block; splice the first hash value with the associated electronic voucher metadata to generate the leaf node value of the data block by performing second hash operation; after all data blocks are processed, a set of leaf node values is formed;

[0100] Step 45, based on the set of leaf node values, recursively perform adjacent node pair splicing hash operation to generate intermediate nodes until they are aggregated into a single root node value;

[0101] Step 46, bind the root node value with the chunk metadata to generate an anchor data package; initiate a blockchain transaction through a smart contract to write the anchor data package into a distributed ledger.

[0102] In the embodiments of the present application, the digital signature verification ensures the authenticity and legality of the instruction, the accurate data index obtains the storage location and key, and supports subsequent download and decryption; distributed download ensures the efficiency and fault tolerance of data block acquisition, block-by-block decryption ensures data security, and prevents unauthorized access; reconstructing the complete data package provides complete and accurate original data for subsequent chunking and Merkle tree construction; fixed-size chunking standardizes processing, and unique identification ensures accurate positioning of data blocks, avoiding confusion; first hash verification checks the integrity of the data block, and secondary hash combined with electronic voucher metadata associates the leaf node with the content and business background, enhancing anti-counterfeiting; double hash strengthens the data tamper resistance, providing reliable underlying node data for subsequent verification; in the Merkle tree constructed by recursive hash, the intermediate nodes are associated with the lower layer hash, and the root node aggregates all data block information; with the help of hash characteristics, any change in the data block will affect the root node, which can quickly verify whether it is tampered with, improving verification efficiency and accuracy; the root node value and the chunk metadata are bound to form an anchor data package, which contains both the verification reference and the chunk background, facilitating traceability.

[0103] In the embodiments of the present application, when applied specifically, the following technical solutions can be used to achieve the above-mentioned technical effects, for example:

[0104] After the above-mentioned step 41, the smart contract first verifies the digital signature of the instruction (i.e., checks whether the signature matches the pre-set identity of the approver, confirms that the instruction is indeed sent by a legal approver and has not been tampered with) after the terminal of the approver returns the pass instruction; if the signature verification is valid, extract the data index (i.e., the unique data index) from the instruction; the smart contract queries the state database through the data index to obtain the distributed storage location identifier (i.e., the storage path of each node associated with the global location hash) of the corresponding XBRL data package and the symmetric key (consistent with the decryption key used in step 31) used for decryption.

[0105] According to the distributed storage location identifier, the smart contract downloads the corresponding encrypted data blocks (i.e., encrypted data stream segments stored in segments) from the distributed storage node cluster; after downloading, use the obtained symmetric key to decrypt each encrypted data block one by one (i.e., restore the ciphertext to the original data block by the key), and then integrate all decrypted original data blocks in their original order in the data package to reconstruct the complete XBRL data package (consistent with the data package reconstructed in step 31).

[0106] The step 43 splits the reconstructed complete XBRL data packet into multiple independent data block sets according to a predefined block size (such as a fixed number of bytes), and generates a plurality of independent data blocks (i.e., the data packet is divided into independent data blocks according to the size from the start position of the data packet); meanwhile, a unique position identifier (such as a block order number or a block identifier generated based on the starting offset of the block in the data packet) is assigned to each data block to distinguish the position information of different data blocks.

[0107] The step 44 calculates the first hash value of the original content of each data block in the data block set, and then splices the first hash value and the electronic voucher metadata (such as the generation time, number, source, and other description information of the electronic voucher) associated with the data block (i.e., the hash value and the metadata are combined in a fixed order), and performs a second hash operation on the spliced content to obtain a leaf node value corresponding to the data block. After all data blocks are processed, all leaf node values are aggregated to form a leaf node value set.

[0108] The step 45 performs a splicing hash operation on adjacent node pairs in a recursive manner based on the leaf node value set: first, the leaf node values are grouped into pairs in order, and a hash operation is performed on each pair of leaf node values to generate an intermediate node value; if the number of leaf nodes is odd, the last leaf node value is spliced with itself and then hashed to generate an intermediate node value; then, the generated intermediate node values are again subjected to the two-grouping and splicing hash operation to recursively generate the last layer of intermediate nodes, until a single root node value (i.e., a Merkle root hash value) is finally aggregated.

[0109] The step 46 binds the root node value (Merkle root hash value) and the block metadata (such as the total number of data blocks, block size, position identifier rule, and other information describing the block process) together (i.e., the root node value and the block metadata are combined in a fixed format) to generate an anchor data packet; the smart contract initiates a blockchain transaction to write the anchor data packet into the distributed ledger of the blockchain (i.e., the data packet is recorded on multiple nodes of the blockchain to form an unalterable record).

[0110] In a preferred embodiment of the present application, the step 5 compares the Merkle root hash value anchored to the blockchain with the local calculation value submitted by the terminal of the approval party; when the consistency verification is passed, an encrypted payment voucher is generated according to the settlement rule matched according to the business type identifier; the encrypted payment voucher is sent to the payment execution component to trigger fund transfer and update the distributed ledger state, which can include:

[0111] Step 51, based on the anchor in the block chain, read the on-chain Merkle root hash value from the smart contract state database based on the account record; after successful acquisition, request and receive the local Merkle root hash value to the back-office terminal; convert the on-chain hash value and the local hash value into equal-length binary strings; compare the binary strings bit by bit, count the number of different bits to generate the Hamming distance value; when the Hamming distance value is zero, generate a consistency pass signal;

[0112] Step 52, in response to the consistency pass signal, extract the business type identifier from the reconstructed XBRL data package; query the settlement rule library according to the business type identifier and match the payment condition parameters;

[0113] Step 53, based on the payment condition parameters, generate structured payment instructions; based on the structured payment instructions, use the public key registered by the payee on the block chain to perform asymmetric encryption and generate encrypted payment credentials; based on the encrypted payment credentials, submit the credentials to the clearing network through the standardized interface protocol of the payment execution component; listen to the fund transfer state event returned by the clearing network, and generate a settlement confirmation signal when the event type is successful;

[0114] Step 54, in response to the settlement confirmation signal, mark the original transaction state as completed in the smart contract, write the settlement completion timestamp and clearing network transaction ID, and update the associated account balance state.

[0115] In the embodiment of the application, the on-chain and local hash values are compared by Hamming distance quantization to ensure that the data is not tampered with after approval, and the verification process is objective and accurate; zero Hamming distance as a pass condition ensures strict verification of data consistency and provides a reliable data basis for subsequent payment; dynamically matching settlement rules based on business types ensures that payment conditions meet business characteristics; the rule library can be flexibly configured to support rapid adjustment of business rules; asymmetric encryption ensures the security of payment instructions and prevents payment information from being leaked or tampered with; the standardized interface protocol supports interfacing with different clearing networks to improve platform compatibility; real-time monitoring of payment status ensures timely access to payment results and avoids risks caused by unclear fund transfer status; clear updating of transaction status makes the business process traceable, and the timestamp and transaction ID provide complete payment link records; real-time updating of account balances ensures that the asset status in the distributed ledger is consistent with the actual fund flow, improving the asset management and control capabilities of the architecture.

[0116] In the embodiment of the application, when specifically applied, the following technical solutions can be used to achieve it, for example:

[0117] In step 51 above, the smart contract reads the written Merkle root hash value (i.e., on-chain hash value) from the blockchain ledger and requests the Merkle root hash value (i.e., local hash value) calculated locally from the approval terminal; converts the two hash values ​​into binary bit strings of the same length (e.g., both converted to 256-bit binary), compares the two binary bit strings bit by bit, and counts the number of different bits at corresponding positions (i.e., Hamming distance); if the Hamming distance is zero, it means that the two hash values ​​are completely consistent, and a consistency pass signal is generated; otherwise, a verification failure signal is generated.

[0118] In step 52 above, responding to the consistency pass signal, the business type identifier (such as "equipment procurement") is extracted from the reconstructed XBRL data packet; using this identifier, the settlement rule base (i.e., the database that stores settlement rules corresponding to different business types) is queried, and the corresponding payment condition parameters (such as "30% prepayment is required for procurement, and the remaining 70% will be paid after acceptance") are matched.

[0119] In step 53 above, based on the matched payment condition parameters (such as amount, payment time, payee information, etc.), a structured payment instruction (i.e., an instruction that encapsulates payment elements in a fixed format) is generated; the payment instruction is asymmetrically encrypted using the payee's public key registered on the blockchain to generate an encrypted payment certificate (i.e., a certificate that can only be decrypted by the payee's private key); the encrypted payment certificate is sent to the clearing network to execute the fund transfer through the standardized interface protocol of the payment execution component (such as a general payment API); the status event returned by the clearing network is monitored, and if the event type is "payment successful", a settlement confirmation signal is generated.

[0120] In step 54 above, after receiving the settlement confirmation signal, the smart contract updates the original transaction status from "processing" to "completed", records the current time as the settlement completion timestamp, and writes the transaction ID (i.e. the unique identifier of fund transfer) returned by the clearing network into the smart contract; at the same time, it updates the balance status of the transaction-related accounts (e.g., reducing the payer's account balance and increasing the payee's account balance).

[0121] like Figure 2 As shown, embodiments of the present invention also provide a smart contract processing system for a cloud computing operation and settlement platform based on the government system, including:

[0122] The submission module is used by user terminals to submit structured business data bodies containing business type identifiers, amount information, and electronic vouchers to cloud smart contracts.

[0123] The preprocessing module is used to perform standardized transformation on the structured business data body received based on the cloud smart contract, generate XBRL language data packets; encrypt and store the generated XBRL data packets to distributed storage nodes, and generate a unique data index;

[0124] The processing module is used for retrieving and parsing the corresponding XBRL data package by calling the rules engine according to the unique data index based on the smart contract; the business type identifier in the parsing result is used for automatically checking the compliance of the amount and the authenticity of the electronic voucher; when the verification is passed, the approval instruction containing the data index is generated according to the preset approval level and is pushed to the terminal of the approval party;

[0125] The anchoring module is used for obtaining the corresponding XBRL data package by the smart contract through the data index in response to the pass instruction returned by the terminal of the approval party; the obtained XBRL data package is subjected to block processing, and the Merkle tree structure containing the leaf node, the intermediate node and the root node is constructed based on the block data, wherein the leaf node is the encrypted hash value of each data block and is associated with the electronic voucher metadata; and the root node is the Merkle root hash value and is anchored to the blockchain;

[0126] The settlement module is used for comparing the Merkle root hash value anchored to the blockchain with the local calculation value submitted by the terminal of the approval party; when the consistency verification is passed, the encrypted payment voucher is generated according to the settlement rule matched with the business type identifier; and the encrypted payment voucher is sent to the payment execution component to trigger the fund transfer and update the distributed ledger state.

[0127] The above is the preferred embodiment of the present application, and it should be pointed out that for ordinary skilled persons in the technical field, some improvements and refinements can be made without departing from the principles of the present application, and these improvements and refinements should also be considered as the protection scope of the present application.

Claims

1. A method for processing smart contracts based on a cloud computing operation settlement platform of a government system, characterized in that, The method comprises: Step 1, the user terminal submits a structured business data body containing a business type identifier, an amount of information and an electronic voucher to a cloud intelligent contract; Step 2, based on the structured business data body received by the cloud intelligent contract, a standardized conversion is performed to generate an XBRL language data package; the generated XBRL data package is stored in a distributed storage node after encryption, and a unique data index is generated, including: the user terminal extracts a set of voucher feature values of the electronic voucher, including the encoding sequence value of the invoice code, the binary representation of the amount value and the gray scale feature value of the voucher image; the set of voucher feature values is bound to the business type identifier and the amount of information as a structured business data body; based on the structured business data body, the anti-fake weight level distribution coefficient is allocated: the invoice code feature is allocated the highest anti-fake level coefficient, the amount value feature is allocated the medium anti-fake level coefficient, and the image gray scale feature is allocated the basic anti-fake level coefficient; the invoice code feature, the amount value feature and the image gray scale feature are subjected to weighted processing of the corresponding level coefficients respectively to generate three types of weighted feature values; the three types of weighted feature values are subjected to XOR operation in a fixed order, the invoice code feature value weighted with the highest anti-fake level is subjected to XOR operation with the amount value feature value weighted with the medium anti-fake level to obtain an operation result, and the operation result is subjected to XOR operation with the image gray scale feature value weighted with the basic anti-fake level to finally generate a checksum; when the deviation rate of the checksum and the pre-stored registration value is within an acceptable risk interval, a data validity flag is generated; in response to the data validity flag, the structured business data body is transmitted to the cloud intelligent contract through an encrypted channel; Step 3, based on the unique data index, the intelligent contract calls the rule engine to retrieve and parse the corresponding XBRL data package; according to the business type identifier in the parsing result, the amount compliance and the electronic voucher authenticity are automatically verified; when the verification is passed, an approval instruction containing the data index is generated according to the preset approval level and pushed to the approval terminal; Step 4, in response to the pass instruction returned by the approval terminal, the intelligent contract obtains the corresponding XBRL data package through the data index; the obtained XBRL data package is subjected to block processing, and a Merkle tree structure containing leaf nodes, intermediate nodes and a root node is constructed based on the block data, wherein: the leaf nodes are encrypted hash values of each data block, and are associated with electronic voucher metadata; the root node is a Merkle root hash value, which is anchored to a blockchain; Step 5, the Merkle root hash value anchored to the blockchain is obtained and compared with the local calculation value submitted by the approval terminal; when the consistency verification is passed, an encrypted payment voucher is generated according to the settlement rule matched according to the business type identifier; the encrypted payment voucher is sent to a payment execution component to trigger fund transfer and update the distributed ledger state. 2.The government affair system based cloud computing operation settlement platform smart contract processing method according to claim 1, characterized in that, Step 1, the user terminal submits a structured business data body containing a business type identifier, an amount of information and an electronic voucher to a cloud intelligent contract, which also includes: The cloud intelligent contract analyzes the meta attributes of the received data to generate a submission voucher hash containing a timestamp and a data fingerprint, and writes it into a blockchain ledger. 3.The government affair system based cloud computing operation settlement platform smart contract processing method according to claim 2, characterized in that, Step 2, based on the structured business data received by the cloud-based smart contract, perform standardized conversion to generate XBRL language data package; Encrypt the generated XBRL data package and store it in the distributed storage node, and generate a unique data index, including: Based on the submission credential hash, retrieve the corresponding structured business data from the blockchain ledger; perform XBRL format conversion on the structured business data: map the business type identifier to the XBRL classification standard element, convert the amount information to XBRL numerical fact value, and encode the electronic certificate feature value set to XBRL context entity, generating a standardized data package conforming to XBRL2.1 specification; Based on the standardized data package, generate an encrypted data stream using a group encryption algorithm; store the encrypted data stream in the distributed storage node cluster, receive the storage location identifier returned by each node; fuse all storage location identifiers to generate a global location hash value; Based on the global location hash value and the submission credential hash, generate an index source string by sequential splicing and perform two consecutive hash operations on the string, and write the operation result as an index value to the smart contract state database, forming a unique data index for the XBRL data package. 4.The government affair system based cloud computing operation settlement platform smart contract processing method according to claim 3, characterized in that, Step 3, based on the unique data index, the smart contract calls the rule engine to retrieve and parse the corresponding XBRL data package; according to the business type identifier in the parsing result, automatically verify the amount compliance and electronic certificate authenticity; when the verification is passed, generate an approval instruction containing the data index according to the pre-set approval level and push it to the approval terminal, including: Based on the unique data index, the smart contract queries the state database to obtain the XBRL data package storage location identifier; download the encrypted data stream from the distributed storage node cluster according to the location identifier, and reconstruct the XBRL data package after decryption using the symmetric key; Based on the reconstructed XBRL data package, extract the business type identifier and match the classification standard in the pre-set rule library; dynamically call the compliance threshold of the corresponding business type according to the matching result; Based on the compliance threshold, perform boundary verification on the amount information in the data package; when the amount verification is passed, calculate the feature value overall deviation rate of the electronic certificate feature value set and the pre-stored registration value, and generate a verification result code including pass code and fail code; When the verification result code indicates that the verification is passed, query the approval level configuration table according to the business type identifier to determine the approval path and time constraints, and encapsulate the approval instruction containing the data index, approval path and time constraints; push the approval instruction to the approval terminal through the blockchain event log; when the verification result code indicates that the verification fails, terminate the process and persistently store the exception status code to the smart contract. 5.The government affair system based cloud computing operation settlement platform smart contract processing method according to claim 4, characterized in that, Step 4, in response to the pass instruction returned by the approval terminal, the smart contract obtains the corresponding XBRL data package through the data index, including: Based on the pass instruction returned by the approval terminal, the smart contract verifies the validity of the digital signature of the instruction; when the signature is valid, extract the data index from the instruction; query the state database through the data index to obtain the distributed storage location identifier and symmetric key of the XBRL data package; According to the storage location identifier, the encrypted data block set is downloaded from the distributed storage node cluster; the complete XBRL data package is reconstructed by using the symmetric key to decrypt block by block. 6.The government affair system based cloud computing operation settlement platform smart contract processing method according to claim 5, characterized in that, Perform block processing on the obtained XBRL data package, and construct a Merkle tree structure including leaf nodes, intermediate nodes and a root node based on the block data, wherein: the leaf nodes are encrypted hash values of each data block, and the electronic voucher metadata is associated; the root node is a Merkle root hash value, which is anchored to the blockchain, including: For the reconstructed XBRL data package, perform data segmentation according to the pre-defined block size, generate a set of independent data blocks and assign a unique location identifier to each data block; Based on the data block set, the first hash value of the original content of the data block is calculated block by block; the first hash value is spliced with the associated electronic voucher metadata to generate the leaf node value of the data block by performing a second hash operation; after all the data blocks are processed, a set of leaf node values is formed; Based on the set of leaf node values, adjacent node splicing hash operations are recursively performed to generate intermediate nodes until they are aggregated into a single root node value; Bind the root node value with the block metadata to generate an anchored data package; initiate a blockchain transaction through a smart contract to write the anchored data package to a distributed ledger. 7.The government affair system based cloud computing operation settlement platform smart contract processing method according to claim 6, characterized in that, Step 5, obtain the Merkle root hash value anchored to the blockchain, and compare it with the local calculation value submitted by the approval terminal; when the consistency verification is passed, generate an encrypted payment voucher according to the business type identifier to match the settlement rule; Send the encrypted payment voucher to the payment execution component to trigger fund transfer and update the distributed ledger state, including: Based on the ledger record anchored in the blockchain, read the on-chain Merkle root hash value from the smart contract state database; After successfully obtaining, request and receive the local Merkle root hash value from the approval terminal; convert the on-chain hash value and the local hash value into equal-length binary bit strings; compare the binary bit strings bit by bit, count the number of different bits to generate a Hamming distance value; when the Hamming distance value is zero, generate a consistency pass signal; In response to the consistency pass signal, extract the business type identifier from the reconstructed XBRL data package; query the settlement rule library according to the business type identifier to match the payment condition parameters; Based on the payment condition parameters, generate a structured payment instruction; based on the structured payment instruction, use the public key registered by the payee on the blockchain to perform asymmetric encryption and generate an encrypted payment voucher; based on the encrypted payment voucher, submit the voucher to the clearing network through the standardized interface protocol of the payment execution component; listen to the fund transfer state event returned by the clearing network, and generate a settlement confirmation signal when the event type is successful; In response to the settlement confirmation signal, mark the original transaction state as completed in the smart contract, write the settlement completion timestamp and clearing network transaction ID, and update the associated account balance state.

8. The smart contract processing system of the cloud computing operation settlement platform based on the government system, which realizes the method of any one of claims 1 to 7, characterized in that, Including: The submission module is used for the user terminal to submit structured business data to the cloud smart contract, including business type identifier, amount information and electronic voucher; The preprocessing module is configured to perform standardized conversion based on the structured business data received by the cloud-side smart contract to generate an XBRL language data package, encrypt the generated XBRL data package and store the encrypted XBRL data package in a distributed storage node, and generate a unique data index; The processing module is configured to search and parse the corresponding XBRL data package by calling a rule engine according to the unique data index, automatically check the compliance of the amount and the authenticity of the electronic voucher according to the business type identifier in the parsed result, and generate an approval instruction containing the data index according to a preset approval level and push the approval instruction to an approval terminal when the verification is passed; The anchoring module is configured to obtain the corresponding XBRL data package by the data index according to the passed instruction returned by the approval terminal, perform block processing on the obtained XBRL data package, and construct a Merkle tree structure containing leaf nodes, intermediate nodes and a root node based on the block data, wherein the leaf nodes are encrypted hash values of the data blocks and are associated with electronic voucher metadata, and the root node is a Merkle root hash value and is anchored to a blockchain; The settlement module is configured to obtain the Merkle root hash value anchored to the blockchain, compare the Merkle root hash value with a local calculation value submitted by the approval terminal, generate an encrypted payment voucher according to a settlement rule when consistency verification is passed, and send the encrypted payment voucher to a payment execution component to trigger fund transfer and update a distributed ledger state.

9. A computing device, comprising: The method comprises the following steps: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 7.

Images