Real estate registration management transaction method and system based on block chain
By linking the passive RFID electronic tag code with the rights holder's identity certificate and storing it on the blockchain in the real estate management system, the system obtains and transforms ownership change time-series data. Combined with distributed identity authentication and smart contracts, it solves the problems of data tampering and identity verification disconnect in centralized storage, and realizes automated, secure and efficient management of real estate transactions.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- 宁夏回族自治区自然资源和不动产确权登记中心
- Filing Date
- 2025-12-01
- Publication Date
- 2026-05-01
AI Technical Summary
Existing real estate management systems rely on centralized storage, which poses a risk of data tampering, disconnects identity authentication from property rights verification, results in long transaction cycles and high costs, makes it difficult to prevent fraud, and struggles to handle complex ownership relationships.
By linking the passive RFID electronic tag code with the rights holder's distributed identity certificate and storing it on the blockchain during the initial registration stage, the time-series data of ownership changes is obtained and transformed into a spatiotemporal graph. Distributed identity authentication technology is used to authenticate the identities of both parties in the transaction, and ownership verification is carried out based on blockchain smart contracts, thereby realizing the transfer of transaction funds and the updating of ownership information.
Ensure that the source data of ownership is tamper-proof, enhance the structured and dynamic traceability of historical records, strengthen the logical connection between the transaction entity and historical ownership, realize the automated driving and status synchronization of the transaction process, reduce the risk of human intervention, and improve the transparency, security and efficiency of transactions.
Smart Images

Figure CN121961574A_ABST
Abstract
Description
A blockchain-based method and system for real estate registration management transactions Technical Field
[0001] This application relates to the field of transaction management technology, and in particular to a blockchain-based method and system for real estate registration management transactions. Background Technology
[0002] With the continuous advancement of urbanization and the ongoing development of the real estate transaction market, higher demands are being placed on the transparency, security, and efficiency of real estate registration and transaction management. In practical application scenarios, real estate, as a high-value asset, involves multiple parties in its ownership transfer, including property owners, intermediary agencies, financial institutions, and regulatory departments responsible for managing transactions and technology.
[0003] Existing real estate management systems combine centralized databases with digital certificate authentication. They record ownership changes through a unified electronic platform, assign unique identifiers to real estate, and encrypt and store transaction history. During transactions, identity verification relies on the certificate issuing authority system, supplemented by manual or semi-automatic comparison of property records. Once confirmed, the transfer approval process is initiated. However, existing solutions rely on centralized storage, which carries the risk of data tampering or loss. Ownership history verification depends on fixed rules, making it difficult to handle complex ownership relationships. The disconnect between identity authentication and property verification can easily create vulnerabilities in scenarios such as inheritance and mortgages. Fund transfers and property changes require manual approval, resulting in long transaction cycles, high costs, and difficulty in preventing fraudulent activities such as selling the same property multiple times. Overall, the security and efficiency are insufficient. Summary of the Invention
[0004] The purpose of this application is to provide a blockchain-based method and system for real estate registration management transactions, in order to solve the security and efficiency problems caused by the ease of tampering with centralized storage, rigid ownership verification, and disconnect between production and finance processes in existing technologies.
[0005] To address the aforementioned technical problems, firstly, this application provides a blockchain-based method for real estate registration management and transactions, comprising:
[0006] The passive radio frequency identification (RFID) electronic tag of the real estate is obtained during the initial registration process, and the real estate code in the passive RFID electronic tag is associated with the distributed identity certificate of the real estate owner to obtain the associated data, and the associated data is transmitted to the blockchain network for evidence storage;
[0007] When real estate enters the second-hand transaction process, and the radio frequency identification reader reads the real estate code, it obtains the ownership change time sequence data corresponding to the real estate.
[0008] The ownership change time series data is verified, and when the verification passes, the ownership change time series data is converted into a spatiotemporal map;
[0009] The identities of both parties in a second-hand real estate transaction are verified using distributed identity authentication technology, generating the identity authentication results for both parties. The identity authentication results are then compared with the historical rights holder information of the real estate in the spatiotemporal map to obtain the ownership comparison results.
[0010] Based on the ownership comparison results and the smart contracts in the blockchain network, the ownership restrictions of real estate are verified to obtain the verification results. Based on the verification results, the transaction funds are transferred and the ownership information is updated to realize the full-chain registration management of real estate secondary transactions.
[0011] Secondly, this application provides a blockchain-based method and system for real estate registration management transactions, including:
[0012] The association module is used to obtain the passive radio frequency identification electronic tag of the real estate during the initial registration process, associate the real estate code in the passive radio frequency identification electronic tag with the distributed identity certificate of the real estate owner to obtain association data, and transmit the association data to the blockchain network for storage.
[0013] The acquisition module is used to acquire the ownership change time sequence data corresponding to the real estate when the real estate enters the second-hand transaction process and the radio frequency identification reader reads the real estate code.
[0014] The conversion module is used to verify the ownership change time series data. When the verification is successful, the ownership change time series data is converted into a spatiotemporal map.
[0015] The authentication module is used to authenticate the identities of both parties in a second-hand real estate transaction through distributed identity authentication technology, generate the identity authentication results of both parties, and compare the identity authentication results with the historical rights holder information of the real estate in the spatiotemporal map to obtain the ownership comparison results.
[0016] The verification module is used to verify the ownership restrictions of real estate based on the ownership comparison results and smart contracts in the blockchain network, obtain the verification results, and perform transaction fund transfer and ownership information update operations based on the verification results, so as to realize the full-chain registration management of real estate secondary transactions.
[0017] Thirdly, this application provides an electronic device, comprising:
[0018] Memory, used to store computer programs;
[0019] A processor is configured to execute the computer program to implement the steps of a blockchain-based real estate registration management transaction method as described in the first aspect above.
[0020] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps of a blockchain-based real estate registration management transaction method as described in the first aspect above.
[0021] The blockchain-based real estate registration management and transaction method provided in this application achieves a reliable anchoring of physical assets and digital identities by linking and storing the passive RFID electronic tag code of the real estate with the distributed identity certificate of the right holder on the blockchain during the initial registration stage, thus ensuring the authenticity and immutability of the source data of ownership. In the secondary transaction stage, the method obtains the time-series data of ownership change of the real estate by reading the electronic tag and transforms it into a spatiotemporal map, thereby improving the structuring and visualization of historical records and enhancing the dynamic tracing ability of complex ownership evolution paths.
[0022] By utilizing distributed identity authentication technology to verify the identities of both parties in a transaction and comparing the authentication results with historical rights holder information in a spatiotemporal graph, the disconnect between identity authentication and property rights verification is bridged, strengthening the logical connection between the transaction entity and the historical ownership chain. Based on the consistency comparison results, the blockchain smart contract collaboratively executes the ownership restriction verification, and automatically triggers the transfer of transaction funds and the update of ownership information. This achieves the coordinated execution and state synchronization of key operations in the transaction process, improving the automation level and execution efficiency of the transaction process, and reducing the operational risks and time costs caused by human intervention.
[0023] Furthermore, by extracting matching identifiers of the transacting parties and historical rights holders from the ownership comparison results, and combining them with their corresponding identities and registration validity periods, accurate identification of the timeliness of the subject's qualifications is achieved. Ownership restriction records stored on the blockchain are categorized by type, and based on various verification rules preset in the smart contract, the restriction statuses such as mortgages, seizures, objections, and pre-registrations are automatically judged. The final verification conclusion is generated by integrating the results of these judgments, thus constructing a dynamic ownership restriction review mechanism. By combining the categorized management of ownership restrictions with time-based smart rule judgments, a refined and automated review of multiple rights burdens such as mortgages, seizures, objections, and pre-registrations is achieved. Relying on trusted data on the blockchain and the deterministic execution of smart contracts, the transparency, consistency, and unavoidability of the verification process are ensured, improving the ability to identify potential transaction obstacles and response speed, and guaranteeing the accuracy and security of transaction decisions. Attached Figure Description
[0024] To more clearly illustrate the technical solutions of the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0025] Figure 1 is a schematic flowchart of a blockchain-based real estate registration management transaction method provided in an embodiment of this application;
[0026] Figure 2 is a schematic diagram illustrating a specific implementation of a blockchain-based real estate registration management transaction method provided in an embodiment of this application;
[0027] Figure 3 is a schematic diagram of the structure of a blockchain-based real estate registration management and transaction system provided in an embodiment of this application. Detailed Implementation
[0028] To address the problems of existing real estate management systems, such as difficulty in ensuring data security due to reliance on centralized storage, lack of subject correlation due to separation of identity authentication and property rights verification, rigid historical ownership verification methods that cannot cope with complex transfer relationships, and excessive manual intervention and low degree of automation in the transaction execution process;
[0029] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0030] The core of this application is to provide a blockchain-based method for real estate registration management and transactions. A flowchart of one specific implementation is shown in Figure 1. The method includes:
[0031] Step 101: Obtain the passive RFID electronic tag of the real estate during the initial registration process, associate the real estate code in the passive RFID electronic tag with the distributed identity certificate of the real estate owner to obtain the associated data, and transmit the associated data to the blockchain network for storage.
[0032] In this step, the initial registration process refers to the procedure for applying for property registration with the statutory registration authority for the first time. Passive RFID tags refer to passive RFID tags with a built-in unique property code, which are usually attached to the property ownership certificate or physical identification of the property. The property code refers to a unique combination of numbers or characters assigned to the property by the registration authority according to uniform rules. Distributed identity credentials refer to decentralized digital credentials issued without relying on a centralized institution to identify the identity of the right holder. Associated data refers to the combined data formed by associating the property code with the distributed identity credential of the property owner through data mapping operations.
[0033] In this embodiment of the application, when the real estate is initially registered, a passive radio frequency identification electronic tag attached to the relevant carrier of the real estate is obtained through radio frequency identification technology, and a unique real estate code is extracted from the tag; then, the real estate code is associated with the distributed identity certificate of the real estate owner through a data association mapping operation to form associated data including the correspondence between the real estate code and the identity of the owner; finally, the associated data is transmitted to the blockchain network, and the distributed storage characteristics of the blockchain are used to complete the evidence storage.
[0034] Step 102: When the real estate enters the second-hand transaction process, and the radio frequency identification reader reads the real estate code, the corresponding ownership change time sequence data of the real estate is obtained.
[0035] In this step, the ownership change time series data refers to the dataset that records the ownership changes and registration status changes of real estate in chronological order.
[0036] Step 103: Verify the ownership change time series data. When the verification passes, convert the ownership change time series data into a spatiotemporal map.
[0037] In this step, the spatiotemporal graph refers to the graph structure of real estate data, which presents the time-series data of ownership changes in terms of nodes and the relationships between nodes.
[0038] In this embodiment of the application, the ownership change time series data is first verified. The verification content includes the integrity of the data fields and the consistency between the data and the initial associated data that has been stored in the blockchain. After the verification is passed, the time series data is transformed into a spatiotemporal map according to the time dimension, the right holder dimension, the registration status dimension, and the location association dimension.
[0039] Step 104: Using distributed identity authentication technology, authenticate the identities of both parties in the real estate secondary transaction, generate the identity authentication results of both parties, and compare the identity authentication results with the real estate historical rights holder information in the spatiotemporal map to obtain the ownership comparison results.
[0040] In this step, the identity verification results of both parties refer to the conclusion reached after verifying the authenticity of the buyer's and seller's identities in a secondary real estate transaction. Real estate historical rights holder information refers to data recording the identity information of all previous legal owners of the real estate, the start and end dates of their ownership holdings, and the chronological data of ownership changes. The ownership comparison results refer to the conclusion that determines whether the association between the identities of both parties and the real estate historical rights holder information is legal.
[0041] In this embodiment of the application, distributed identity authentication technology is used to authenticate the identities of both parties in a second-hand real estate transaction, generate the identity authentication results of both parties, and perform field matching and comparison with the information of the historical rights holders of the real estate in the spatiotemporal map to determine the legality of the association between the two parties and the historical rights holders, and obtain the ownership comparison results.
[0042] Step 105: Based on the ownership comparison results and the smart contract in the blockchain network, the ownership restriction verification of the real estate is carried out to obtain the verification results. Based on the verification results, the transaction funds are transferred and the ownership information is updated to realize the full-chain registration management of real estate secondary transactions.
[0043] In this step, the verification result refers to the verification conclusion and ownership comparison result regarding whether the real estate currently has any ownership restrictions such as mortgage, seizure, objection, or pre-announcement.
[0044] This application utilizes passive radio frequency identification (RFID) technology to uniquely bind the physical entity of real estate with its digital information. During the initial registration phase, the asset code and the rights holder's distributed identity certificate are linked and stored on the blockchain, ensuring the immutability of the original ownership data. In secondary transactions, complete ownership change timeline data is obtained by reading electronic tags and transformed into a spatiotemporal graph, enhancing the structured representation and dynamic traceability of historical records. Distributed identity authentication is used to reliably verify the identities of both parties in the transaction, comparing them against historical rights holder information in the spatiotemporal graph to strengthen the logical connection between the transaction entity and the asset's history. Blockchain smart contracts are used to collaboratively complete ownership restriction reviews and link fund transfers with ownership information updates, achieving automated driving and state coordination throughout the entire transaction process. This approach avoids the risk of data tampering in centralized storage, solves the problem of tracing complex ownership relationships, fills the gap between identity and property rights verification, shortens the transaction cycle, reduces costs, prevents fraud, and improves the transparency, security, and efficiency of real estate registration and transactions.
[0045] This application provides a specific embodiment. Step 102, when the real estate enters the second-hand transaction process and the RFID reader reads the real estate code, obtains the ownership change time sequence data corresponding to the real estate, specifically including the following steps:
[0046] Step 201: When the real estate enters the second-hand transaction process, and the RFID reader reads the real estate code, a trigger command is generated based on the real estate code and the reader device identifier.
[0047] In this step, the reader device identifier refers to the unique identification code of the RFID reader. The trigger command refers to the structured data command used to initiate the real estate history query process.
[0048] In this embodiment of the application, when real estate enters the second-hand transaction process, after the RFID reader reads the real estate code in the passive RFID electronic tag of the real estate, it obtains the reader device identifier of the reader itself; then, according to the preset data format, the real estate code and the reader device identifier are combined into fields, and an operation timestamp is added to generate a trigger instruction for triggering subsequent data queries.
[0049] Step 202: Send the trigger command to the access verification node of the blockchain network. The access verification node performs permission verification on the reader device identifier and generates a permission verification result. If the permission verification result is that the permission verification is successful, then send the trigger command to multiple cross-department nodes in the blockchain network. The cross-department nodes include the real estate initial registration department node, the ownership change registration department node, the transaction filing department node, and the tax registration department node.
[0050] In this step, the access verification node refers to the node in the blockchain network responsible for device access verification. The authorization verification result refers to the conclusion regarding the operational qualifications of the accessed device. Cross-departmental nodes refer to information storage and processing nodes belonging to different government departments in the blockchain network. The initial real estate registration department node refers to the blockchain node belonging to the competent authority for initial real estate registration. The ownership change registration department node refers to the blockchain node belonging to the competent authority for ownership change registration. The transaction filing department node refers to the blockchain node belonging to the competent authority for real estate transaction filing. The tax registration department node refers to the blockchain node belonging to the competent authority for taxation.
[0051] In this embodiment, the trigger command is sent to the access verification node through the communication interface of the blockchain network. The access verification node calls the pre-stored device permission list, which includes all authorized and registered reader device identifiers and their corresponding permission ranges. The reader device identifier in the trigger command is compared with the authorized identifiers in the list one by one. If the result is that the permission verification is successful, the access verification node forwards the trigger command to multiple cross-department nodes in the blockchain network through the node communication link of the blockchain.
[0052] If, after comparison, it is found that the reader device identifier in the trigger command does not appear in the pre-stored device permission list, or if the identifier is in the device permission list but the corresponding permission does not include triggering real estate history query, the access verification node generates a permission verification failure result including the reason for failure. Subsequently, the access verification node feeds back the permission verification failure result to the operation terminal corresponding to the reader that initiated the trigger command through the original communication link. At the same time, the permission verification failure result, the corresponding operation timestamp, and the reader device identifier are synchronously transmitted to the blockchain network for notarization, and the process of obtaining the ownership change time series data is terminated. When the process of obtaining the ownership change time series data is terminated due to permission verification failure, the operation terminal will receive the permission verification failure result and reason fed back by the access verification node, and display specific prompt information to the staff through the interface. At the same time, the blockchain network will permanently store the record of this unauthorized operation.
[0053] Because the ownership change time series data was not successfully obtained, subsequent steps such as verifying the ownership change time series data, converting it into a spatiotemporal map, and comparing identity authentication results could not be executed. The real estate second-hand transaction process was suspended. After the staff resolved the equipment authorization issue according to the specific prompts, they will re-use the authorized RFID reader to read the real estate code and re-trigger the ownership change time series data acquisition process until the data is successfully obtained, and then continue to execute the subsequent steps.
[0054] Step 203: After each cross-department node receives the trigger instruction, it queries the target historical records related to the real estate based on the real estate code. The target historical records include information on changes in the right holder of the real estate, information on changes in registration status, and the number of the change approval document corresponding to different timestamps.
[0055] In this step, "Change of Ownership Information" refers to the data recording the change of the real estate owner from the original entity to a new entity. "Change of Registration Status Information" refers to the information recording changes in the real estate registration status. "Change Approval Document Number" refers to the unique number of the document issued by the approval department each time ownership or status of the real estate changes.
[0056] In this embodiment, after receiving the trigger command, each cross-department node parses the real estate code in the trigger command and uses the real estate code as the search keyword to query the target historical records related to the real estate in the database of its respective cross-department node. Specifically, this includes: querying the initial registration records in the real estate initial registration department node, querying the previous transfer records in the ownership change registration department node, querying the transaction filing information in the transaction filing department node, and querying the tax payment records in the tax registration department node. These records all include the real estate right holder change information, registration status change information, and change approval document number corresponding to different timestamps.
[0057] Step 204: Add a node identifier to the target history record to form an identified history record, and transmit the identified history record to the aggregation node of the blockchain network.
[0058] In this step, the node identifier refers to a unique code used to distinguish different cross-departmental nodes. The aggregation node refers to the core node in the blockchain network responsible for integrating data from multiple departments.
[0059] In this embodiment, a node identifier is added to the header or tail field of the target historical record obtained from the query, and the node identifier is integrated with the target historical record to form an identified historical record; then, the identified historical record is synchronously transmitted to the aggregation node in the blockchain network responsible for data aggregation through the encrypted transmission channel of the blockchain.
[0060] Step 205: After the aggregation node receives the identified historical records transmitted by each cross-department node, it compares the content of different identified historical records corresponding to the same timestamp, generates a content comparison result, and performs integrity verification on the identified historical records, generating an integrity verification result.
[0061] In this step, the content comparison result refers to the conclusion on the degree of matching between the content of records from different cross-department nodes at the same timestamp. The integrity verification result refers to the conclusion on the inspection of missing mandatory fields in the identified historical records.
[0062] In this embodiment, after receiving the identified historical records from all cross-departmental nodes, the aggregation node compares the core content such as the change of rights holder and the change of registration status from different nodes under the same timestamp, determines whether they are consistent, and generates a content comparison result; it also checks whether each identified historical record is missing any required fields and generates an integrity verification result.
[0063] Step 206: Based on the integrity verification result and the content comparison result, classify the identified historical records to obtain a list of valid historical records, a list of conflicting records, a list of incomplete records, and a list of invalid records.
[0064] In this embodiment of the application, the identified historical records are classified based on the integrity verification results and content comparison results: those that pass both consistency comparison and integrity verification are classified as valid historical records; those with inconsistent content under the same timestamp are classified as conflict record lists; those with missing required fields are classified as incomplete record lists; and those that are both incomplete and conflicting are classified as invalid record lists, resulting in four types of record sets.
[0065] Step 207: Calibrate the timestamps in the valid historical records to obtain calibrated timestamps. Based on the calibrated timestamps, integrate the valid historical records, conflict record list, incomplete record list, invalid record list, node identifiers, and change approval document numbers to form ownership change time sequence data.
[0066] In this embodiment, the timestamps in the valid historical records are compared with the standard time in the blockchain network to adjust the timestamps with large deviations to obtain calibrated timestamps. Based on the calibrated timestamps, the valid historical records, conflict record lists, incomplete record lists, invalid record lists, node identifiers corresponding to each record, and change approval document numbers are structured and integrated, and arranged in chronological order to form complete ownership change time sequence data.
[0067] The embodiments of this application ensure the security and collaboration of data queries, achieve full-dimensional ownership data coverage, and enable efficient cross-departmental data collaboration, thereby improving the integrity and credibility of ownership data.
[0068] This application provides a specific embodiment. Step 103, when the verification passes, converts the ownership change time series data into a spatiotemporal map, specifically including the following steps:
[0069] Step 301: When the verification is successful, the core dimensions of the spatiotemporal map are determined based on the ownership change time series data. The core dimensions include the time dimension, the right holder dimension, the registration status dimension, and the location association dimension.
[0070] In this step, the core dimension refers to the key information categories that need to be covered when constructing the spatiotemporal map, namely, the time-series data of ownership changes. The time dimension refers to the dimension that records changes in real estate information based on time. The rights holder dimension refers to the dimension that records ownership changes with the rights holder at its core. The registration status dimension refers to the dimension that records restrictions on rights based on the registration status. The location association dimension refers to the dimension that records the spatial associations of real estate based on location information.
[0071] In this embodiment of the application, after the verification of the ownership change time series data is passed, the time series data is subjected to structured analysis to extract the most critical information categories, thereby determining the core dimensions for constructing the spatiotemporal map. These core dimensions specifically include the time dimension, the rights holder dimension, the registration status dimension, and the location association dimension, to ensure that the subsequent map construction can cover all elements of real estate information.
[0072] Step 302: Based on the core dimensions, create a time node for each calibrated timestamp, a rights holder node for each rights holder change information, a status node for each registration status change information, and a location association node for the real estate location association information corresponding to the change approval document number.
[0073] In this step, a time node refers to a graph node representing a specific point in time. A rights holder node refers to a graph node representing information about a rights holder. A status node refers to a graph node representing the time-series data of ownership changes for a specific registration status. Real estate location association information refers to spatial information related to the location of real estate, including address, survey coordinates, and relationships with adjacent real estate. Location association nodes refer to graph nodes representing real estate location association information.
[0074] In this embodiment, based on the core dimension, the specific information in the ownership change time series data is processed into nodes. The specific processing includes: generating a time node including specific time information for each calibrated timestamp; generating a rights holder node including the rights holder's identity and the reason for the change for each piece of rights holder change information; generating a status node including the status type and the change time for each piece of registration status change information; and generating a location association node including location details for the real estate location association information corresponding to the change approval document number, so that various types of information are presented independently in the form of nodes.
[0075] Step 303: Establish association relationships among time nodes, rights holder nodes, status nodes, and location-related nodes under the same calibrated timestamp to form basic association units.
[0076] In this step, the association relationship refers to the logical connection between nodes under the same timestamp. The basic association unit refers to an information unit composed of time nodes, rights holder nodes, status nodes, location association nodes, and association relationships under the same timestamp.
[0077] In this embodiment, time nodes, rights holder nodes, status nodes, and location-related nodes belonging to the same calibrated timestamp are selected. Through data field matching, for example, an association identifier is added between nodes that all include the same calibrated timestamp. These interconnected nodes are then integrated into an indivisible basic association unit to fully reflect the comprehensive information of real estate at a certain moment.
[0078] Step 304: Establish a supplementary association relationship between the list nodes corresponding to each timestamp in the conflict record list, incomplete record list, and invalid record list, and the time nodes corresponding to the calibrated timestamps in the basic association unit.
[0079] In this step, a list node refers to a graph node representing a record corresponding to a specific timestamp in a list of conflicting, incomplete, or invalid records. Supplementary associations refer to the logical connections between list nodes and their corresponding time-based association units.
[0080] In this embodiment of the application, a corresponding list node is created for the timestamp of each record in the conflict record list, the incomplete record list, and the invalid record list. The list node includes the list type and a record content summary. Then, by timestamp matching, the time node corresponding to the calibrated timestamp that is consistent with the timestamp of the list node in the basic association unit is found, and a supplementary association identifier is added between the two nodes to establish a supplementary association relationship, so that the problem record is associated with the valid information of the corresponding time.
[0081] Step 305: Connect all basic association units and the supplementary association relationships in series to form a spatiotemporal map.
[0082] In this embodiment of the application, all basic association units are sequentially connected in the order of the calibrated timestamps. For example, the time node of the previous unit is connected to the time node of the next unit through a time progression identifier. At the same time, each supplementary association is attached to the corresponding basic association unit. For example, the supplementary association of the conflict list node points to the basic association unit of the corresponding time. Finally, a complete spatiotemporal map is formed, including time flow, rights holder change, status change, location association and problem record supplement.
[0083] This application embodiment, by forming a spatiotemporal map, makes the history of real estate ownership more intuitive, facilitates the rapid tracing of complex ownership relationships, improves the efficiency and accuracy of data verification, and provides a clear basis for transaction verification.
[0084] This application provides a specific embodiment, as shown in Figure 2. Step 104 involves using distributed identity authentication technology to authenticate the identities of both parties in a second-hand real estate transaction and generating the authentication results for both parties. This specifically includes the following steps:
[0085] Step 401: Integrate the distributed identity credentials and additional identity information submitted by both parties to the transaction into an identity authentication request, and send the identity authentication request to multiple identity verification nodes in the blockchain network.
[0086] In this step, distributed identity credentials refer to decentralized digital credentials issued by a non-centralized institution to identify the identities of both parties in a transaction. Distributed identity credentials include unique identification codes, digital signatures, and validity periods for both parties. Additional identity information refers to supplementary materials submitted by both parties to aid in identity verification, including supplementary identity documents and transaction authorization letters. An identity authentication request refers to structured request data formed by integrating the distributed identity credentials and additional identity information of both parties according to a preset data format. The identity authentication request includes core credential information, a summary of additional information, and a request timestamp. Identity verification nodes refer to nodes in the blockchain network responsible for the initial verification of the identities of both parties. Identity verification nodes include government nodes with identity verification qualifications and third-party verification nodes.
[0087] In this embodiment, the paper copies of the distributed identity certificates and the electronic copies of the identity supplementary information submitted by the buyer and seller at the transaction service window are obtained respectively. Then, the identity request generation module of the blockchain transaction system integrates the obtained data into a structured identity authentication request according to the preset format of certificate information area - supplementary information area - request metadata area.
[0088] The specific integration process includes: filling in key fields such as the unique identity code and digital signature validity period in the credential information area; associating the storage path and digest value of the additional information in the additional information area; generating a unique request number and submission time in the request metadata area; and pushing the identity authentication request to the receiving port of the registered identity verification node in the blockchain network through the node communication interface.
[0089] Step 402: After confirming that each identity verification node has received the identity authentication request, extract the target identity information from the distributed identity credential and the identity identifier from the identity attachment information, and associate the target identity information with the associated data stored in the blockchain network to obtain the association relationship.
[0090] In this step, the target identity information refers to the key information extracted from the distributed identity credential that uniquely identifies the identity of the transaction entity. This target identity information includes identity fingerprint features, unique identity code fragments, and digital signature features. The identity identifier refers to the identifying information extracted from the identity supplementary information that assists in confirming the identity of the transaction entity. The identity identifier includes the transaction entity's name / title, document number, and contact identifier. The association relationship refers to the conclusion obtained after matching the target identity information with the associated data stored in the blockchain network. The association relationship includes three scenarios: successful match, partial match, and no match.
[0091] In this embodiment of the application, after all authentication nodes return a communication receipt containing the node identifier and the receiving time, each authentication node starts the local data parsing module to read the contents of the credential information area in the identity authentication request, and extracts the target identity information such as the unique identity code and digital signature hash value in the distributed identity credential, and then extracts the identity identifier such as the name and supplementary document number from the identity supplementary information.
[0092] Subsequently, each identity verification node retrieves the associated data in the blockchain network through the distributed storage query module of the blockchain transaction system. It compares the target identity information with the identity feature fields in the associated data one by one to obtain a preliminary comparison result. Then, it performs a second comparison with the identity identifier field in the associated data to obtain a second comparison result. If both results are consistent, it is determined to be a complete match. If the preliminary comparison result is consistent and the second comparison result has some differences, it is determined to be a partial match. If the preliminary comparison result or the second comparison result is inconsistent, it is determined to be a mismatch. Finally, an association relationship is generated.
[0093] Step 403: Based on the association, compare the identity identifiers of the two parties to the transaction with the identity benchmark information in the distributed identity credential to generate a single-node verification fragment. The single-node verification fragment includes the node identifier, the judgment basis, and the identity judgment result of the two parties to the transaction.
[0094] In this step, the identity baseline information refers to the standard information recorded in the distributed identity credential, used as the basis for identity verification. This includes the official identity code of the transaction entity, the signature information of the certification authority, and the validity period of the identity. A single-node verification fragment refers to the structured verification record generated after a single identity verification node completes identity verification. This fragment includes the node's identifier, the relationship between the judgment criteria during the verification process, and the identity judgment result regarding the legality of the identities of both parties in the transaction. Judgment criteria refer to the key evidence relied upon by the identity verification node when generating the identity judgment result. These criteria include a matching report of the target identity information and associated data, a comparison report of the identity identifier and the identity baseline information, and a report verifying the authenticity of additional information. The identity judgment result of both parties in the transaction refers to the conclusion of a single identity verification node regarding the legality and validity of the buyer's and seller's identities. This judgment result includes two independent results: buyer's identity passed / failed, and seller's identity passed / failed.
[0095] In this embodiment, based on the association relationship, the identity comparison module of each identity verification node extracts identity benchmark information such as official identity code and certification authority seal information from the distributed identity credential. Then, the identity identifiers of the two parties to the transaction are compared with these identity benchmark information fields to form a judgment basis to clarify whether various types of information are consistent or have differences. The judgment basis includes the matching conclusion of the target identity information of the two parties to the transaction and the associated data in the association relationship, the field comparison results of each identity identifier of the buyer and the buyer's identity benchmark information, and the field comparison results of each identity identifier of the seller and the seller's identity benchmark information. Subsequently, the judgment result of whether the buyer's and seller's identities are legal is given. Finally, the node identifier, the complete judgment basis, and the judgment results of the identities of the two parties to the transaction are integrated into a single node verification segment.
[0096] Step 404: Transmit the single-node verification fragments of all identity verification nodes to the identity consensus node of the blockchain network, and perform consistency verification on the identity determination results of both parties in the transaction through the identity consensus node, so as to count the number of nodes that have consistent verification, including the number of nodes that have consistent verification by the buyer and the number of nodes that have consistent verification by the seller.
[0097] In this step, the identity consensus node refers to the core node in the blockchain network responsible for verifying and summarizing the verification results of multiple identity verification nodes. The identity consensus node has the ability to integrate data, make consistency judgments, and statistically analyze results.
[0098] Step 405: If the number of nodes with consistent verification reaches a preset threshold, the valid information in each single-node verification segment is integrated to generate an identity authentication result. If the number of nodes with consistent verification does not reach the preset threshold, an identity authentication pending verification result including the inconsistency judgment node identifier and the difference content is generated. Based on the identity authentication pending verification result, supplementary information of both parties to the transaction is obtained and sent to each identity verification node to regenerate a supplementary single-node verification segment. The supplementary single-node verification segment with the number of nodes with consistent verification reaching the preset threshold and the valid information in each single-node verification segment are integrated to generate an identity authentication result.
[0099] In this step, the preset threshold refers to the minimum number of consistent nodes that are pre-set in the blockchain network to determine whether identity authentication is successful. The preset threshold includes the buyer identity authentication consistency threshold and the seller identity authentication consistency threshold.
[0100] Valid information refers to information extracted from a single-node verification fragment that is valuable for generating the final identity authentication result. Valid information includes node identifiers, valid parts of the judgment criteria, and identity judgment results.
[0101] The inconsistency determination node identifier refers to the identifier of the identity verification node whose identity determination result for the two parties in the transaction is inconsistent with that of the majority of nodes during the identity consensus node verification.
[0102] The identity authentication pending verification result refers to the intermediate result generated when the number of nodes with consistent verification has not reached the preset threshold, indicating that the identity authentication has not yet passed. The identity authentication pending verification result includes the inconsistency judgment node identifier, the difference content, and the prompt for supplementary information.
[0103] Supplementary information from both parties to the transaction refers to the materials submitted by both parties to resolve verification discrepancies based on the identity authentication pending verification result. This supplementary information includes supplementary identity verification documents, materials explaining the differences in characteristics, and supplementary authorization certificates.
[0104] A supplementary single-node verification fragment refers to a new verification fragment generated by the identity verification node after re-executing the verification process based on supplementary information from both parties to the transaction. This supplementary single-node verification fragment includes the node identifier, supplementary judgment criteria, and the re-judged identity result.
[0105] In this embodiment, a preset threshold is retrieved from the blockchain network, and the number of nodes with consistent verification by the buyer and the number of nodes with consistent verification by the seller are compared with the preset threshold. After confirming that the number of nodes with consistent verification by both the buyer and seller has reached the threshold, valid information is extracted from all single-node verification fragments and integrated into the real estate second-hand transaction identity authentication result in the format of authentication result title-node identifier list-judgment basis-final result.
[0106] If the number of nodes on either side does not reach the threshold, an identity authentication pending verification result containing the inconsistency judgment node identifier, the difference content, and the information to be supplemented is generated and synchronized to the transaction service window. After the staff informs both parties to the transaction, and both parties supplement the information and upload it to the identity consensus node, the identity consensus node forwards the supplemented information to each verification node, regenerates the supplemented single-node verification fragment, and repeats steps 414-405 until an identity authentication result is generated.
[0107] Optionally, step 404 involves verifying the consistency of the identity determination results of both parties in the transaction through the identity consensus node, and counting the number of nodes that have achieved consistent verification. The number of nodes that have achieved consistent verification includes the number of nodes that have achieved consistent verification by the buyer and the number of nodes that have achieved consistent verification by the seller. Specifically, this includes the following steps:
[0108] Step 411: Based on the node qualification information pre-stored in the blockchain network, match the corresponding node trust level for each node identifier, and combine the verification fragments of each single node to form a basic dataset.
[0109] In this step, node qualification information refers to the information pre-stored in the blockchain network used to assess the qualifications of identity verification nodes. This node qualification information includes the node's certification level, business scope, historical verification accuracy rate, and credit rating.
[0110] The node trust level refers to the level assigned to each identity verification node based on its qualification information, reflecting the trustworthiness of its verification results.
[0111] The basic dataset refers to the dataset formed by associating and integrating the node trust level of each authentication node with the corresponding single-node verification fragment. This dataset includes node identifier, trust level, and complete verification fragment.
[0112] Step 412: Perform integrity identification on the judgment criteria in the basic dataset to remove unsupported segments in the basic dataset that do not include the judgment criteria, thereby obtaining a valid dataset.
[0113] In this step, "unsupported fragment" refers to a single-node verification fragment in the base dataset that does not include the basis for judgment or lacks key information about the basis for judgment.
[0114] The effective dataset refers to the dataset remaining after removing unsubstantiated fragments from the basic dataset. This effective dataset includes node identifiers, credibility levels, and the basic dataset containing complete verification fragments.
[0115] Step 413: Identify duplicate single-node verification segments belonging to the same authentication node in the valid dataset, retain duplicate single-node verification segments with a completeness higher than a preset threshold, and form a deduplicated dataset.
[0116] In this step, repeated single-node verification fragments refer to verification fragments generated by the same authentication node in the valid dataset that have duplicate or highly similar content.
[0117] The deduplicated dataset refers to the dataset formed after removing duplicate single-node validation fragments from the valid dataset. The deduplicated dataset includes a unique high-quality validation fragment for each node and its corresponding credibility level.
[0118] Step 414: Count the buyer-consistent results and seller-consistent results in the deduplicated dataset, and determine the counting unit for each buyer-consistent result and seller-consistent result to calculate the buyer-weighted cumulative number and seller-weighted cumulative number. Convert the buyer-weighted cumulative number into the number of nodes with buyer-verified consistency, and convert the seller-weighted cumulative number into the number of nodes with seller-verified consistency.
[0119] In this step, the buyer consensus result refers to the verification record in the deduplicated dataset where the authentication node's determination of the buyer's identity is consistent with the determination results of the majority of nodes.
[0120] Seller consistency results refer to verification records in the dataset where the authentication nodes' determination of the seller's identity is consistent with the determination results of the majority of nodes after deduplication.
[0121] The counting unit refers to the weighting coefficient used to statistically consistent results, which is set according to the node's credibility level.
[0122] The buyer-weighted cumulative count refers to the value obtained by summing the buyer-consistent results in the deduplicated dataset according to the counting unit of the corresponding node.
[0123] The seller weighted cumulative count refers to the value obtained by summing the seller consistency results in the deduplicated dataset according to the counting unit of the corresponding node.
[0124] In this embodiment, the single-node verification fragments of each identity verification node are encrypted using an encryption algorithm and then sent to the identity consensus node of the blockchain network through the dedicated channel of the blockchain consensus node. After receiving and decrypting the fragments, the identity consensus node performs subsequent processing according to steps 411-414: First, sub-step 411 is executed: the node qualification information stored in the blockchain network is retrieved, and the node credibility level is matched with the node identifier in each single-node verification fragment according to the preset rules. Then, the node credibility level is associated with the corresponding single-node verification fragment to form a basic dataset.
[0125] Then execute sub-step 412: perform a completeness check on the judgment criteria of each single-node verification segment in the basic dataset. The completeness check includes confirming whether it includes core correlation, identity identification comparison details, and identity benchmark information sources, so as to eliminate unfounded segments that are missing any key information and obtain a valid dataset.
[0126] Next, sub-step 413 is executed: the fragments in the valid dataset are grouped by node identifier. If there are multiple duplicate fragments in the same group that are in the same authentication node, the integrity assessment module needs to be started to count the number of fields and the level of detail of the content in the duplicate fragments, and retain the fragments in the valid dataset whose integrity is higher than the preset threshold, and finally form the deduplicated dataset.
[0127] Finally, sub-step 414 is executed: Based on each single-node verification segment in the deduplicated dataset, the number of identity verification nodes corresponding to the pass and fail judgments in the buyer's identity determination results, and the number of identity verification nodes corresponding to the pass and fail judgments in the seller's identity determination results are counted respectively; then, the judgment results of identity verification nodes exceeding the preset number are determined, and the buyer consistent results and seller consistent results that are consistent with the judgment results are selected. The preset number is reasonably set according to the total number of identity verification nodes in the blockchain network.
[0128] Next, according to preset rules, calculate the buyer's weighted cumulative number and the seller's weighted cumulative number. The preset rule can be that the counting unit of the authentication nodes with a credibility higher than the preset value is set to 1. This application embodiment does not limit the rule, and it can be set according to the actual situation. Finally, according to preset rules, convert the two types of weighted cumulative numbers into the number of nodes that are consistent with the buyer's verification and the number of nodes that are consistent with the seller's verification, respectively. The preset rule can be that when the weighted cumulative number reaches a certain set value, it corresponds to a specific number of consistent nodes. This application embodiment does not limit the rule, and it can be set according to the actual situation.
[0129] The embodiments of this application improve the credibility and consistency of identity authentication results, avoid the risk of identity forgery, and ensure the legality and compliance of the identity of the transaction subject.
[0130] This application provides a specific embodiment. Step 105 involves verifying the ownership restriction of the real estate based on the ownership comparison result and the smart contract in the blockchain network, and obtaining the verification result. This specifically includes the following steps:
[0131] Step 501: Extract the first matching identifier of the two parties to the transaction and the second matching identifier of the historical rights holder information of the real estate from the ownership comparison results, and match the first matching identifier with the identity validity period of the two parties to the transaction, and match the second matching identifier with the registration validity period of the historical rights holder registration record.
[0132] In this step, the first matching identifier for both parties to the transaction refers to the unique identifier extracted from the ownership comparison results and bound to the identities of both parties to the transaction. This first matching identifier includes the distributed identity credential codes of the buyer and the seller.
[0133] Real estate historical rights holder information refers to the identity and registration information of all past legal rights holders of the real estate recorded in the spatiotemporal map. This real estate historical rights holder information includes the name / title of the historical rights holder, identity identifier, and registration time.
[0134] The second matching identifier refers to the unique identity identifier of the historical rights holder extracted from the information of the historical rights holder of the real estate, such as the distributed identity code of the historical rights holder.
[0135] The identity validity period refers to the valid time range of the identity credentials of both parties in the transaction that are bound to the first matching identifier. This identity validity period includes the effective date and the expiration date of the credentials.
[0136] Historical rights holder registration records refer to the archival information of historical rights holders who registered the ownership of the real estate, which is archived by the real estate registration department. These historical rights holder registration records include the effective date of registration, the expiration date of registration, and the registered items.
[0137] The valid registration period refers to the valid time range of historical rights holder registration records that are bound to the second matching identifier. This valid registration period includes the registration effective date and the expiration date.
[0138] In this embodiment, the identity identifiers bound to the identity authentication results of both parties in the transaction are extracted from the ownership comparison results as the first matching identifiers of both parties in the transaction, and the identity identifiers corresponding to the historical rights holder information of the real estate are extracted from the spatiotemporal graph as the second matching identifiers of the historical rights holder information of the real estate. Then, the validity period of the identity recorded in the distributed identity certificates of both parties in the transaction is queried, and the validity period of the identity is matched with the first matching identifier. The registration effective and invalidation times recorded in the historical rights holder registration records in the spatiotemporal graph are queried, and the registration validity period of the historical rights holder registration records is matched with the second matching identifier, thus forming the association data between the identifiers and the time periods.
[0139] Step 502: Retrieve the ownership restriction records of real estate from the blockchain network, classify the ownership restriction records according to the restriction type, and form a mortgage verification group, a seizure verification group, an objection verification group, and a pre-notification verification group. The ownership restriction records include the restriction type, restriction initiation time, restriction period, restriction initiating institution identifier, and restriction status identifier.
[0140] In this step, the property ownership restriction record refers to the information on restrictions on rights established for the property stored in the blockchain. The mortgage verification group refers to the set of records formed after filtering the property ownership restriction records by restriction type (mortgage). The seizure verification group refers to the set of records formed after filtering the property ownership restriction records by restriction type (seizure). The objection verification group refers to the set of records formed after filtering the property ownership restriction records by restriction type (objection). The pre-notification verification group refers to the set of records formed after filtering the property ownership restriction records by restriction type (pre-notification).
[0141] In this embodiment of the application, the ownership restriction records of real estate are retrieved through the distributed storage query interface of the blockchain network; then, the restriction type field in the ownership restriction record is identified, and all records identified as mortgages are assigned to the mortgage verification group, records identified as seizures are assigned to the seizure verification group, records identified as objections are assigned to the objection verification group, and records identified as notices are assigned to the notice verification group.
[0142] Step 503: Based on the collateral registration verification rules in the smart contract in the blockchain network and the second matching identifier, perform a collateral settlement judgment on the collateral verification group with a valid restriction status identifier to obtain the first judgment result.
[0143] In this step, the mortgage registration verification rules refer to the pre-defined rules in the blockchain smart contract used to determine whether the mortgage restriction has been lifted. These rules include the requirement to provide proof of settlement and automatic lifting upon expiration of the period. The first judgment result refers to the conclusion obtained after verifying the records in the mortgage verification group whose restriction status is marked as valid.
[0144] In this embodiment, the pre-set mortgage registration verification rules within the smart contract are parsed to obtain information included in the rules, such as the requirement to provide a mortgage settlement certificate, automatic release if the restriction period has expired, and the restriction initiator's identifier being consistent with the filing. The second matching identifier is matched with the rights holder association identifier field of each record in the mortgage verification group to confirm whether they are mortgage records of the same real estate. Only the successfully matched mortgage records are retained. Then, in conjunction with the mortgage registration verification rules, it is checked whether the records with a valid restriction status among the retained successfully matched mortgage records meet the requirements of providing a settlement certificate or the restriction period having exceeded the current time. If they meet the requirements, it is determined that the mortgage has been released; otherwise, it is determined that the mortgage is still valid. Finally, the judgment results of all valid mortgage records are integrated to obtain the first judgment result.
[0145] Step 504: Based on the seizure registration verification rules in the smart contract, the second matching identifier, and the registration validity period, determine the seizure release for the seizure verification group with a valid restriction status identifier, and obtain the second judgment result.
[0146] In this step, the seizure registration verification rules refer to the pre-set rules in the blockchain smart contract used to determine whether the seizure restrictions have been lifted. These seizure registration verification rules include the requirement to provide a release ruling, automatic release upon expiration of the period without renewal, etc. The second judgment result refers to the conclusion obtained after verifying the records in the seizure verification group whose restriction status is marked as valid.
[0147] In this embodiment, the seizure registration verification rules within the smart contract are parsed to obtain information included in the rules, such as the seizure period expiring without renewal and the seizure only requiring verification within the valid registration period. The second matching identifier is matched with the identifier of the seized rights holder recorded in the seizure verification group to confirm the associated real estate. Records whose seizure initiation time is within the valid registration period are selected from the associated real estate. For records with a valid restriction status identifier, it is checked whether there is a release order or whether the seizure period has exceeded the current time. If the conditions are met, the seizure is determined to be released; otherwise, the seizure is determined to be still valid. The judgment results of all valid seizure records are integrated to obtain the second judgment result.
[0148] Step 505: Based on the objection registration verification rules in the smart contract, the first matching identifier, and the identity validity period, determine the objection invalidation of the objection verification group whose restriction status identifier is valid, and obtain the third judgment result.
[0149] In this step, the objection registration verification rules refer to the pre-set rules in the blockchain smart contract used to determine whether an objection is invalid. These rules include invalidation upon withdrawal by the applicant and invalidation upon failure to file a lawsuit within the statutory period. The third judgment result refers to the conclusion obtained after verifying the records in the objection verification group whose restriction status is marked as valid.
[0150] In this embodiment, the objection registration verification rules within the smart contract are parsed to obtain information included in the rules, such as the objection becoming invalid if the applicant withdraws the application, the objection becoming invalid if no lawsuit is filed within the statutory period after the objection registration expires, and only objections within the identity validity period need to be verified. The first matching identifier is matched with the objection-related transaction party identifier recorded in the objection verification group to ensure that the filtered objection records are for both parties in this transaction. Combined with the identity validity period, records corresponding to the related transaction party whose objection initiation time is within the identity validity period are filtered out. For records with a valid restriction status identifier, it is checked whether there is proof of objection withdrawal or whether the objection period has exceeded the statutory period. If the conditions are met, the objection is determined to be invalid; if not, the objection is determined to be valid. The judgment results of all valid objection records are integrated to obtain the third judgment result.
[0151] Step 506: Based on the pre-registration verification rules in the smart contract, the first matching identifier, and the identity validity period, determine the pre-registration failure of the pre-registration verification group whose restriction status identifier is valid, and obtain the fourth judgment result.
[0152] In this step, the pre-registration verification rules refer to the pre-defined rules in the blockchain smart contract used to determine whether a pre-registration has expired. These pre-registration verification rules include invalidation if the main contract expires, and invalidation if the registration is not completed within the statutory period. The fourth judgment result refers to the conclusion obtained after verifying the records in the pre-registration verification group whose restriction status is valid.
[0153] In this embodiment of the application, the pre-registration verification rules in the smart contract are parsed to obtain the information included in the rules, such as the pre-registration becoming invalid if the main contract corresponding to it becomes invalid, the pre-registration becoming invalid if the registration is not completed within the statutory period, and only pre-registrations within the validity period of the identity need to be verified. The first matching identifier is matched with the pre-registration related transaction party identifier recorded in the pre-registration verification group, and only the pre-registration records that are successfully matched are retained to confirm the related transaction parties.
[0154] Based on the validity period of the identity, the records corresponding to the related party in the transaction and whose announcements were initiated within the validity period of the identity are selected. For records with a valid restriction status, it is checked whether there is proof of the invalidity of the main contract or whether the announcement period has exceeded the statutory period. If the conditions are met, the announcement is deemed invalid; otherwise, the announcement is deemed valid. The judgment results of all valid announcement records are integrated to obtain the fourth judgment result.
[0155] Step 507: Generate a verification result based on the first judgment result, the second judgment result, the third judgment result, and the fourth judgment result. If all judgment results indicate that the restriction has been lifted or does not affect the transaction, the verification result is that there is no valid ownership restriction. If any judgment result indicates that the restriction is still valid and affects the transaction, a verification result including the type of valid restriction and the content of the ownership restriction is generated.
[0156] In this step, "all judgment results" refers to the collective term for the first, second, third, and fourth judgment results. "Restriction lifted or does not affect the transaction" means the restriction status in the judgment result is lifted, or the restriction exists but is irrelevant to this transaction. "No valid ownership restriction" means that, after considering all judgment results, it is determined that the real estate currently has no rights restrictions affecting the transaction. "Any judgment result" refers to any one or more of the judgment results. "Restriction still valid and affects the transaction" means the restriction status in the judgment result is still valid, and the restriction directly hinders this transfer of ownership. "Valid restriction type" refers to the restriction category corresponding to the restriction still being valid and affecting the transaction. "Ownership restriction content" refers to the restriction details corresponding to the restriction still being valid and affecting the transaction, including the restriction initiation time, restriction period, and the identifier of the restriction initiating institution.
[0157] In this embodiment of the application, the judgment results are classified. If all judgment results are that the restriction has been lifted or does not affect the transaction, the verification result is generated as "no valid ownership restriction". If any judgment result is that the restriction is still valid and affects the transaction, such as the mortgage has not been lifted or the seizure is still valid, and directly affects the transfer of ownership, the valid restriction type and ownership restriction content are extracted from the corresponding judgment result and integrated to generate a verification result including this information.
[0158] The embodiments of this application can provide accurate correlation evidence for ownership verification, making the verification more accurate.
[0159] This application provides a specific embodiment. Step 105 involves performing transaction fund transfer and ownership information update operations based on the verification results to achieve full-chain registration management of real estate secondary transactions. The specific steps include:
[0160] Step 511: When the verification result is that there is no valid ownership restriction, generate a transaction permission instruction based on the transaction fund custody account information in the smart contract.
[0161] In this step, the permitted transaction instruction refers to the instruction that authorizes the transfer of funds when the verification result shows that there is no valid ownership restriction. The permitted transaction instruction includes the instruction number, transaction fund custody account information, real estate code, and instruction effective time.
[0162] In this embodiment of the application, when the verification result is that there is no valid ownership restriction, the transaction fund custody account information is extracted from the smart contract. The account information includes the name of the bank where the custody account is opened, the account number, and the smart contract address bound to the account. Then, based on the transaction fund custody account information, a transaction permission instruction is generated in a preset format to ensure that the flow of funds complies with the contract agreement.
[0163] Step 512: According to the transaction permission instruction, initiate a transaction fund transfer request to the buyer's fund account, and transfer the preset funds to the transaction fund custody account in the smart contract to generate a fund custody certificate including the transfer amount, transfer timestamp, and custody account identifier, and transmit the fund custody certificate to the blockchain network for storage.
[0164] In this step, the transaction fund transfer request refers to a request initiated by the financial institution to which the buyer's funds account belongs, requesting the transfer of funds. This transaction fund transfer request includes a request number, buyer's funds account information, transaction fund escrow account information, transfer amount, and transaction purpose. The fund escrow certificate refers to a certificate recording the fund escrow operation, and includes the transfer amount, transfer timestamp, escrow account identifier, buyer's funds account identifier, and certificate number.
[0165] In this embodiment, a transaction fund transfer request is initiated to the buyer's fund account through an interface with the financial institution to which the buyer's fund account belongs. After the financial institution agrees to the transfer, the funds are transferred from the buyer's fund account to the transaction fund custody account in the smart contract according to the preset amount agreed upon by both parties. After the transfer is completed, a fund custody certificate is generated. Finally, the fund custody certificate is uploaded to the blockchain network through the blockchain's notarization interface, and multiple nodes record it synchronously to complete the notarization.
[0166] Step 513: After confirming the completion of the fund custody certificate storage, update the right holder change information and registration status change information in the ownership change time series data, and add the fund custody certificate and update operation timestamp to form updated ownership time series data.
[0167] In this step, updating the ownership change time series data refers to the updated ownership change time series data that has not yet taken final effect. This updated ownership change time series data includes the updated rights holder information, registration status information, fund custody certificate, and update operation timestamp.
[0168] In this embodiment of the application, after confirming that the fund custody certificate has been successfully stored through the blockchain's evidence storage query interface, the original ownership change time series data is retrieved, and the right holder change information is updated to buyer information, and the registration status change information is updated to pre-update; at the same time, the stored fund custody certificate and update operation timestamp are added to the time series data; the updated right holder information, registration status information, fund custody certificate, and update operation timestamp are integrated to form updated ownership time series data, which is only a temporary state and has not yet taken effect.
[0169] Step 514: Based on the updated ownership time series data, mark the status of the rights holder nodes in the spatiotemporal graph as a pre-update status, and generate a graph update confirmation result.
[0170] In this step, the pre-update status refers to the temporary status marker of the right holder node in the spatiotemporal graph that updates the ownership time series data. The graph update confirmation result refers to the record that proves the spatiotemporal graph has completed the pre-update, and the confirmation result includes the updated right holder node identifier, the pre-update status marker time, and the updated ownership time series data association number.
[0171] In this embodiment, the corresponding right holder node is located in the spatiotemporal graph based on the real estate code and the updated right holder information in the updated ownership time series data. The status field of the right holder node is marked as pre-update state through the graph editing module to distinguish between unupdated, pre-updated, and updated states, and to avoid confusion with the final effective state. After marking is completed, the graph update confirmation result is generated, which includes the updated ownership time series data.
[0172] Step 515: Send ownership update instructions to cross-department nodes and aggregation nodes. After receiving pre-update completion signals from all cross-department nodes and aggregation nodes, send a fund transfer trigger instruction to the smart contract. The ownership update instruction includes updated ownership time-series data and graph update confirmation results.
[0173] In this step, the ownership update instruction refers to the instruction sent by the cross-department node and the aggregation node, requesting the execution of a pre-update operation. The pre-update completion signal refers to the confirmation signal returned to the system by the cross-department node and the aggregation node after completing the local data pre-update. This pre-update completion signal includes the node identifier, the pre-update completion time, and the pre-update data association number. The funds transfer trigger instruction refers to the instruction sent by the system to the smart contract, authorizing the transfer of escrow funds to the seller. This funds transfer trigger instruction includes the instruction number, the transaction funds escrow account identifier, and the seller's funds account information.
[0174] In this embodiment of the application, ownership update instructions are sent to cross-department nodes and aggregate nodes through the node communication link of the blockchain. The instructions include updated ownership time sequence data and graph update confirmation results for nodes to refer to for update content. After receiving the pre-update completion signal returned by all cross-department nodes and aggregate nodes, it is confirmed that each node has completed the pre-update of local data. Then, a fund transfer trigger instruction is sent to the smart contract through the smart contract trigger interface, so that the smart contract transfers the funds in the escrow account to the seller.
[0175] Step 516: If the smart contract reports a successful fund transfer and generates a final fund transfer record including the accounts of both parties, the transfer amount, and the final transfer timestamp, then send an ownership update confirmation instruction to the cross-department nodes and the aggregation node, and receive the final update completion signal from all cross-department nodes and the aggregation node. If the smart contract reports a failed fund transfer, then send an ownership pre-update rollback instruction to the cross-department nodes and the aggregation node to cancel the update operation, and generate a fund transfer failure explanation.
[0176] In this step, the final fund transfer record refers to the record detailing the final fund transfer, including the accounts of both parties, the transfer amount, the final transfer timestamp, and the transfer voucher number. The ownership update confirmation instruction is a command sent by the system to the cross-departmental nodes and the aggregation node, authorizing the conversion of the pre-update status to the final effective status. The ownership pre-update rollback instruction is a command sent by the system to the cross-departmental nodes and the aggregation node when the fund transfer fails, requesting the cancellation of the pre-update operation. The update operation refers to the pre-update or final update operation performed by the cross-departmental nodes and the aggregation node on the locally stored real estate ownership data. This update operation includes modifying the rights holder information and adjusting the registration status.
[0177] In this embodiment of the application, after the smart contract receives the fund transfer trigger instruction, it executes the fund transfer operation and provides feedback on the transfer result: if the transfer result indicates that the fund transfer was successful and a final fund transfer record is generated, then the ownership update confirmation instruction is sent to the cross-department node and the aggregation node, and the authorized node changes the pre-update state to the final effective state. The ownership update confirmation instruction includes the final fund transfer record; after receiving the final update completion signal returned by all nodes, the formal update of the ownership information is completed.
[0178] If the transfer result indicates that the fund transfer has failed, a pre-update rollback instruction for ownership is sent to the cross-department node and the aggregation node, requiring the nodes to revoke the previous pre-update operation. At the same time, a fund transfer failure explanation is generated, which includes the failure time, the reason for failure, and suggestions for handling. The pre-update operation restores the original rights holder information and registration status. The pre-update rollback instruction for ownership includes the rollback basis, which is the reason for the fund transfer failure.
[0179] Step 517: Combine the fund custody certificate, updated ownership time series data, and map update confirmation results with the final update completion signals and final fund transfer records of each cross-department node and the summary node, or the fund transfer failure explanation, to form a full-link registration record for real estate second-hand transactions. Transmit the full-link registration record to the blockchain network for evidence storage, so as to realize the full-link registration management of real estate second-hand transactions.
[0180] In this step, the full-link registration record refers to the collection of records that integrate all materials from the entire process of real estate secondary transactions. This full-link registration record includes fund custody certificates, updated ownership time series data, map update confirmation results, node feedback signals, and final fund transfer records or explanations of fund transfer failures.
[0181] In this embodiment, materials are integrated based on the fund transfer result. Specifically: if the fund transfer is successful, the fund custody certificate, updated ownership time series data, map update confirmation result, final update completion signal of each node, and final fund transfer record are integrated; if the fund transfer fails, the fund custody certificate, updated ownership time series data, map update confirmation result, and fund transfer failure explanation are integrated. These materials are organized in the order of transaction process stage - material type to form a full-link registration record of real estate secondary transactions. Finally, the full-link registration record is transmitted to the blockchain network for storage through the blockchain's evidence storage interface, realizing the registration management of the entire real estate secondary transaction process for subsequent query and traceability.
[0182] The embodiments of this application can ensure the compliance of fund transfer authorization, protect fund security, avoid the separation of ownership and funds, realize full traceability of the transaction process, and ensure transaction transparency and security.
[0183] Figure 3 is a schematic diagram of a specific implementation of a blockchain-based real estate registration management and transaction system provided in this application. Referring to Figure 3, the system may include:
[0184] The association module 21 is used to obtain the passive radio frequency identification electronic tag of the real estate during the initial registration process, associate the real estate code in the passive radio frequency identification electronic tag with the distributed identity certificate of the real estate owner to obtain the association data, and transmit the association data to the blockchain network for storage.
[0185] The acquisition module 22 is used to acquire the ownership change time sequence data corresponding to the real estate when the real estate enters the second-hand transaction process and the radio frequency identification reader reads the real estate code.
[0186] The conversion module 23 is used to verify the ownership change time series data. When the verification is successful, the ownership change time series data is converted into a spatiotemporal map.
[0187] The authentication module 24 is used to authenticate the identities of both parties in a second-hand real estate transaction through distributed identity authentication technology, generate the identity authentication results of both parties, and compare the identity authentication results with the real estate historical rights holder information in the spatiotemporal map to obtain the ownership comparison results.
[0188] The verification module 25 is used to verify the ownership restrictions of real estate based on the ownership comparison results and the smart contract in the blockchain network, obtain the verification results, and perform transaction fund transfer and ownership information update operations based on the verification results, so as to realize the full-link registration management of real estate secondary transactions.
[0189] This application provides an embodiment of a blockchain-based real estate registration management and transaction system for implementing the aforementioned blockchain-based real estate registration management and transaction method. Therefore, the specific implementation of the blockchain-based real estate registration management and transaction system can be found in the embodiment section of the blockchain-based real estate registration management and transaction method described above. The specific implementation can be referred to the description of the corresponding embodiments, which will not be repeated here.
[0190] This application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of any of the above-described blockchain-based real estate registration management transaction methods.
[0191] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the above-described blockchain-based real estate registration management transaction methods.
[0192] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory, random access memory, portable hard drives, magnetic disks, or optical disks.
[0193] The embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above embodiments of the blockchain-based real estate registration management transaction method.
[0194] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0195] The foregoing has provided a detailed description of a blockchain-based real estate registration management and transaction method and system provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of this application.
Claims
1. A blockchain-based method for real estate registration management and transaction, characterized in that, include: The process involves acquiring passive RFID tags during the initial registration of real estate, associating the real estate code within the tags with the distributed identity certificate of the real estate owner to obtain associated data, and transmitting this associated data to a blockchain network for evidence storage. When the real estate enters a secondary market transaction, and the RFID reader reads the real estate code, the process obtains the corresponding ownership change timeline data. This timeline data is then verified; if the verification passes, it is converted into a spatiotemporal graph. Distributed identity authentication technology is used to authenticate both parties in the secondary real estate transaction, generating authentication results. These authentication results are then compared with the historical owner information of the real estate in the spatiotemporal graph to obtain ownership comparison results. Based on the ownership comparison results and the smart contracts in the blockchain network, the ownership restrictions of real estate are verified to obtain the verification results. Based on the verification results, the transaction funds are transferred and the ownership information is updated to realize the full-chain registration management of real estate secondary transactions.
2. The method according to claim 1, characterized in that, This paper utilizes distributed identity authentication technology to authenticate the identities of both parties in a second-hand real estate transaction, generating authentication results for both parties. The process includes: integrating the distributed identity credentials and additional identity information submitted by both parties into an authentication request; sending the authentication request to multiple identity verification nodes in a blockchain network; after confirming that each identity verification node has received the authentication request, extracting the target identity information from the distributed identity credentials and the identity identifier from the additional identity information; associating the target identity information with the stored related data in the blockchain network to obtain a correlation relationship; based on the correlation relationship, comparing the identity identifiers of both parties with the identity baseline information in the distributed identity credentials to generate a single-node verification fragment, which includes a node identifier, judgment criteria, and the identity judgment results of both parties; and transmitting the single-node verification fragments from all identity verification nodes. The identity consensus nodes of the blockchain network are used to verify the consistency of the identity determination results of both parties in the transaction. The number of nodes with consistent verification is counted, including the number of nodes with consistent verification by the buyer and the number of nodes with consistent verification by the seller. If the number of nodes with consistent verification reaches a preset threshold, the valid information in each single node verification segment is integrated to generate an identity authentication result. If the number of nodes with consistent verification does not reach the preset threshold, an identity authentication pending verification result is generated, including the inconsistency judgment node identifier and the difference content. Based on the identity authentication pending verification result, supplementary information of both parties in the transaction is obtained and sent to each identity verification node to regenerate supplementary single node verification segments. The supplementary single node verification segments with consistent verification reaching the preset threshold and the valid information in each single node verification segment are integrated to generate an identity authentication result.
3. The method according to claim 2, characterized in that, The identity consensus nodes perform consistency verification on the identity determination results of both parties in the transaction, and count the number of nodes with consistent verification. The number of nodes with consistent verification includes the number of nodes with consistent verification by the buyer and the number of nodes with consistent verification by the seller. This includes: based on the node qualification information pre-stored in the blockchain network, matching each node identifier with a corresponding node credibility level, and combining each single node verification segment to form a basic dataset; performing integrity identification on the judgment basis in the basic dataset to remove unfounded segments in the basic dataset that do not include judgment basis, and obtaining a valid dataset; identifying duplicate single node verification segments belonging to the same identity verification node in the valid dataset, retaining duplicate single node verification segments with integrity higher than a preset threshold, and forming a deduplicated dataset; counting the consistent results of the buyer and the consistent results of the seller in the deduplicated dataset, and determining the counting unit for each consistent result of the buyer and the consistent result of the seller, to calculate the weighted cumulative number of the buyer and the weighted cumulative number of the seller, converting the weighted cumulative number of the buyer into the number of nodes with consistent verification by the buyer, and converting the weighted cumulative number of the seller into the number of nodes with consistent verification by the seller.
4. The method according to claim 1, characterized in that, Based on the ownership comparison results and the smart contract in the blockchain network, the ownership restriction verification of the real estate is performed to obtain the verification results, including: extracting the first matching identifier of the two parties to the transaction and the second matching identifier of the historical rights holder information of the real estate from the ownership comparison results, and matching the first matching identifier with the identity validity time period corresponding to the two parties to the transaction, and matching the second matching identifier with the registration validity time period corresponding to the historical rights holder registration record; retrieving the ownership restriction records of the real estate from the blockchain network, classifying the ownership restriction records according to the restriction type to form a mortgage verification group, a seizure verification group, an objection verification group, and a pre-notification verification group, wherein the ownership restriction records include the restriction type, restriction initiation time, restriction period, restriction initiating institution identifier, and restriction status identifier; according to the mortgage registration verification rules in the smart contract in the blockchain network and the second matching identifier, the mortgage verification group with a valid restriction status identifier is judged to settle the mortgage, and a first judgment result is obtained; according to the smart contract... The seizure registration verification rules, the second matching identifier, and the valid registration time period are used to determine the seizure release for seizure verification groups with valid restriction status identifiers, resulting in a second judgment result. Based on the objection registration verification rules in the smart contract, the first matching identifier, and the identity validity time period, objection invalidation is determined for objection verification groups with valid restriction status identifiers, resulting in a third judgment result. Based on the pre-announcement registration verification rules in the smart contract, the first matching identifier, and the identity validity time period, pre-announcement invalidation is determined for pre-announcement verification groups with valid restriction status identifiers, resulting in a fourth judgment result. Based on the first, second, third, and fourth judgment results, a verification result is generated. If all judgment results indicate that the restriction has been lifted or does not affect the transaction, the verification result is "no valid ownership restriction." If any judgment result indicates that the restriction is still valid and affects the transaction, a verification result including the valid restriction type and ownership restriction content is generated.
5. The method according to claim 1, characterized in that, Based on the verification results, transaction fund transfer and ownership information update operations are performed to achieve full-chain registration management of real estate secondary transactions. This includes: when the verification result indicates no valid ownership restrictions, generating a transaction permission instruction based on the transaction fund escrow account information in the smart contract; initiating a transaction fund transfer request to the buyer's fund account based on the transaction permission instruction, and transferring the preset funds to the transaction fund escrow account in the smart contract to generate a fund escrow certificate including the transfer amount, transfer timestamp, and escrow account identifier, and transmitting the fund escrow certificate to the blockchain network for notarization; after confirming the notarization of the fund escrow certificate, updating the right holder change information and registration status change information in the ownership change time series data, and adding the fund escrow certificate and update operation timestamp to form updated ownership time series data; marking the status of the right holder node in the spatiotemporal graph as a pre-update state based on the updated ownership time series data, and generating a graph update confirmation result; sending ownership update instructions to cross-department nodes and aggregation nodes, and upon receiving... After all cross-departmental nodes and aggregation nodes have completed their pre-update signals, a fund transfer trigger instruction is sent to the smart contract. This ownership update instruction includes updated ownership time-series data and graph update confirmation results. If the smart contract reports a successful fund transfer and generates a final fund transfer record including the accounts of both parties, the transfer amount, and the final transfer timestamp, an ownership update confirmation instruction is sent to the cross-departmental nodes and aggregation nodes. The smart contract also receives the final update completion signals from all cross-departmental nodes and aggregation nodes. If the smart contract reports a failed fund transfer, an ownership pre-update rollback instruction is sent to the cross-departmental nodes and aggregation nodes to revert the update operation and generate a fund transfer failure explanation. The fund custody certificate, updated ownership time-series data, graph update confirmation results, combined with the final update completion signals and final fund transfer records from each cross-departmental node and aggregation node, or the fund transfer failure explanation, form a full-chain registration record for real estate secondary transactions. This full-chain registration record is transmitted to the blockchain network for notarization, thereby achieving full-chain registration management of real estate secondary transactions.
6. The method according to claim 1, characterized in that, When real estate enters the secondary transaction process and the RFID reader reads the real estate code, the corresponding ownership change timeline data is obtained, including: when real estate enters the secondary transaction process and the RFID reader reads the real estate code, a trigger command is generated based on the real estate code and the reader device identifier; the trigger command is sent to the access verification node of the blockchain network, and the access verification node performs permission verification on the reader device identifier, generating a permission verification result; if the permission verification result is successful, the trigger command is sent to multiple cross-department nodes in the blockchain network, including the real estate initial registration department node, the ownership change registration department node, the transaction filing department node, and the tax registration department node; after each cross-department node receives the trigger command, it queries the target historical records related to the real estate based on the real estate code, and the target historical records include changes in the right holder of the real estate corresponding to different timestamps. The system collects information, registration status change information, and change approval document numbers; adds node identifiers to the target historical records to form identified historical records, and transmits the identified historical records to the aggregation node of the blockchain network; after receiving the identified historical records transmitted by each cross-department node, the aggregation node compares the content of different identified historical records corresponding to the same timestamp, generates content comparison results, and performs integrity verification on the identified historical records to generate integrity verification results; based on the integrity verification results and the content comparison results, the identified historical records are classified to obtain valid historical records, conflict record lists, incomplete record lists, and invalid record lists; the timestamps in the valid historical records are calibrated to obtain calibrated timestamps; based on the calibrated timestamps, the valid historical records, conflict record lists, incomplete record lists, invalid record lists, node identifiers, and change approval document numbers are integrated to form ownership change time-series data.
7. The method according to claim 1, characterized in that, When the verification passes, the ownership change time series data is transformed into a spatiotemporal graph, including: when the verification passes, determining the core dimensions of the spatiotemporal graph based on the ownership change time series data, wherein the core dimensions include a time dimension, a right holder dimension, a registration status dimension, and a location association dimension; based on the core dimensions, creating a time node for each calibrated timestamp, creating a right holder node for each right holder change information, creating a status node for each registration status change information, and creating a location association node for the real estate location association information corresponding to the change approval document number; establishing association relationships between time nodes, right holder nodes, status nodes, and location association nodes under the same calibrated timestamp to form basic association units; establishing supplementary association relationships between the list nodes corresponding to each timestamp in the conflict record list, incomplete record list, and invalid record list, and the time nodes corresponding to the calibrated timestamps in the basic association units; and connecting all basic association units and the supplementary association relationships to form a spatiotemporal graph.
8. A blockchain-based real estate registration management and transaction system, characterized in that, include: The association module is used to acquire the passive RFID electronic tag of the real estate during the initial registration process, associate the real estate code in the passive RFID electronic tag with the distributed identity certificate of the real estate owner to obtain association data, and transmit the association data to the blockchain network for evidence storage; the acquisition module is used to acquire the ownership change time sequence data corresponding to the real estate when the real estate enters the second-hand transaction process and the RFID reader reads the real estate code. The conversion module is used to verify the ownership change time series data. When the verification is successful, the ownership change time series data is converted into a spatiotemporal map. The authentication module is used to authenticate the identities of both parties in the real estate second-hand transaction through distributed identity authentication technology, generate the identity authentication results of both parties, and compare the identity authentication results with the real estate historical rights holder information in the spatiotemporal map to obtain the ownership comparison result. The verification module is used to verify the ownership restrictions of real estate based on the ownership comparison results and smart contracts in the blockchain network, obtain the verification results, and perform transaction fund transfer and ownership information update operations based on the verification results, so as to realize the full-chain registration management of real estate secondary transactions.
9. A computing device, characterized in that, It includes a processing component and a storage component; the storage component stores one or more computer instructions; the one or more computer instructions are invoked and executed by the processing component to implement a blockchain-based real estate registration management transaction method as described in any one of claims 1 to 7.
10. A computer storage medium, characterized in that, The system contains a computer program that, when executed by a computer, implements a blockchain-based real estate registration management transaction method as described in any one of claims 1 to 7.