Cross-mechanism collaborative liquidation method and system based on block chain on-chain state awareness

Abstract

The invention provides a cross-mechanism collaborative liquidation method and system based on block chain on-chain state perception, and relates to the technical field of block chains. The method comprises the following steps: submitting each settlement transaction as an on-chain event to a block chain network; based on a preset role binding relationship, registering the plurality of participating institutions into a multilateral liquidation contract; periodically triggering a multilateral clearing contract, acquiring all transaction events recorded on the block chain in the last clearing period, and generating a contact state table among the participating institutions based on the transaction events; on the basis of the contact state table, net amount calculation is carried out on the receivable amount and the payable amount of each participating mechanism, and a target clearing instruction corresponding to each participating mechanism is obtained; and calling a fund channel contract bound with the account of each participating mechanism based on the target clearing instruction, and carrying out account transfer operation. According to the technical scheme, on-chain automatic clearing and fund collaborative transfer of cross-institution settlement can be realized, the clearing efficiency is improved, and the accuracy of transaction data is ensured.

Description

Technical Field

[0001] The present disclosure relates to the field of blockchain technology, and in particular to a cross-institutional collaborative clearing method and system based on blockchain state perception. Background Art

[0002] In current multi-institutional settlement scenarios, each participant typically uses independently developed accounting systems to manage transaction records and fund flows. This decentralized management model can easily lead to inconsistent accounting standards and asynchronous data updates in practice. To address this issue, some technologies utilize centralized scheduling from a central platform, facilitating the settlement process through regular reconciliations and centralized generation of clearing instructions. While this centralized approach has improved reconciliation efficiency to some extent, it still faces significant limitations in cross-organizational clearing collaboration. For example, differences in data structures and processing cycles between different systems can easily lead to account discrepancies; central platforms often experience delays when processing high-frequency transactions, impacting settlement efficiency; and, in the event of data errors or abnormal transactions, manual intervention is costly and difficult to troubleshoot. These issues are becoming increasingly prominent in today's complex trading networks and the increasing demand for real-time processing.

[0003] Therefore, there is still room for improvement in the existing cross-institutional clearing technology in terms of clearing efficiency and accuracy.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to ordinary technicians in the field. Summary of the Invention

[0005] The purpose of the embodiments of the present disclosure is to provide a cross-institutional collaborative clearing method based on blockchain on-chain state perception, a cross-institutional collaborative clearing system based on blockchain on-chain state perception, an electronic device and a computer-readable storage medium, by uniformly processing settlement transactions as on-chain events, combining periodic state perception, net amount calculation and contract-controlled transfer operations, thereby improving the clearing efficiency and accuracy of cross-institutional collaborative clearing technology at least to a certain extent.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by practice of the present disclosure.

[0007] According to a first aspect of an embodiment of the present disclosure, a cross-institution collaborative clearing method based on blockchain on-chain state perception is provided, the method comprising: submitting each settlement transaction as an on-chain event to the blockchain network, the on-chain event comprising one or more of a transaction participant identifier, a transaction amount, a transaction time, and a transaction type; based on a preset role binding relationship, registering a plurality of participating institutions in a multilateral clearing contract, the multilateral clearing contract being deployed on the blockchain network and being used to record a mapping relationship between the participating institutions and the on-chain events; periodically triggering the multilateral clearing contract to obtain all transaction events recorded on the blockchain in the previous clearing cycle, and generating a transaction status table between the participating institutions based on the transaction events; based on the transaction status table, performing a net calculation of the receivables and payables of each participating institution to obtain a target clearing instruction corresponding to each participating institution; based on the target clearing instruction, calling a funds channel contract bound to the account of each participating institution to perform a transfer operation, the funds channel contract being deployed on the blockchain network.

[0008] In some example embodiments of the present disclosure, based on the aforementioned scheme, submitting each settlement transaction as an on-chain event to the blockchain network includes: structurally encapsulating the settlement transaction data to be submitted to obtain an on-chain event data packet; performing consistency verification on the signature information and data summary in the on-chain event data; and in response to passing the verification, submitting the on-chain event data packet to the blockchain network and recording it as the on-chain event that can participate in the clearing process.

[0009] In some example embodiments of the present disclosure, based on the aforementioned scheme, the settlement transaction data to be submitted is structurally encapsulated to obtain an on-chain event data packet, including: extracting the participant identification, transaction amount, transaction time and transaction type in the settlement transaction data, and performing standardization processing to generate corresponding structured data items; performing summary calculation on the structured data items to obtain a data summary for integrity verification; performing signature processing on the data summary to generate signature information; generating a path identifier according to the source process of the settlement transaction data, and performing hash calculation on the path identifier to obtain a path hash value; combining the structured data items, the data summary, the signature information, the path hash value and the corresponding timestamp into the on-chain event data packet.

[0010] In some example embodiments of the present disclosure, based on the aforementioned scheme, the multiple participating institutions are registered in the multilateral clearing contract based on the preset role binding relationship, including: obtaining the institutional identification and corresponding role information of each participating institution, and constructing a role binding relationship data item in a preset format; writing the role binding relationship data item into the role mapping table in the multilateral clearing contract to complete the initial role binding operation; receiving a role binding relationship change request, and authenticating the initiator of the change request according to preset permission verification rules; in response to the verification being passed, updating the role mapping table in the multilateral clearing contract according to the change request, and adjusting the role binding relationship of the corresponding institution.

[0011] In some example embodiments of the present disclosure, based on the aforementioned scheme, the generating of the transaction status table between each of the participating institutions based on the transaction event includes: configuring a timing dependency identifier for each of the transaction events, the timing dependency identifier being used to mark the trigger relationship, exclusive relationship or priority execution relationship between the transaction event and at least one associated transaction event; generating a transaction event dependency chain based on the timing dependency identifier, the dependency chain being used to characterize the execution order of transaction events with dependencies within a settlement cycle; sequentially screening all transaction events based on the dependency chain to determine a target transaction event that meets the settlement cycle execution conditions; and based on the target transaction event, counting the receivables and payables of each participating institution to generate the transaction status table.

[0012] In some example embodiments of the present disclosure, based on the aforementioned scheme, the transaction status table between each of the participating institutions is generated based on the transaction event, including: obtaining the account address of the participating party corresponding to the transaction event, calling the account balance table on the blockchain, and obtaining the current balance data of the account address; based on the account address, calling the on-chain locked position record to obtain the locked position amount data corresponding to the account address; based on the account address, calling the on-chain fund freeze status table to obtain the frozen amount data corresponding to the account address; judging the execution validity of the corresponding transaction event according to the balance data, the locked position amount data and the frozen amount data, so as to screen out valid transaction events that meet the execution conditions; based on the valid transaction event, counting the receivable amount and payable amount of each participating institution to generate the transaction status table.

[0013] In some example embodiments of the present disclosure, based on the aforementioned scheme, the receivables and payables of each of the participating institutions are netted based on the transaction status table to obtain the target clearing instructions corresponding to each participating institution, including: grouping the transaction events according to the transaction participant identifiers based on the transaction events recorded in the transaction status table to generate multiple groups of participant transaction sub-tables; performing netting calculation operations on the transaction events in the multiple groups of participant transaction sub-tables in parallel to determine the sub-clearing instructions corresponding to each group; performing hash value calculations on the sub-clearing instructions to obtain a corresponding sub-instruction hash value set; sending the sub-instruction hash value set to the blockchain network for consistency verification; in response to the verification being qualified, aggregating the sub-clearing instructions to generate the corresponding target clearing instruction set.

[0014] In some example embodiments of the present disclosure, based on the aforementioned scheme, the target clearing instruction is based on calling the funding channel contract bound to the account of each participating institution to perform a transfer operation, including: writing the target clearing instruction into a preset on-chain confirmation pool, and the on-chain confirmation pool is used to temporarily store a set of clearing instructions to be executed; based on the clearing instruction set, calling the funding channel contract bound to the account of each participating institution, initiating a fund transfer request and recording the execution status; monitoring the execution result of the fund transfer request to determine whether there is a clearing instruction that failed to transfer; in response to detecting at least one clearing instruction that failed to transfer, calling the rollback logic in the clearing contract, canceling the completed fund transfer operation, and restoring each account to the state before the execution of the clearing instruction; in response to the successful execution of all fund transfer requests, marking the clearing instructions in the on-chain confirmation pool as completed, and updating the on-chain clearing result record.

[0015] In some example embodiments of the present disclosure, based on the aforementioned scheme, the above-mentioned cross-institution collaborative clearing method based on blockchain on-chain status perception also includes: after completing the transfer operation corresponding to the target clearing instruction, obtaining the actual amount received in the account of each participating institution; comparing the actual amount received with the receivable amount and payable amount in the target clearing instruction item by item; in response to inconsistencies in the comparison results, generating an exception record and marking the corresponding clearing record as a pending verification status; and outputting a notification instruction containing the exception information to trigger the clearing alarm process.

[0016] According to a second aspect of an embodiment of the present disclosure, a cross-institution collaborative clearing system based on blockchain on-chain state perception is provided, the system comprising: an event submission module for submitting each settlement transaction as an on-chain event to the blockchain network, the on-chain event including one or more of a transaction participant identifier, a transaction amount, a transaction time, and a transaction type; an institution registration module for registering multiple participating institutions, based on a preset role binding relationship, into a multilateral clearing contract, the multilateral clearing contract being deployed on the blockchain network and recording a mapping relationship between the participating institutions and the on-chain events; a state table generation module for periodically triggering the multilateral clearing contract, obtaining all transaction events recorded on the blockchain during the previous clearing cycle, and generating a transaction state table between the participating institutions based on the transaction events; a net amount calculation module for performing a net amount calculation of the receivables and payables of each participating institution based on the transaction state table to obtain a target clearing instruction corresponding to each participating institution; and a transfer operation module for invoking a funding channel contract bound to the account of each participating institution based on the target clearing instruction to perform a transfer operation, the funding channel contract being deployed on the blockchain network.

[0017] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the cross-institutional collaborative clearing method based on blockchain on-chain status perception as in the first aspect is implemented.

[0018] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the cross-institutional collaborative clearing method based on blockchain on-chain status perception as in the first aspect is implemented.

[0019] The technical solutions provided by the embodiments of the present disclosure may have the following beneficial effects:

[0020] The cross-institutional collaborative clearing method based on blockchain on-chain state perception in the disclosed embodiments submits each settlement transaction as an on-chain event to the blockchain network, enabling multiple participating institutions to conduct subsequent processing based on the same data source, thus avoiding the problems of inconsistent transaction data and misaligned accounts caused by the independent operation of each system. On the one hand, registering participating institutions based on preset role binding relationships and recording the mapping relationship between transaction events and institutions on the chain helps to clarify the identity of each participating institution in the clearing process, reduce manual configuration operations before clearing, and improve the system's identification efficiency of participants. On the other hand, by periodically triggering the multilateral clearing contract to obtain transaction events within the clearing cycle and generating a transaction status table between participating institutions based on this, it is possible to unify the receivable and payable relationships across institutions, reduce the risk of errors in the manual statistical process, and improve processing efficiency and the collaborative ability of clearing nodes. On the other hand, netting calculations based on the transaction status table can aggregate and merge multiple transaction data, reducing the frequency of capital flow while reducing system load and avoiding resource waste or execution failures caused by frequent transfers. Ultimately, by invoking the fund channel contract bound to the participating institution's account to perform a transfer operation, funds can be transferred directly based on the target clearing instruction, eliminating the need for intermediate interface systems or offline manual processing. This improves the execution efficiency and timeliness of clearing results, and also makes the entire clearing process more transparent and traceable. This further enhances the clearing efficiency and accuracy of cross-institutional collaborative clearing technology.

[0021] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification, are used to explain the principles of the present disclosure. Obviously, the drawings described below are only some embodiments of the present disclosure, and those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0023] Figure 1 The present invention schematically illustrates a flow chart of a cross-institutional collaborative clearing method based on blockchain state perception according to some embodiments of the present disclosure.

[0024] Figure 2 The figure schematically shows a flow chart of obtaining on-chain event data packets according to some embodiments of the present disclosure.

[0025] Figure 3 The following schematically illustrates a flow chart of obtaining target clearing instructions corresponding to each participating institution according to some embodiments of the present disclosure.

[0026] Figure 4 The present invention schematically illustrates a block diagram of a cross-institutional collaborative clearing system based on blockchain state perception according to some embodiments of the present disclosure.

[0027] Figure 5 A schematic structural diagram of a computer system of an electronic device according to some embodiments of the present disclosure is schematically shown.

[0028] Figure 6 A schematic diagram of a computer-readable storage medium according to some embodiments of the present disclosure is schematically shown.

[0029] In the drawings, the same or corresponding reference numerals denote the same or corresponding parts. DETAILED DESCRIPTION

[0030] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with this specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of this specification, as detailed in the appended claims.

[0031] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. As used in this specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0032] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, such information should not be limited to these terms. These terms are merely used to distinguish information of the same type from one another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information without departing from the scope of this specification. Depending on the context, the term "if" as used herein may be interpreted as "when," "when," or "in response to determining."

[0033] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art.

[0034] In addition, the described features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, well-known methods, devices, implementations or operations are not shown or described in detail to avoid blurring various aspects of the present disclosure.

[0035] Furthermore, the drawings are schematic illustrations only and are not necessarily drawn to scale. The block diagrams shown in the drawings are merely functional entities and do not necessarily correspond to physically separate entities. In other words, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0036] In this example embodiment, a cross-institutional collaborative clearing method based on blockchain state perception is first provided. Figure 1 The following schematically illustrates a flow chart of a cross-institution collaborative clearing method based on blockchain state perception according to some embodiments of the present disclosure. Figure 1 As shown, the cross-institutional collaborative liquidation method based on blockchain state perception may include the following steps:

[0037] In step S110, each settlement transaction is submitted to the blockchain network as an on-chain event. The on-chain event includes one or more of the transaction participant identification, transaction amount, transaction time, and transaction type.

[0038] In step S120, based on the preset role binding relationship, multiple participating institutions are registered in the multilateral clearing contract. The multilateral clearing contract is deployed on the blockchain network and is used to record the mapping relationship between the participating institutions and the events on the chain.

[0039] Step S130: Periodically trigger the multilateral clearing contract to obtain all transaction events recorded on the blockchain during the previous clearing cycle, and generate a transaction status table between participating institutions based on the transaction events.

[0040] Step S140: Based on the transaction status table, the net amount of the receivable amount and the payable amount of each participating institution is calculated to obtain the target settlement instruction corresponding to each participating institution.

[0041] In step S150, based on the target clearing instruction, the fund channel contract bound to the account of each participating institution is called to perform the transfer operation. The fund channel contract is deployed on the blockchain network.

[0042] According to the cross-institution collaborative clearing method based on blockchain on-chain state awareness in this exemplary embodiment, by submitting each settlement transaction as an on-chain event to the blockchain network, multiple participating institutions can conduct subsequent processing based on the same data source, avoiding the problems of inconsistent transaction data and misaligned accounts caused by the independent operation of each system. On the one hand, registering participating institutions based on preset role binding relationships and recording the mapping relationship between transaction events and institutions on the chain helps to clarify the identity of each participating institution in the clearing process, reduce manual configuration operations before clearing, and improve the system's identification efficiency of participants. On the other hand, by periodically triggering the multilateral clearing contract to obtain transaction events within the clearing cycle and generating a transaction status table between participating institutions based on this, it is possible to unify the receivable and payable relationships across institutions, reduce the risk of errors in the manual statistical process, and improve processing efficiency and the coordination ability between clearing nodes. On the other hand, netting calculations based on the transaction status table can aggregate and merge multiple transaction data, reducing the frequency of capital flow and system load, avoiding resource waste or execution failures caused by frequent transfers. Ultimately, by invoking the fund channel contract bound to the participating institution's account to perform a transfer operation, funds can be transferred directly based on the target clearing instruction, eliminating the need for intermediate interface systems or offline manual processing. This improves the execution efficiency and timeliness of clearing results, and also makes the entire clearing process more transparent and traceable. This further enhances the clearing efficiency and accuracy of cross-institutional collaborative clearing technology.

[0043] Below, the cross-institutional collaborative clearing method based on blockchain on-chain state perception in this example embodiment will be further explained.

[0044] In step S110, each settlement transaction is submitted to the blockchain network as an on-chain event. The on-chain event includes one or more of the transaction participant identification, transaction amount, transaction time, and transaction type.

[0045] A settlement transaction can represent a funds settlement request generated by two or more institutions based on business transactions. This request can include the corresponding payer, payee, amount, and transaction trigger conditions, representing the value exchange behavior that needs to be processed within the settlement cycle. An on-chain event can represent a structured data item submitted to a blockchain network and recorded in a distributed ledger. A blockchain network can represent a decentralized data management platform composed of multiple consensus nodes. The platform supports the sequential writing of transaction events, the distributed execution of contract logic, and the synchronization of data status across the entire network, ensuring the immutability and verifiability of on-chain events. A transaction participant identifier can represent the account address, institution number, or on-chain registration identifier used to uniquely identify each participating institution in the settlement transaction. A transaction type can represent the business classification attributes of the settlement transaction, including but not limited to transfer, refund, split, and merge.

[0046] In step S120, based on the preset role binding relationship, multiple participating institutions are registered in the multilateral clearing contract. The multilateral clearing contract is deployed on the blockchain network and is used to record the mapping relationship between the participating institutions and the events on the chain.

[0047] Role bindings can represent configurations that determine the functional roles of different participating institutions in the clearing process. These roles include, but are not limited to, payer, payee, clearing observer node, and settlement initiator node. These role bindings enable on-chain contracts to identify the division of responsibilities and authority control for each participating institution. A participating institution can represent the institution responsible for paying, receiving, or processing funds in a clearing transaction. These participating institutions can be entities registered on the blockchain network and possess account address identifiers, including but not limited to banks, securities firms, payment platforms, or other third-party institutions with clearing qualifications. A multilateral clearing contract can represent a contract program deployed on the blockchain network that establishes a mapping between settlement transactions and roles among multiple registered participating institutions. It automatically retrieves corresponding on-chain event data within a set clearing cycle, generates a transaction status table between participating institutions based on clearing rules, and further performs netting calculations and generates clearing instructions to enable cross-institutional collaborative clearing operations.

[0048] Step S130: Periodically trigger the multilateral clearing contract to obtain all transaction events recorded on the blockchain during the previous clearing cycle, and generate a transaction status table between participating institutions based on the transaction events.

[0049] The clearing cycle can represent the time window used to periodically trigger the processing logic of the multilateral clearing contract. This clearing cycle can be a fixed time interval, such as 5 minutes, 30 minutes, 1 hour, or 1 business day, or it can be dynamically adjusted based on preset conditions, such as early triggering when a set threshold of transaction events is reached or when high-frequency trading behavior occurs. The transaction status table can represent a structured data set constructed based on the transaction event data recorded on the blockchain network during the predetermined clearing cycle and the capital flow relationship between participating institutions. It is used to represent the receivables and payables between the institutions during the current clearing cycle.

[0050] Step S140: Based on the transaction status table, the net amount of the receivable amount and the payable amount of each participating institution is calculated to obtain the target settlement instruction corresponding to each participating institution.

[0051] Among them, the net amount calculation can represent the numerical relationship between the receivable and payable amounts of each participating institution in the transaction status table, and the calculation of the difference value of its funds to be cleared by institution dimension. This difference value is used to determine the actual fund settlement amount of the participating institution in the current cycle. The clearing instruction can represent a data structure generated based on the net amount calculation result and used to guide the on-chain fund channel contract to execute the transfer operation. The clearing instruction can include fields such as the clearing party identifier, counterparty identifier, clearing amount, and instruction status, and is used to drive the execution of the actual fund transfer process after the end of the clearing cycle.

[0052] In step S150, based on the target clearing instruction, the fund channel contract bound to the account of each participating institution is called to perform the transfer operation. The fund channel contract is deployed on the blockchain network.

[0053] A funding channel contract can represent a contract program deployed on a blockchain network and bound to the account addresses of participating institutions. It is used to transfer funds according to the content of the clearing instructions. The funding channel contract can verify account balances, confirm transfer paths, and complete the update of funds between on-chain accounts when the transfer conditions are met. The transfer operation can represent the process of calling the funding channel contract to transfer the value of cleared funds from the payer's account to the payee's account.

[0054] The technical contents in steps S110 to S150 of the above embodiment are described in detail below.

[0055] In some embodiments, each settlement transaction is submitted to the blockchain network as an on-chain event, including: structurally encapsulating the submitted settlement transaction data to obtain an on-chain event data packet; performing consistency verification on the signature information and data summary in the on-chain event data; in response to passing the verification, submitting the on-chain event data packet to the blockchain network and recording it as an on-chain event that can participate in the clearing process.

[0056] Among them, the on-chain event data packet can represent a structured data set constructed from the settlement transaction data to be submitted. This data set may include the transaction participant identification, transaction amount, transaction time, transaction type, signature information, data summary, and other fields used for clearing identification. It is used to record and process as a unit event in the blockchain network. The signature information can represent the digital signature result generated by the transaction data or its summary content based on a preset encryption algorithm. It is used to verify the authenticity of the data source and the legitimacy of the submitting party's identity on the chain. The data summary can represent the summary value calculated by the hash algorithm on the core fields of the settlement transaction. It is used for data integrity verification during the signature verification process.

[0057] In this embodiment, by structurally encapsulating the settlement transaction data to be submitted and generating an on-chain event data packet containing signature information and data summary, consistency verification is performed before the data is submitted, which can effectively ensure the source credibility and content integrity of the transaction data before it is uploaded to the chain; after the verification is passed, the data packet is submitted to the blockchain network and recorded as an on-chain event that can participate in the clearing process, which helps to improve the data credibility of the on-chain clearing process, the effectiveness of chain entry, and the security and stability of subsequent processing.

[0058] In some embodiments, reference Figure 2 As shown, the structure of the settlement transaction data to be submitted is encapsulated to obtain an on-chain event data packet, which specifically includes the following technical steps:

[0059] Step S210: extract the participant identification, transaction amount, transaction time and transaction type from the settlement transaction data, perform standardization processing on them, and generate corresponding structured data items.

[0060] Among them, standardization can refer to the process of data cleaning, format conversion and type verification for each field content in the settlement transaction data according to the preset format specifications and field agreement rules. Standardization can ensure the consistency and parsability of the data structure to meet the subsequent on-chain packaging and processing requirements. Structured data items can represent data units composed of standardized fields such as participant identification, transaction amount, transaction time and transaction type.

[0061] Step S220: performing digest calculation on the structured data item to obtain a data digest for integrity verification.

[0062] Specifically, when performing summary calculation, you can first select the participant identification, transaction amount, transaction time and transaction type in the structured data item as the summary input fields; splice the fields according to the preset field order to generate a character string to be summarized; perform hash calculation on the character string to be summarized based on the set hash algorithm to obtain a hash value of a fixed length as the data summary.

[0063] Step S230: Sign the data summary to generate signature information.

[0064] Specifically, when signing a data digest, the private key corresponding to a key entity with signing authority is first called upon to perform a digital signature operation on the data digest, generating a signature result corresponding to the data digest. The signature result is then encoded into a specified format and embedded as signature information within the on-chain event data packet. This signature information is used to subsequently verify the identity of the entity that generated the data digest and the authenticity of the data source, ensuring that the on-chain event data has been trustworthy before being submitted to the blockchain network.

[0065] Step S240: Generate a path identifier according to the source process of the settlement transaction data, and perform a hash calculation on the path identifier to obtain a path hash value.

[0066] Among them, the source process can represent the processing flow information of the settlement transaction data before it is generated, transmitted and encapsulated. The processing flow information includes but is not limited to the data generation system identifier, generation timestamp, transmission node identifier, processing module identifier and its sequential path, which is used to characterize the source trajectory and processing path of the transaction data before it is submitted to the chain. The path hash value can represent the path identifier constructed based on the source process, which can be calculated and generated by a hash algorithm. In the specific implementation process, the processing flow information of the settlement transaction data before encapsulation can be first extracted, and the processing flow information can be spliced ​​according to the preset field order to construct a path identification string to characterize the generation and transmission path of the settlement transaction data. Then, the preset hash algorithm is called to perform a digest operation on the path identification string to generate a data output with a fixed length as the path hash value.

[0067] Step S250: Combine the structured data item, data summary, signature information, path hash value and corresponding timestamp into an on-chain event data packet.

[0068] Specifically, according to the preset data structure template, a set of on-chain event data packet fields is constructed. The structured data item is embedded as the main transaction content in the data body field, the data summary is written into the summary field, the signature information is written into the signature field, the path hash value is written into the path traceability field, and the time information of the current encapsulation operation is recorded in the timestamp field. The data of each of the above fields is packaged in a unified format to form an on-chain event data packet, which is then submitted to the consistency verification process before being uploaded to the chain and serves as the original event input for the subsequent clearing process.

[0069] In some embodiments, based on a preset role binding relationship, multiple participating institutions are registered in a multilateral clearing contract respectively, which specifically includes the following technical steps: obtaining the institutional identification and corresponding role information of each participating institution, and constructing a role binding relationship data item according to a preset format; writing the role binding relationship data item into the role mapping table in the multilateral clearing contract to complete the initial role binding operation; receiving a role binding relationship change request, and authenticating the initiator of the change request according to preset authority verification rules; in response to the verification being passed, updating the role mapping table in the multilateral clearing contract according to the change request, and adjusting the role binding relationship of the corresponding institution.

[0070] Among them, the institution identifier can represent the identification information used to uniquely identify the on-chain account of the participating institution. Role information can represent attribute data related to the functions performed by the participating institution in the clearing process. Role information can include role name, authority level, and business scope, etc., which is used to limit the types of operations that the institution can trigger during the contract execution phase. The role binding relationship data item can represent a data unit that combines the institution identifier and the corresponding role information according to a preset field format. The role mapping table can represent a tabular data structure stored in the multilateral clearing contract for recording multiple role binding relationship data items. This data structure can support query, insert, and update operations to maintain the latest correspondence status between each institution and role. Identity verification can represent the verification process of confirming the legitimacy of the initiator of the role binding relationship change request based on preset permission verification rules.

[0071] In this embodiment, by obtaining the institutional identification and corresponding role information of each participating institution, constructing role binding relationship data items and writing them into the role mapping table in the multilateral clearing contract, the identities and functions of participating institutions in the clearing process can be registered on-chain, helping to improve the structured level of role management and access efficiency. Receiving change requests and performing identity verification based on preset permission verification rules, and dynamically updating the role mapping table after verification, ensures controllable changes to role binding relationships and a trustworthy process, thereby enhancing the operational flexibility and permission security of the multi-institution clearing system.

[0072] In some embodiments, a transaction status table between participating institutions is generated based on transaction events, specifically including the following technical steps: configuring a timing dependency identifier for each transaction event, the timing dependency identifier is used to mark the trigger relationship, exclusive relationship or priority execution relationship between the transaction event and at least one related transaction event; based on the timing dependency identifier, a transaction event dependency chain is generated, the dependency chain is used to characterize the execution order of transaction events with dependencies within a settlement cycle; based on the dependency chain, all transaction events are sequentially screened to determine the target transaction event that meets the settlement cycle execution conditions; based on the target transaction event, the receivables and payables of each participating institution are counted to generate a transaction status table.

[0073] Among them, the timing dependency identifier can represent a data field attached to a transaction event that is used to describe the dependency attributes between the event and other transaction events in terms of execution time or logic. The trigger relationship is used to mark that the execution of a certain transaction event is subject to the completion of another transaction event. The exclusive relationship is used to mark that a certain transaction event cannot be executed simultaneously with another event under certain conditions. The priority execution relationship is used to indicate the order of events that need to be processed first when multiple events coexist, and is used to control the processing priority of events within the settlement cycle. The transaction event dependency chain can represent an ordered relationship structure constructed by multiple transaction events with timing dependency identifiers, which can be used to describe the triggering, exclusivity or priority order between each transaction event, so as to form an executable path within the settlement cycle. The target transaction event can represent a set of transaction events that meet the execution conditions and can participate in subsequent settlement calculations after sequential screening based on the dependency chain within the current settlement cycle.

[0074] In this embodiment, by configuring timing dependency identifiers for transaction events and establishing a dependency chain, the execution order between events can be clarified to avoid settlement conflicts caused by sequence errors; based on the dependency chain, target transaction events that meet the settlement conditions are screened out, which can effectively eliminate invalid or conflicting events and improve the accuracy and efficiency of settlement processing; further, a transaction status table is generated based on the target transaction event, which helps to ensure that the statistical results of the receivables and payables relationship are consistent with the business logic and enhance the reliability of the settlement data.

[0075] Exemplarily, all transaction events are sequentially screened based on the dependency chain to determine the target transaction events that meet the execution conditions of the settlement cycle. This can be done through the following steps: based on the transaction event dependency chain, all transaction events are orderly traversed according to a preset topological sorting algorithm or other sequential control logic; during the traversal process, it is determined whether the trigger relationship of each transaction event has been satisfied, whether there is an exclusive conflict with other transaction events, and whether its execution priority meets the processing requirements of the current settlement cycle; if the above conditions are met, the transaction event is marked as a target transaction event and added to the target transaction event set.

[0076] For example, based on a target transaction event, the receivables and payables of each participating institution are counted to generate a transaction status table. This can be accomplished by parsing the target transaction event set item by item, extracting the participant identification and transaction amount information from each transaction event. Using the participant identification as a dimension, the transaction amounts of the payer are counted to form the payable amount, and the transaction amounts of the payee are counted to form the receivable amount. These receivables and payables are aggregated according to the bilateral or multilateral receivables and payables relationships between the institutions to generate a transaction status table between the participating institutions.

[0077] Furthermore, relevant liquidation methods often lack real-time verification of the available funds in an account, which may result in locked or frozen funds being included in liquidation, leading to liquidation failures or abnormal instruction execution. Therefore, by comprehensively assessing account balances, locked and frozen amounts before generating the transaction status table, we can filter out executable transaction events, thereby improving liquidation accuracy and stability.

[0078] Therefore, in some embodiments, generating a transaction status table between participating institutions based on a transaction event may include the following technical steps: obtaining the account address of the participating party corresponding to the transaction event, calling the account balance table on the blockchain, and obtaining the current balance data of the account address; based on the account address, calling the on-chain locked position record to obtain the locked position amount data corresponding to the account address; based on the account address, calling the on-chain fund freeze status table to obtain the frozen amount data corresponding to the account address; judging the execution validity of the corresponding transaction event based on the balance data, locked position amount data and frozen amount data, so as to screen out valid transaction events that meet the execution conditions; based on the valid transaction events, counting the receivables and payables of each participating institution to generate a transaction status table.

[0079] Among them, the on-chain lock-up record can represent a data structure deployed on the blockchain network, used to record the details of funds under a specific account address that are locked and cannot be transferred out under specific periods or conditions. The locked amount data can represent the total amount of locked funds corresponding to a specified account address, extracted from the on-chain lock-up record. This is used to assess the actual available funds of an account before executing a transaction event. The fund freeze status table can represent a tabular data structure recorded on the blockchain network, describing the frozen status of funds corresponding to an account address. The frozen amount data can represent the current frozen funds value associated with a specified account address, extracted from the fund freeze status table. This is used to assist in determining whether the funds meet the transfer conditions when executing a transaction. A valid transaction event can represent a transaction event that meets the execution conditions and can be used as a basis for liquidation within a liquidation cycle, based on the combined assessment of account balance, locked amount, and frozen amount.

[0080] In the specific implementation, the fields in each transaction event are first parsed to extract the payer and beneficiary account addresses. Based on the extracted account addresses, the corresponding entries are queried in the account balance table deployed on the blockchain network to read the current available balance of the account, which is used to assess whether the basic funding conditions are met to support the transaction. Secondly, the lock-up record entry corresponding to the account address is located and the value of the locked funds is extracted. Funds cannot be used for clearing and transfers until the lock-up period expires or the unlocking conditions are met. Next, the freeze information for the corresponding account is retrieved from the fund freeze status table to obtain the frozen funds amount. Frozen funds are temporarily unavailable and cannot participate in transfer operations within the current clearing cycle. Next, the account balance is compared with the locked and frozen amounts to determine whether the account's available funds are greater than or equal to the transaction amount of the transaction event. If so, the transaction event is marked as valid. Finally, all valid transaction events are traversed, and the payable and receivable amounts are calculated based on the payer and beneficiary information. These amounts are then sorted and aggregated by participating institutions to construct a transaction status table for the current clearing cycle.

[0081] In some embodiments, reference Figure 3 As shown in the figure, based on the current status table, the receivables and payables of each participating institution are netted and the target settlement instructions corresponding to each participating institution are obtained. The specific technical steps include the following:

[0082] Step S310: Based on the transaction events recorded in the transaction status table, the transaction events are grouped according to the transaction participant identifiers to generate multiple groups of participant transaction sub-tables.

[0083] The participant transaction subtable can represent a data subset generated by categorizing transaction events recorded in the transaction status table according to the transaction participant identifiers. This subset is used to centrally represent all transaction details involving a specific participant during a settlement cycle. When grouping transaction events, each transaction event in the transaction status table can first be parsed, and the payer and beneficiary identifiers extracted as the participant identifier set for that transaction event. All transaction events are then traversed and categorized according to the participant identifiers, with transaction events containing the same institution identifier grouped into the same logical group. If an institution appears as both the payer and beneficiary in multiple transaction events, all related transactions will be consolidated into the transaction subtable corresponding to that institution, forming a participant transaction subtable with that institution as the dimension. Each generated group of participant transaction subtables includes all transaction records involving that institution during the current settlement cycle.

[0084] Step S320 , performing netting operations in parallel on the transaction events in the transaction sub-tables of the multiple groups of participants, and determining the corresponding sub-clearing instructions for each group.

[0085] Among them, netting calculation can refer to the process of calculating the difference between receipts and payments of a participant's funds transactions during the clearing cycle based on the receivable and payable transaction amounts recorded in a participant's transaction sub-table. Sub-clearing instructions can refer to clearing operation instructions generated based on the netting calculation results of a single participant's transaction sub-table. The instruction can include the clearing direction of the participating institution, that is, collection or payment, netting amount, settlement counterparty identification, and clearing execution status. In this step, by grouping transaction events according to participant identification to generate multiple participant transaction sub-tables, and performing netting calculation operations on each group of data in parallel, the processing efficiency of multi-institution clearing tasks can be significantly improved while maintaining clearing accuracy. Furthermore, corresponding sub-clearing instructions are generated based on the grouping calculation results, which facilitates subsequent unified aggregation and helps to achieve modularization and distributed execution of clearing logic.

[0086] Step S330: Calculate the hash value of the sub-clearing instruction to obtain a corresponding sub-instruction hash value set.

[0087] The sub-instruction hash value set can represent a data set consisting of multiple hash values ​​generated by executing a hash algorithm on each sub-clearing instruction, and the hash value is used to uniquely identify the content status of each sub-clearing instruction. In this step, when performing hash value calculations on the sub-clearing instructions, the sub-clearing instructions generated by multiple groups of participating transaction sub-tables can be first traversed, the field content of each sub-clearing instruction can be formatted and standardized, and a standard data string for hash input can be constructed. Then, a hash calculation is performed on the standard data string based on a preset hash algorithm to obtain a sub-instruction hash value that corresponds one-to-one to the content of the sub-clearing instruction. The hash values ​​corresponding to all sub-clearing instructions are aggregated to form a sub-instruction hash value set.

[0088] Step S340: Send the sub-instruction hash value set to the blockchain network for consistency verification.

[0089] Consistency checking refers to comparing the hash values ​​of the submitted sub-instructions with the reference hash values ​​on the blockchain based on pre-set verification rules to determine whether the clearing instructions are consistent in content, sequence, or quantity. Consistency checking ensures the integrity and consistency of clearing data during multi-party parallel processing.

[0090] Step S350: In response to the verification being qualified, the sub-clearing instructions are aggregated to generate a corresponding target clearing instruction set.

[0091] In some embodiments, based on the target clearing instruction, the funding channel contract bound to the account of each participating institution is called to perform a transfer operation, which specifically includes the following technical steps: writing the target clearing instruction into a preset on-chain confirmation pool, and the on-chain confirmation pool is used to temporarily store a set of clearing instructions to be executed; based on the clearing instruction set, calling the funding channel contract bound to the account of each participating institution, initiating a fund transfer request and recording the execution status; monitoring the execution result of the fund transfer request to determine whether there is a clearing instruction that failed to transfer; in response to detecting at least one clearing instruction that failed to transfer, calling the rollback logic in the clearing contract, canceling the completed fund transfer operation, and restoring each account to the state before the execution of the clearing instruction; in response to the successful execution of all fund transfer requests, marking the clearing instructions in the on-chain confirmation pool as completed, and updating the on-chain clearing result record.

[0092] The on-chain confirmation pool can represent a data storage structure deployed within the blockchain network, used to temporarily store a set of pending target clearing instructions before initiating a funds transfer operation. Rollback logic can represent an exception handling mechanism embedded within the clearing contract. Upon detecting that a funds transfer request corresponding to a portion of the clearing instructions has failed to execute, the rollback logic can automatically undo the completed funds transfer operation and restore the relevant account status to its initial value prior to the execution of the clearing operation. In this embodiment, by temporarily storing clearing instructions in the on-chain confirmation pool and uniformly monitoring their execution status, the rollback logic is triggered upon any transfer failure, undoing the executed operation and restoring the account status, thereby ensuring the atomicity of the clearing process and the consistency of funds processing.

[0093] In some embodiments, the above-mentioned cross-institution collaborative clearing method based on blockchain on-chain state perception may also include the following technical steps: after completing the transfer operation corresponding to the target clearing instruction, obtaining the actual amount received in the account of each participating institution; comparing the actual amount received with the receivable amount and payable amount in the target clearing instruction item by item; in response to any inconsistency in the comparison results, generating an abnormal record and marking the corresponding clearing record as pending verification; outputting a notification instruction containing abnormal information to trigger the clearing alarm process.

[0094] The pending verification status can indicate a status flag attached to a settlement record when the execution result of a target settlement instruction differs from the expected receivable or payable amount during the settlement process. This status indicates that the settlement has not yet been verified, suspending subsequent operations and entering the exception handling process. The settlement alarm process can represent a response mechanism automatically triggered when a discrepancy between the settlement result and the settlement instruction is detected. In this embodiment, after the transfer operation of the target settlement instruction is completed, the actual amount received in each participating institution's account is obtained and compared item by item with the receivable and payable amounts in the settlement instruction. This allows for timely detection of amount discrepancies or abnormalities in the settlement process. Furthermore, when the comparison results are inconsistent, an exception record is generated and the corresponding settlement record is marked as pending verification. This allows for clear identification of abnormal settlement behavior and prevents it from being mistakenly included in subsequent processes as a completed transaction. Furthermore, triggering the settlement alarm process by outputting a notification instruction containing exception information helps the system promptly report abnormalities to the management end, thereby improving the clearing system's responsiveness in fault detection and risk control.

[0095] It should be noted that although the steps of the method disclosed herein are depicted in a particular order in the accompanying drawings, this does not require or imply that the steps must be performed in that particular order, or that all steps must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one, and / or one step may be decomposed into multiple steps.

[0096] In addition, in this exemplary embodiment, a cross-institutional collaborative clearing system based on blockchain state perception is also provided. Figure 4 As shown, the cross-institutional collaborative clearing system 400 based on blockchain state perception may include: an event submission module 410, an institution registration module 420, a state table generation module 430, a net amount calculation module 440, and a transfer operation module 450. Among them:

[0097] The event submission module 410 may be used to submit each settlement transaction as an on-chain event to the blockchain network. The on-chain event may include one or more of the transaction participant identification, transaction amount, transaction time, and transaction type.

[0098] The institution registration module 420 can be used to register multiple participating institutions into a multilateral clearing contract based on a preset role binding relationship. The multilateral clearing contract is deployed on the blockchain network and is used to record the mapping relationship between participating institutions and on-chain events.

[0099] The status table generation module 430 can be used to periodically trigger the multilateral clearing contract, obtain all transaction events recorded on the blockchain during the previous clearing cycle, and generate a transaction status table between participating institutions based on the transaction events;

[0100] The netting calculation module 440 may be used to perform netting calculations on the receivables and payables of each participating institution based on the transaction status table, and obtain target settlement instructions corresponding to each participating institution;

[0101] The transfer operation module 450 can be used to call the fund channel contract bound to the accounts of each participating institution based on the target settlement instruction to perform transfer operations. The fund channel contract is deployed on the blockchain network.

[0102] The specific details of each module of the above cross-institutional collaborative clearing system based on blockchain on-chain state perception have been described in detail in the corresponding cross-institutional collaborative clearing method based on blockchain on-chain state perception, so they will not be repeated here.

[0103] It should be noted that although the detailed description above mentions several modules or units of the cross-institutional collaborative clearing system based on blockchain state perception, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in a single module or unit. Conversely, the features and functions of a single module or unit described above can be further divided and embodied by multiple modules or units.

[0104] In addition, in an exemplary embodiment of the present disclosure, an electronic device is also provided that can implement the above-mentioned cross-institutional collaborative clearing method based on blockchain on-chain status perception.

[0105] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods, or program products. Therefore, various aspects of the present disclosure may be implemented in the following forms: a complete hardware embodiment, a complete software embodiment (including firmware, microcode, etc.), or an embodiment combining hardware and software aspects, which may be collectively referred to herein as a "circuit," "module," or "system."

[0106] Refer to the following Figure 5 hereinafter, an electronic device 500 according to such an embodiment of the present disclosure is described. Figure 5 The electronic device 500 shown is merely an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0107] like Figure 5As shown, electronic device 500 is implemented as a general-purpose computing device. Components of electronic device 500 may include, but are not limited to, the aforementioned at least one processing unit 510, the aforementioned at least one storage unit 520, a bus 530 connecting various system components (including storage unit 520 and processing unit 510), and a display unit 540.

[0108] The storage unit stores program code, which can be executed by the processing unit 510, so that the processing unit 510 performs the steps described in the "Exemplary Methods" section above according to various exemplary embodiments of the present disclosure. The storage unit 520 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 521 and / or a cache memory unit 522, and may further include a read-only memory unit (ROM) 523.

[0109] The storage unit 520 may also include a program / utility 524 having a set (at least one) of program modules 525, such program modules 525 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0110] Bus 530 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0111] The electronic device 500 can also communicate with one or more external devices 570 (e.g., a keyboard, a pointing device, a Bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 500, and / or any device that enables the electronic device 500 to communicate with one or more other computing devices (e.g., a router, a modem, etc.). Such communication can occur via an input / output (I / O) interface 550. Furthermore, the electronic device 500 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network such as the Internet) via a network adapter 560. As shown, the network adapter 560 communicates with other modules of the electronic device 500 via a bus 530. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 500, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0112] Through the description of the above embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by combining software with necessary hardware.

[0113] In exemplary embodiments of the present disclosure, a computer-readable storage medium is also provided, on which is stored a program product capable of implementing the aforementioned methods of this specification. In some possible embodiments, various aspects of the present disclosure may also be implemented in the form of a program product, which includes program code. When the program product is executed on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary embodiments of the present disclosure described in the "Exemplary Methods" section of this specification.

[0114] refer to Figure 6 As shown, a program product 600 for implementing the above-mentioned cross-institutional collaborative clearing method based on blockchain state perception according to an embodiment of the present disclosure is described. The program product 600 can be a portable compact disc read-only memory (CD-ROM) and includes program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0115] The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0116] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0117] Furthermore, the figures above are merely illustrative of the processes included in the methods according to exemplary embodiments of the present disclosure and are not intended to be limiting. It is readily understood that the processes illustrated in the figures above do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0118] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A cross-institutional collaborative clearing method based on blockchain state perception, characterized in that: include: Submitting each settlement transaction as an on-chain event to the blockchain network, where the on-chain event includes one or more of the transaction participant identification, transaction amount, transaction time, and transaction type; Based on a preset role binding relationship, multiple participating institutions are registered in a multilateral clearing contract. The multilateral clearing contract is deployed on the blockchain network and is used to record the mapping relationship between the participating institutions and the on-chain events; Periodically triggering the multilateral clearing contract to obtain all transaction events recorded on the blockchain during the previous clearing cycle, and generating a transaction status table between each of the participating institutions based on the transaction events; Based on the transaction status table, netting the receivables and payables of each participating institution to obtain a target settlement instruction corresponding to each participating institution; Based on the target clearing instruction, a fund channel contract bound to the account of each participating institution is called to perform a transfer operation, and the fund channel contract is deployed on the blockchain network.

2. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 1 is characterized in that: Submitting each settlement transaction to the blockchain network as an on-chain event includes: The submitted settlement transaction data is structured and encapsulated to obtain an on-chain event data packet; Perform consistency verification on the signature information and data summary in the on-chain event data; In response to the verification being passed, the on-chain event data packet is submitted to the blockchain network and recorded as the on-chain event that can participate in the liquidation process.

3. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 2 is characterized in that: The settlement transaction data to be submitted is structurally encapsulated to obtain an on-chain event data packet, including: Extracting the participant identification, transaction amount, transaction time, and transaction type from the settlement transaction data, and performing standardization processing to generate corresponding structured data items; Performing digest calculation on the structured data item to obtain a data digest for integrity verification; Performing signature processing on the data summary to generate signature information; Generate a path identifier according to the source process of the settlement transaction data, and perform a hash calculation on the path identifier to obtain a path hash value; The structured data item, the data summary, the signature information, the path hash value and the corresponding timestamp are combined into the on-chain event data packet.

4. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 1 is characterized in that: Based on the preset role binding relationship, multiple participating institutions are registered in the multilateral clearing contract, including: Obtain the organization identification and corresponding role information of each participating organization, and construct role binding relationship data items according to the preset format; Writing the role binding relationship data item into the role mapping table in the multilateral clearing contract to complete the initial role binding operation; Receive role binding change requests and authenticate the initiator of the change request based on preset permission verification rules; In response to the verification being passed, the role mapping table in the multilateral clearing contract is updated according to the change request, and the role binding relationship of the corresponding institution is adjusted.

5. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 1 is characterized in that: The generating of the transaction status table between the participating institutions based on the transaction event includes: Configuring a timing dependency identifier for each transaction event, wherein the timing dependency identifier is used to mark a trigger relationship, an exclusive relationship, or a priority execution relationship between the transaction event and at least one associated transaction event; Based on the timing dependency identifier, a transaction event dependency chain is generated, where the dependency chain is used to represent the execution order of transaction events with dependencies within a clearing cycle; Sequentially screening all transaction events based on the dependency chain to determine target transaction events that meet the clearing cycle execution conditions; Based on the target transaction event, the receivable amount and payable amount of each participating institution are counted to generate the transaction status table.

6. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 1 is characterized in that: The generating of the transaction status table between the participating institutions based on the transaction event includes: Obtain the account address of the participant corresponding to the transaction event, call the account balance table on the blockchain, and obtain the current balance data of the account address; Based on the account address, call the on-chain lock-up record to obtain the lock-up amount data corresponding to the account address; Based on the account address, call the on-chain fund freeze status table to obtain the frozen amount data corresponding to the account address; Determining the execution validity of corresponding transaction events based on the balance data, the locked amount data, and the frozen amount data, so as to screen out valid transaction events that meet the execution conditions; Based on the valid transaction events, the receivable amounts and payable amounts of each participating institution are counted to generate the transaction status table.

7. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 1 is characterized in that: Based on the transaction status table, the net amount of the receivable amount and the payable amount of each participating institution is calculated to obtain the target settlement instruction corresponding to each participating institution, including: Based on the transaction events recorded in the transaction status table, the transaction events are grouped according to the transaction participant identifiers to generate multiple groups of participant transaction sub-tables; Performing netting operations in parallel on the transaction events in the transaction sub-tables of the multiple groups of participants, respectively, to determine the corresponding sub-clearing instructions for each group; Performing hash value calculation on the sub-clearing instruction to obtain a corresponding sub-instruction hash value set; Sending the sub-instruction hash value set to the blockchain network for consistency verification; In response to the verification being qualified, the sub-clearing instructions are aggregated to generate the corresponding target clearing instruction set.

8. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 1 is characterized in that: The target liquidation instruction is based on calling the fund channel contract bound to the account of each participating institution to perform the transfer operation, including: Writing the target liquidation instruction into a preset on-chain confirmation pool, which is used to temporarily store a set of liquidation instructions to be executed; Based on the liquidation instruction set, call the funding channel contract bound to each participating institution account, initiate a fund transfer request and record the execution status; Monitoring the execution result of the fund transfer request to determine whether there is a clearing instruction resulting in a failed transfer; In response to detecting at least one failed liquidation instruction, invoke the rollback logic in the liquidation contract to undo the completed fund transfer operation and restore each account to the state before the liquidation instruction was executed; In response to all fund transfer requests being successfully executed, the clearing instructions in the on-chain confirmation pool are marked as completed, and the on-chain clearing result record is updated.

9. The cross-institutional collaborative liquidation method based on blockchain state perception according to claim 1 is characterized in that: Also includes: After completing the transfer operation corresponding to the target clearing instruction, obtain the actual amount received in the account of each participating institution; Compare the actual amount received with the receivable amount and payable amount in the target liquidation instruction item by item; In response to any inconsistency in the comparison results, an exception record is generated and the corresponding liquidation record is marked as pending verification; Output notification instructions containing abnormal information to trigger the liquidation alarm process.

10. A cross-institutional collaborative clearing system based on blockchain state perception, characterized by: include: An event submission module, configured to submit each settlement transaction as an on-chain event to the blockchain network, wherein the on-chain event includes one or more of the transaction participant identification, transaction amount, transaction time, and transaction type; An institution registration module, configured to register multiple participating institutions into a multilateral clearing contract based on a preset role binding relationship. The multilateral clearing contract is deployed on the blockchain network and is configured to record the mapping relationship between the participating institutions and the on-chain events. A status table generation module, configured to periodically trigger the multilateral clearing contract, obtain all transaction events recorded on the blockchain during the previous clearing cycle, and generate a transaction status table between each of the participating institutions based on the transaction events; a netting calculation module, configured to perform netting calculations on the receivables and payables of each participating institution based on the transaction status table, and obtain a target settlement instruction corresponding to each participating institution; A transfer operation module is used to call the funding channel contract bound to the accounts of each participating institution based on the target settlement instruction to perform a transfer operation, and the funding channel contract is deployed on the blockchain network.

Images