Cultural and artistic product transaction double-layer settlement blockchain storage system with fusion regulatory node

Abstract

The application discloses a cultural and artistic product transaction double-layer settlement blockchain storage system fusing a supervision node, and particularly relates to the field of cultural and artistic product transaction, and is used for solving the problems of audit difficulty and increased disputes caused by the inconsistency of right change and fund clearing timing and the lag of supervision intervention in the existing platform, receiving a transaction confirmation through an event filing unit, creating a unique event record and sending an abstract to the supervision node, receiving a receiving and paying confirmation through an anchor binding unit, establishing a reconciliation anchor binding reference position and supervision endorsement, calculating timing consistency and endorsement intersection through a plan arrangement unit, generating an execution plan and setting a supervision entry, writing a ledger according to the plan through a submission execution unit, listening to a confirmation and processing rollback, summarizing records through a reconciliation checking unit, generating a credential and checking differences, and further realizing cross-ledger consistency delivery and supervision preposition, guaranteeing transparent and traceable transaction, and improving the compliance and efficiency of the cultural and artistic product market.

Description

Technical Field

[0001] This invention relates to the field of cultural and artistic product transactions, and more specifically, to a two-tiered blockchain-based evidence storage system for cultural and artistic product transactions that integrates regulatory nodes. Background Technology

[0002] The cultural and artistic product trading platform revolves around the processes of rights confirmation, evidence preservation, display, bidding, transaction, clearing, and delivery. Rights changes are recorded in the project's blockchain ledger, while payments are settled in the funds ledger or clearing channel. Regulatory nodes participate in endorsement and auditing according to governance procedures. The business chain, from listing to delivery, encompasses ownership transfer, payment settlement, royalty distribution, and compliance blocks. Data flows multiple times between the blockchain and the blockchain side, forming a multi-source event flow and multi-channel status confirmation. The auditing side requires a closed-loop evidence system within the same audit domain, while the regulatory side requires strong constraints on freezing and revocation entry points in the write path. Transaction matching and clearing execution rely on consistent event semantics and reliable sequential relationships.

[0003] However, the rights ledger and the funds ledger reside in different accounting domains, lacking a unified data model for cross-domain atomic settlement and verifiable reconciliation. When the rights side transfers ownership first or the funds side clears accounts first, the arrival and confirmation times of events are not consistent, making it easy for successful submissions and failed rollbacks to be separated. Partial submissions occur between the on-chain state and the liquidation state, and the rollback granularity and retry path are difficult to align. After concurrent transactions, cancellations, rollbacks, and supplementary entries are superimposed, the rearrangement of event order in different channels leads to state race conditions, and the freezing and cancellation of regulatory nodes cannot be done before the write operation. To facilitate strong hook intervention, endorsement strategies and member governance cannot provide source verification for settlement semantics. The direct consequences are inconsistent reconciliation, incomplete audit evidence, increased difficulty in dispute adjudication, long-term separation between rule-compliant blocks and settlement blocks, and a lack of publicly available on-chain evidence for royalty distribution and service fee clearing. The core technical issues lie at the data processing layer, focusing on the coordination gaps in event state machines, cross-ledger submission and rollback orchestration, and sequence constraints and consistency proofs. There is an urgent need to establish executable, auditable, and traceable settlement semantics between the consortium blockchain and the clearing channel.

[0004] To address the aforementioned problems, a technical solution is provided. Summary of the Invention

[0005] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a two-layer settlement blockchain evidence storage system for cultural and artistic transactions that integrates regulatory nodes. The system utilizes an event archiving unit to receive transaction confirmation identifiers from the transaction module, create settlement event records and generate unique event identifiers, write artwork and transaction party information into entries, define fixed fields, and send event summaries to regulatory nodes for monitoring. Anchor binding units receive payment confirmations, establish reconciliation anchor binding event identifiers, record the positions of rights and funds in the ledger, integrate regulatory endorsement, and generate receipt snapshots. A planning and orchestration unit extracts timing consistency and endorsement intersection parameters, uses a sequential likelihood ratio test to output an execution plan, and sets regulatory freeze and revocation entry points. An execution submission unit writes the plan into the ledger, monitors confirmation, and handles rollbacks. A reconciliation verification unit summarizes records, generates vouchers, verifies consistency, and corrects discrepancies, thereby addressing the problems mentioned in the background art.

[0006] To achieve the above objectives, the present invention provides the following technical solution:

[0007] Event Filing Unit: Receives transaction confirmation identifiers, creates settlement event records and assigns unique event identifiers, binds work identifiers and counterparty identifiers, registers regulatory roster versions and regulatory strategy locations, and publishes event summaries to regulatory nodes for pre-emptive monitoring;

[0008] Anchor Binding Unit: Acceptance and payment confirmation identifier, generates reconciliation anchor points and binds them one by one with event identifiers, records the reference positions of the rights ledger and funds ledger, writes them into the regulatory endorsement position and establishes a mapping between receipts and payments and transactions;

[0009] The planning unit extracts the time-series consistency quantity and the endorsement intersection quantity, uses the sequential likelihood ratio test to generate the atomicity judgment index, selects atomic submission, delayed review or pre-rollback, and sets the regulatory freeze entry and revocation entry in the plan summary;

[0010] Submitting the execution unit: Write the transfer information in the rights ledger and the clearing information in the funds ledger according to the plan; monitor the confirmation and supervision instructions of the two ledgers; if the conditions are not met or a freeze instruction is received, correct the writing according to the pre-rollback and record the trajectory.

[0011] Reconciliation and verification unit: Summarize transaction receipts, payments, transfers, rollbacks, and regulatory records at the event identifier level, generate verifiable reconciliation vouchers, complete consistency and compliance verification, update records and trigger limited-scope review when discrepancies exist.

[0012] Furthermore, the event filing unit receives the transaction confirmation identifier from the transaction matching module, creates a settlement event record and generates a unique event identifier, writes the work identifier and the counterparty identifier into the same event entry, defines a fixed set of fields including source channel identifier, generation time tag, event status field, plan summary field, consistency check field, anchor reference field, regulatory roster field and regulatory strategy reference location, constructs a deduplicated fingerprint and performs idempotency verification before saving it to disk, and generates an event summary to send to the regulatory node cache area.

[0013] Furthermore, the anchor binding unit receives payment confirmation identifiers from the clearing channel, establishes reconciliation anchors in the settlement event record, binds the reconciliation anchors to the event identifiers one by one, records the reference positions of the rights ledger and the funds ledger, parses the most recent endorsement summary of the regulatory node to generate the regulatory endorsement reference position and writes it into the reconciliation anchor, establishes the mapping relationship between payment confirmation identifiers and transaction confirmation identifiers and the three-way association with the regulatory endorsement reference position, generates a source receipt snapshot and writes it back to the settlement event record.

[0014] Furthermore, the planning and orchestration unit extracts the reference positions of the rights ledger and the funds ledger from the settlement event records and reconciliation anchor points, compares the same source relationship, the corresponding relationship of the summary structure, and the relationship of the generation order to form a sequence comparison table, applies a monotonic mapping function to output the temporal consistency quantity, analyzes the most recently confirmed endorsement summary set of the rights ledger, the most recently confirmed endorsement summary set of the funds ledger, and the endorsement participation set of the regulatory node, calculates the intersection coverage relationship, and applies a monotonic mapping function to output the endorsement intersection quantity.

[0015] Furthermore, the planning and scheduling unit inputs the time-series consistency quantity and the endorsement intersection quantity into the order likelihood ratio test process, initializes the cumulative statistic to zero, calculates and accumulates the log-likelihood difference for each piece of evidence, compares it with the upper and lower bound thresholds, outputs an atomic plan submission signal, a pre-rollback plan signal, or a delayed review plan signal, and simultaneously stores it in the settlement event record.

[0016] Furthermore, the execution unit performs transfer writing in the rights ledger and clearing writing in the funds ledger according to the plan summary, registers the writing intent hash and starts the receipt listening, and verifies the rights ledger confirmation and funds ledger confirmation by matching the event identifier and target reference position. When the plan summary requirements are met, the transfer confirmation result is written in the settlement event record and the rights ledger reference position, funds ledger reference position and confirmation time are fixed.

[0017] Furthermore, when the confirmation of the rights ledger or the funds ledger does not meet the requirements of the plan summary, or when the execution unit receives a regulatory freeze instruction through the regulatory channel, it generates a rollback instruction, writes and executes the corresponding write-back or cancellation write according to the pre-rollback plan location, and simultaneously corrects the event status field and the reference position of the rights ledger and the reference position of the funds ledger in the settlement event record, records the rollback trajectory, the summary of the triggering reason and the regulatory triggering information, and writes it back to the plan summary and event entry.

[0018] Furthermore, the reconciliation verification unit summarizes transaction confirmation identifiers, payment confirmation identifiers, transfer confirmation results, rollback trajectories and regulatory freeze entry and regulatory revocation entry records at the event identifier granularity, generating verifiable reconciliation vouchers that include snapshots of the rights ledger reference location, snapshots of the funds ledger reference location, snapshots of the most recently confirmed endorsement summary set of the rights ledger, snapshots of the most recently confirmed endorsement summary set of the funds ledger, snapshots of the regulatory node endorsement participation set, snapshots of the atomic submission plan, and judgment trajectory index.

[0019] Furthermore, the reconciliation verification unit performs consistency verification. First, it verifies the same-origin relationship and entry consistency between the snapshot of the reference location in the rights ledger and the snapshot of the reference location in the funds ledger. Then, it verifies the intersection and coverage relationship between the snapshot of the most recently confirmed endorsement summary set in the rights ledger, the snapshot of the most recently confirmed endorsement summary set in the funds ledger, and the snapshot of the endorsement participation set in the regulatory node. Finally, it verifies the consistency relationship between the snapshot of the atomic submission plan and the transfer confirmation result, and between the rollback trajectory and the regulatory freeze entry record.

[0020] Furthermore, when the reconciliation verification unit discovers inconsistencies in the snapshots of the rights ledger reference locations, conflicts in the snapshots of the most recently confirmed endorsement summary set of the rights ledger, inconsistencies between the execution of the atomic submission plan snapshot and the transfer confirmation results, or when the regulatory freeze entry trigger is not recorded, it generates a discrepancy list and marks the generation stage. The discrepancy list is written into the settlement event record and plan summary and triggers a limited-scope review. The review is only performed on the rights ledger reference location snapshots and related entries involved in the discrepancy list. After the review is completed, the consistency verification result and verifiable reconciliation voucher reference are output.

[0021] The technical effects and advantages of this invention, which integrates a two-tiered settlement blockchain evidence storage system for cultural and artistic transactions with regulatory nodes, are as follows:

[0022] This invention uses a unique event identifier to govern both the rights ledger and the funds ledger. Settlement event records and reconciliation anchors form a common-source reference. The sequence likelihood ratio test converges the temporal consistency quantity and endorsement intersection quantity at the plan entry point, outputting a single execution conclusion and driving commit or pre-rollback. The commit semantics and rollback semantics remain consistent. Parallel writing and regulatory freeze entry points are linked within the plan summary, enabling anomalies to be quickly contained in the write path. Finally, verifiable reconciliation vouchers solidify the transaction, payment, transfer, and regulatory evidence into a replayable link, suppressing partial commits and sequence rearrangements, and improving the consistency and verifiability of compliance audits and royalty settlement. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of the structure of the dual-layer settlement blockchain evidence storage system for cultural and artistic transactions that integrates regulatory nodes, as described in this invention. Detailed Implementation

[0024] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] Example 1: Figure 1 This invention presents a two-tiered blockchain-based evidence storage system for cultural and artistic transactions, integrating regulatory nodes, comprising:

[0026] Event Filing Unit: Receives transaction confirmation identifiers, creates settlement event records and assigns unique event identifiers, binds work identifiers and counterparty identifiers, registers regulatory roster versions and regulatory strategy locations, and publishes event summaries to regulatory nodes for pre-emptive monitoring.

[0027] Anchor Binding Unit: Acceptance and payment confirmation identifier, generates reconciliation anchor points and binds them one by one with event identifiers, records the reference positions of the rights ledger and funds ledger, writes them into the regulatory endorsement position, and establishes a mapping between receipts and payments and transactions.

[0028] The planning unit extracts the time-series consistency quantity and the endorsement intersection quantity, uses the sequential likelihood ratio test to generate the atomicity judgment index, selects atomic submission, delayed review or pre-rollback, and sets the regulatory freeze entry and revocation entry in the plan summary.

[0029] Submitting the execution unit: Write the transfer information in the rights ledger and the clearing information in the funds ledger according to the plan. Monitor the rule confirmation and regulatory instructions of the two ledgers. If the conditions are not met or a freeze instruction is received, correct the writing according to the pre-rollback and record the trajectory.

[0030] Reconciliation and verification unit: Summarize transaction receipts, payments, transfers, rollbacks, and regulatory records at the event identifier level, generate verifiable reconciliation vouchers, complete consistency and compliance verification, update records and trigger limited-scope review when discrepancies exist.

[0031] In the two-tiered settlement blockchain evidence storage system of cultural and artistic product trading platforms, the heterogeneity between the rights ledger and the funds ledger leads to a mismatch in event triggering timing, causing some submission and state race conditions, and making it difficult for regulatory nodes to embed endorsement strategies to achieve pre-emptive compliance constraints. By introducing event filing units, a unified identifier and summary mechanism can be established at the beginning of the settlement event, ensuring the common basis of subsequent anchor binding and planning, thereby providing a traceable atomicity determination starting point for cross-ledger consistency settlement.

[0032] 1-1. Receive the transaction confirmation flag and create a settlement event record.

[0033] In the trading process of cultural and artistic products trading platforms, transactions often involve multiple event streams, and the broadcasting of bids and transactions can easily lead to confusion in historical records. The event archiving unit receives transaction confirmation identifiers from the transaction matching module. This identifier serves as a trigger signal for the settlement event and includes transaction details such as price, timestamp, and participant verification, ensuring the integrity and legality of the input data. The receiving process employs an asynchronous message queue mechanism to parse the JSON structure of the transaction confirmation identifier, extracting core fields including transaction price, transaction time, and associated hash, and temporarily storing them in a memory buffer. Subsequently, based on these extracted fields, a unique event identifier is generated using a UUID algorithm combined with the transaction time and random entropy, ensuring global uniqueness and unpredictability. The settlement event record is initialized as a structured data object containing a predefined key-value pair framework, and the unique event identifier is injected into this record as the primary key, enabling independent tracking at the event level.

[0034] The transaction matching module is a core component of a trading platform used to automatically match buy and sell orders. It is primarily used in financial markets, e-commerce, and blockchain-based evidence storage systems. By receiving orders from both buyers and sellers, it compares and matches them in real time according to preset rules such as price priority and time priority. A transaction is completed when the buyer's bid is higher than or equal to the seller's offer, and a corresponding confirmation identifier is generated for subsequent settlement processes. The transaction matching module handles the display, bidding, and transaction stages, ensuring the accuracy and traceability of the initial trigger points for changes in rights and payment settlement, thus providing the event archiving unit with transaction confirmation identifiers as input.

[0035] 1-2. Write the work identifier, the counterparty identifier, and a set of fixed fields.

[0036] After the settlement event record is created, it needs to be bound to a specific transaction entity and pre-defined standardized fields to form a closed contextual association, supporting cross-layer referencing and verification of subsequent units. The event archiving unit directly writes the artwork identifier and the counterparty identifier into the same event entry of the settlement event record. The artwork identifier refers to the unique digital fingerprint of the cultural and artistic work, such as an NFT hash, while the counterparty identifier includes the public key address or consortium blockchain account ID of the buyer and seller, ensuring atomic binding of these identifiers within the entry and preventing subsequent reference drift. Through key-value mapping, the event entry is expanded into a nested dictionary structure, with the artwork identifier placed in the `artwork_key` field and the counterparty identifier placed in the `buyer_id` and `seller_id` subfields. Simultaneously, a fixed set of fields is clearly defined, including: a source channel identifier for tracing the event origin; a generation timestamp using UTC timestamp format to record the creation time; an event status field initialized to "pending" to indicate a pending status; a plan summary field reserved as an empty placeholder for the plan orchestration unit to fill; a consistency check field initially empty for the reconciliation check unit's result write-back; an anchor reference field reserved for the anchor binding unit's binding result; a regulatory roster field capturing the current regulatory roster version; and a regulatory policy reference pointing to the blockchain block height and hash of the policy document. These fields are enforced through enumeration types to ensure the structural integrity of the settlement event records.

[0037] 1-3. Construct a deduplicated fingerprint, perform idempotency verification, and then save it to disk.

[0038] After the fixed set of fields is written, a deduplication mechanism is needed to prevent duplicate events caused by concurrent transactions and maintain ledger purity. The event archiving unit uses the transaction confirmation identifier, work identifier, and counterparty identifier as input. A deduplication fingerprint is constructed using the SHA-256 hash algorithm. Specifically, these identifiers are concatenated and hashed in one direction to generate a fixed-length fingerprint value. The local database or blockchain index is then queried to check if the deduplication fingerprint exists. If it does not exist, an idempotent check is performed, and the complete settlement event record is persistently saved to the project blockchain's dedicated storage layer, ensuring atomic writes and transaction isolation. Simultaneously, a regulatory roster field is recorded in the settlement event record, specifically capturing the current regulatory roster version and associating it with the regulatory policy reference position to ensure this information is updated synchronously. This field uses a version control mechanism, such as writing the roster version and policy position as immutable additional attributes to the event entry, supporting the intersection and coverage verification of the reconciliation unit.

[0039] 1-4. Generate an event summary and send it to the monitoring node's cache.

[0040] After settlement event records are stored on disk, to enable pre-monitoring by regulatory nodes, key information must be extracted to minimize transmission overhead, and regulatory nodes must be notified promptly to inject potential freeze or revocation hooks. The event documentation unit generates an event summary, which is refined into a compact JSON object including a unique event identifier, work identifier, counterparty identifier, source channel identifier, and generation timestamp. This ensures that these elements cover the core semantics of the settlement event without disclosing sensitive details, such as excluding price or endorsement information to comply with privacy requirements. The event summary is then sent to the regulatory node's cache via a dedicated regulatory channel. This channel uses the WebSocket protocol for real-time push, ensuring low-latency transmission. Before sending, the event summary is digitally signed using the event documentation unit's private key to verify the source's authenticity. Upon receipt, the regulatory node stores it in its local cache for subsequent endorsement participation and compliance entry matching.

[0041] The processing logic of the event filing unit establishes a unified foundation for settlement events through the above steps, ensuring that subsequent operations of the rights ledger and the funds ledger have a traceable common source anchor point. This effectively alleviates the problems of event mismatch and post-regulation in the two-layer settlement scenario of cultural and artistic transactions, and realizes the pre-injection of evidence closure and compliance simulation.

[0042] The event documentation unit, by creating settlement event records and generating event summaries, establishes a unified starting point for settlement events and a foundation for pre-regulatory monitoring, ensuring the traceability of subsequent units. The introduction of the anchor binding unit allows for the receipt and payment confirmation identifiers from the clearing channel to generate reconciliation anchors and achieve precise binding with event identifiers. It also records the reference positions in the rights ledger and funds ledger and integrates a regulatory endorsement mechanism. This provides cross-ledger anchoring support for the atomicity determination of the planning and scheduling unit and the evidentiary closure of the reconciliation verification unit, effectively mitigating issues of inconsistent event arrival order and mismatched confirmation timing, and achieving compliance and consistency assurance for two-tier settlement.

[0043] 2-1. Receive payment confirmation marks and establish reconciliation anchors.

[0044] The separation of clearing and transfer paths in cultural and artistic product trading platforms often leads to drifting of reference positions and partial submissions. The anchor binding unit receives payment confirmation identifiers from the clearing channel. This identifier serves as a settlement trigger signal for the funds ledger and includes payment details such as amount, timestamp, and verification signature. The receiving process employs a message subscription mechanism, parsing the structured format of the payment confirmation identifier, extracting core fields including payment amount, payment time, and associated hash, and temporarily caching them in a dedicated buffer. Subsequently, a reconciliation anchor is established within the settlement event record. This reconciliation anchor is initialized as an independent data structure object containing a preset key-value frame for subsequent binding and position recording, achieving extended anchoring of settlement events.

[0045] 2-2. Bind event identifiers and record two types of reference locations.

[0046] After the reconciliation anchor is established, it needs to be associated with existing events and the location information of heterogeneous ledgers needs to be captured to form a verifiable cross-domain reference. The anchor binding unit binds the reconciliation anchor to the event identifier one by one, ensuring a unique correspondence through a hash mapping mechanism. Subsequently, the rights ledger reference position and the funds ledger reference position are recorded. These positions are organized according to a unified field structure: the rights ledger reference position specifically includes a chain identifier to distinguish consortium chain instances, a channel name to indicate a specific business channel, a block height index to indicate the block height, a transaction hash digest as a unique hash of the transaction, and a block entry time tag in UTC format to record the confirmation time; the funds ledger reference position follows the same field structure and is associated with the event identifier in the same event entry to ensure the atomic embedding of the two types of reference positions and support subsequent time-series consistency quantity calculations.

[0047] 2-3. Analyze the regulatory endorsement and write it to the location.

[0048] After recording the two types of reference positions, to inject compliance constraints, the endorsement information of the regulatory node must be integrated to establish a three-way association basis. The anchor binding unit parses the most recent endorsement summary of the regulatory node. This summary is obtained from the regulatory channel and includes the set of endorsement participants and signature verification details. Key elements such as endorsement time and hash are extracted through JSON parsing. Subsequently, a regulatory endorsement reference position is generated. The structure of this position is consistent with the two types of reference positions, including chain identifier, channel name, block height index, transaction hash summary, and block entry time tag. This information is directly written to the reconciliation anchor to ensure the immutable anchoring of regulatory information and facilitate the quantitative assessment of endorsement intersection.

[0049] 2-4. Establish mapping relationships and generate source receipt snapshots.

[0050] After the regulatory endorsement location is written, a multi-party mapping needs to be constructed to close the evidence chain, and the results are written back for downstream units to read. The anchor binding unit establishes a mapping relationship between the payment confirmation identifier and the transaction confirmation identifier. This mapping adopts a key-value pair format, with the payment confirmation identifier as the primary key linking the transaction confirmation identifier, and is extended to a three-way association with the regulatory endorsement reference location to ensure semantic consistency among the three. Subsequently, a source receipt snapshot is generated. This snapshot captures the real-time status of the current reconciliation anchor reference, the two types of reference location snapshots, and the regulatory endorsement reference location. This information is solidified through serialization and written back to the corresponding fields of the settlement event record, such as the anchor reference field and the reserved area of ​​the plan summary field, supporting the time-series comparison of the plan orchestration unit and the generation of the difference list of the reconciliation verification unit.

[0051] The processing logic of the anchor binding unit, through the above processing, constructs a cross-ledger reconciliation anchor mechanism to ensure that the reference positions of the rights ledger and the funds ledger are bound to the same source, and incorporates regulatory endorsement to achieve evidence closure and compliance before the two-layer settlement. This effectively solves the problem of the separation process between clearing and transfer in the context of cultural and artistic transactions, and improves audit efficiency and the transparency of dispute resolution.

[0052] The anchor binding unit has established a cross-ledger mapping relationship by generating reconciliation anchors and binding event identifiers, recording two types of reference locations and regulatory endorsement locations, thus laying the data foundation for subsequent atomicity determination. Through the introduction of the plan orchestration unit, the temporal consistency quantity and endorsement intersection quantity can be extracted from settlement event records and reconciliation anchors. An atomicity determination index is generated using the sequential likelihood ratio test method, thereby selecting an appropriate execution plan. Regulatory freeze and revocation entry points are set in the plan summary, enabling predictive control of event mismatches and state race conditions, ensuring temporal consistency and compliance pre-injection in two-layer settlement.

[0053] The temporal consistency measure ensures the consistency of settlement events at specific points in time by comparing the source relationships, structural correspondences, and generation order of references between the two ledgers, avoiding partial submissions caused by separate processes such as transfer before clearing or vice versa. The endorsement intersection measure verifies the embedding depth of compliance constraints by calculating the intersection coverage relationship between the set of endorsement summaries of the two ledgers and the set of endorsement participants of regulatory nodes, preventing evidence non-closure issues caused by scattered endorsement sets. These quantitative indicators collectively support the generation of the atomicity determination index, selecting atomic submission, delayed review, or pre-rollback plans, thereby improving the atomicity of cross-ledger settlements, audit efficiency, and transparency of dispute resolution, effectively mitigating the risks of post-regulatory and reconciliation discrepancies.

[0054] 3-1. Extract parameters and calculate timing consistency quantities.

[0055] In the concurrent transaction process of cultural and artistic product trading platforms, the separation process of transferring ownership before clearing or vice versa often leads to timing mismatches. The planning and orchestration unit extracts relevant parameters from settlement event records and reconciliation anchors, including specific fields such as chain identifier, channel name, block height index, transaction hash digest, and block entry timestamp for the reference positions in the rights ledger and funds ledger. Subsequently, a timing consistency quantity is calculated by comparing the matching degree of these positions in the homology relationship, the similarity in the correspondence of digest structures, and the logical consistency in the generation order, forming a sequential comparison table. This table uses an ordered list structure to organize each comparison item. Based on this table, a monotonic mapping function is applied to convert the multidimensional comparison results into single-value quantization results. This function ensures that the mapping output is a continuous value within the positive real number range, facilitating subsequent input verification and supporting the quantization basis for atomicity determination.

[0056] The specific operation of applying the monotonic mapping function is to map the multidimensional alignment results in the sequential alignment table into a single quantized value through linear normalization. For example, for each alignment item, calculate its relative position with respect to the difference between the minimum and maximum values ​​of the set, thereby outputting a continuous single-value result in the positive real number interval.

[0057] 3-2. Calculate the intersection of endorsements.

[0058] After calculating the time-series consistency measure, the intersection of endorsement participants must be quantified to assess the coverage of the compliance simulation. The planning and orchestration unit parses the most recently confirmed endorsement digest set from the rights ledger and the most recently confirmed endorsement digest set from the funds ledger. These sets are extracted from the transaction hash digests of the two types of reference locations and contain a list of endorsement participant public keys and signature verification details. Simultaneously, the set of regulatory node endorsement participants is parsed, obtaining relevant information from the regulatory endorsement reference locations. The intersection coverage relationship is then calculated. Set operations determine the proportion of common elements between the two ledger endorsement digest sets and the regulatory node endorsement participant set. A monotonic mapping function is applied to output a single-value quantification result. This function maps the coverage proportion to a standardized score, ensuring consistency with the dimensions of the time-series consistency measure and facilitating unified processing during the comprehensive verification process.

[0059] The formulas for calculating the temporal consistency quantity and the endorsement intersection quantity are as follows:

[0060] For timing consistency metrics, a sequential alignment table is first created, which contains multiple alignment entries. (representing the first) Several comparison dimensions, such as the matching degree value of homology relationship, the similarity value of summary structure correspondence, or the logical consistency value of generation order relationship, ranging from [0,1], are then quantized using a monotonic mapping function:

[0061] ;

[0062] in:

[0063] This represents the temporal consistency quantity, which is used as a single-value quantization result and is then used as input for the subsequent order likelihood ratio test.

[0064] Indicates the first in the order comparison table The specific values ​​of each comparison item;

[0065] Indicates the first Preset weights for each comparison item ensure ;

[0066] Indicates the total number of comparison items;

[0067] Indicates all comparison items A set;

[0068] and Representing sets The minimum and maximum values ​​are used to achieve normalization mapping to the [0,1] interval.

[0069] The amount of endorsement intersection is quantified by calculating the intersection coverage relationship:

[0070] ;

[0071] in:

[0072] This represents the endorsement intersection, which is used as a single-value quantization result and is then used as input for the subsequent order likelihood ratio test.

[0073] This represents the most recently confirmed set of endorsement summaries in the rights ledger, including endorsement participant identifiers;

[0074] This represents the set of endorsement summaries most recently confirmed in the funds ledger, including the endorsement participant identifiers;

[0075] This represents the set of participants endorsing the regulatory node, including the identifiers of the endorsing participants;

[0076] The cardinality (number of elements) of a set;

[0077] Then apply the monotonic mapping function. (In this scenario, it is an identity mapping to ensure the monotonically increasing property.) Output the final quantized value.

[0078] To facilitate understanding how to calculate the temporal consistency quantity and the endorsement intersection quantity, the following example is provided:

[0079] Assume the specific fields of the rights ledger reference location are chain identifier A, channel name B, block height index 100, transaction hash digest H1, and block entry time stamp T1, and the reference location of the funds ledger is chain identifier A, channel name B, block height index 101, transaction hash digest H2, and block entry time stamp T2, where T2 is later than T1. When comparing the same source relationship, the chain identifier and channel name are completely matched and assigned a matching degree of 1. The corresponding relationship of the digest structure is assigned a similarity of 0.9 through field format comparison. The generation order relationship is assigned a logical consistency of 1 because T1 is earlier than T2. ​​The resulting order comparison table contains three items: 1, 0.9, and 1. The monotonic mapping function is applied to normalize the relative position of each item with respect to the minimum value 0 and the maximum value 1 of the whole set. After calculating each item, the average value is obtained to obtain the time consistency quantity of 0.967. Assume the most recently confirmed endorsement summary set of the rights ledger is Node 1, Node 2, Node 3; the most recently confirmed endorsement summary set of the funds ledger is Node 1, Node 2, Node 4; and the endorsement participation set of the regulatory node is Node 1, Node 2, Node 3, Node 5. Calculate the common elements of the two ledger endorsement summary sets as Node 1 and Node 2, obtaining an intersection size of 2. Then, divide this intersection size by 5, which equals 0.4, to form a coverage relationship value of 0.4. Apply a monotonic mapping function to normalize the relative position of this coverage relationship value with respect to the preset minimum value 0 and maximum value 1, outputting the endorsement intersection amount of 0.4.

[0080] 3-3. Perform a sequence likelihood ratio test to generate an atomicity determination index.

[0081] After calculating the endorsement intersection, the two quantification results need to be combined to determine the execution strategy, avoiding misalignment of rollback granularity. When the planning and orchestration unit performs the order likelihood ratio test to generate the atomicity decision index, it first integrates the temporal consistency quantity and the endorsement intersection quantity into an ordered evidence sequence. This sequence is treated as a series of independent observation data points, each representing the correspondence between the two quantification results in a specific dimension, such as the order of temporal matching or the proportion of intersection covered by endorsements, thus forming an input set that can be processed item by item. This process initializes a cumulative statistic to zero as the starting benchmark for the test, used to gradually accumulate evidence strength. Subsequently, the system iterates through each observation data point in the evidence sequence, evaluating the difference in probability distribution for each data point under the two scenarios of hypothesis consistency being true and false. This difference is quantified by calculating the logarithmic likelihood ratio, and this ratio is accumulated to the cumulative statistic, ensuring that the accumulation process reflects the asymptotic weight distribution of the evidence. After accumulation, the final cumulative statistic is compared with pre-set upper and lower thresholds: if the cumulative statistic exceeds the upper threshold, the event is deemed to have high overall consistency, generating an atomic commit plan signal, allowing for the direct simultaneous execution of rights ledger transfer and funds ledger clearing; if the cumulative statistic is below the lower threshold, a significant mismatch risk is identified, generating a pre-rollback plan signal to prepare for early reversal of potential anomalies to avoid state race conditions; if the cumulative statistic is between the upper and lower thresholds, insufficient evidence for immediate decision-making is identified, generating a delayed review plan signal, requiring additional verification steps such as re-querying the reference position or endorsement set to further clarify uncertainties. This verification mechanism, through a sequential processing dynamic decision-making framework, ensures that the generation of the atomicity judgment index is both efficient and reliable, supporting the predictive control of event rearrangement and mismatch in concurrent transaction scenarios, thereby maintaining overall consistency and compliance across ledger transactions.

[0082] For example:

[0083] The formula for calculating the order likelihood ratio test is as follows, where all parameters are defined based on the integrated evidence sequence of temporal consistency quantity and endorsement intersection quantity.

[0084] For each observation data point (representing the first in the sequence of evidence) For each independent observation (e.g., the quantization result of time-series matching or the specific correspondence of endorsement coverage ratio), calculate the log-likelihood difference:

[0085] ;

[0086] in:

[0087] Indicating consistency assumption (The overall timeline of the event is highly consistent with the endorsement) Observation data points The probability density function value;

[0088] Indicating the inconsistency assumption (Observation data points where there is significant time mismatch or insufficient endorsement coverage of the event) The probability density function value;

[0089] Indicates the first The log-likelihood difference of each observation is used to quantify the strength of evidence.

[0090] Subsequently, cumulative statistics By accumulating each item, we obtain:

[0091] ;

[0092] in:

[0093] This indicates the total number of observation data points that have been processed;

[0094] Indicates as of the date The cumulative statistics of each observation serve as the quantitative basis for the atomicity determination index.

[0095] Ultimately, Compared with the preset threshold:

[0096] like (Upper threshold, preset as a positive threshold, representing a highly consistent decision boundary), then an atomic submission plan signal is generated;

[0097] like (Lower bound threshold, preset to a negative threshold, representing the decision boundary of significant mismatch), then a pre-rollback plan signal is generated;

[0098] like Then a delayed review plan signal will be generated.

[0099] probability density function Predefined according to specific application scenarios (such as the normal distribution assumption) to match the distribution characteristics of the evidence sequence.

[0100] 3-4. Generate a plan summary and set up a monitoring entry point, and write back the settlement event record.

[0101] After the atomicity judgment index is generated, to provide actionable guidance and compliance hooks, the plan details must be solidified and retrospectively stored. The plan orchestration unit generates a plan summary, which includes judgment ranges such as threshold ranges, key observation summaries such as summaries of major comparison items, target reference positions such as the expected final values ​​of two types of reference positions, and expected execution order such as transfer priority or clearing priority. Simultaneously, the plan summary sets regulatory freeze and regulatory revocation entry points, including trigger condition fields defining specific abnormal thresholds, regulatory roster version fields referencing the current version, regulatory instruction receipt fields reserving instruction signature areas, and record location fields pointing to event entries. Subsequently, the plan summary, judgment trajectory indexes such as inspection step logs, and threshold snapshots are synchronously stored in the plan summary fields and consistency verification fields reserved in the settlement event record, ensuring seamless reading and verification by downstream submission execution units and reconciliation verification units.

[0102] The processing logic of the planning and orchestration unit, through the above steps, realizes the quantitative arrangement and plan generation of timing and endorsement parameters, ensuring the atomic execution path of the rights ledger and the funds ledger. This effectively solves the problems of state competition and post-regulation in the two-layer settlement scenario of cultural and artistic transactions, and improves the transparency of evidence and the efficiency of audit closure in handling transaction disputes.

[0103] The planning and orchestration unit has extracted the temporal consistency quantity and the endorsement intersection quantity, generated an atomicity determination index using the sequential likelihood ratio test, and set a regulatory entry point to provide a controllable execution path and rollback mechanism for submission execution. The submission execution unit performs write operations on the rights ledger and funds ledger according to the plan summary, while simultaneously monitoring confirmation and regulatory instructions. This enables atomic submissions under met conditions or pre-rollbacks under abnormal conditions, thereby ensuring eventual consistency and compliance intervention in cross-ledger settlements and mitigating reconciliation discrepancies caused by state race conditions and event reordering.

[0104] 4-1. Perform transfer write and clearing write.

[0105] In cultural and artistic product trading platforms, the separation of rights transfers and payment settlements often occurs due to heterogeneous ledgers, leading to inconsistent confirmation times. The submission execution unit, following the expected execution order specified in the plan summary, first performs a transfer write in the rights ledger. This write operation transfers the work identifier and the counterparty identifier from the seller's account to the buyer's account, updating the block structure of the rights ledger, including injecting the transaction hash digest and block timestamp, ensuring the immutability of the transfer record. Subsequently, a settlement write is performed in the funds ledger, deducting the amount corresponding to the payment confirmation identifier from the seller's funds account and transferring it to the buyer's funds account. Simultaneously, royalty allocation and service fee deductions are processed, updating the corresponding entries in the funds ledger and ensuring the semantic correlation between the settlement record and the rights transfer.

[0106] 4-2. Register the intent hash and start the receipt listener.

[0107] After a write operation is initiated, to track the execution status and prevent partial commits, the intent must be pre-registered and a real-time monitoring mechanism enabled. However, the commit execution unit separately registers the transfer write intent hash and the clearing write intent hash. These hashes are generated by calculating the concatenated hash of the written data using the SHA-256 algorithm, and are used for subsequent matching and verification. Subsequently, an acknowledgment listener is initiated. This listener adopts an event-driven model, filtering confirmation acknowledgments from the rights ledger and funds ledger by event identifier and target reference position, capturing the confirmation time and final reference position in real time, such as the block height index and transaction hash digest, ensuring that the listening process covers the expected execution order defined in the plan digest.

[0108] 4-3. Verify, confirm, and respond to regulatory instructions.

[0109] After the receipt monitoring is activated, it is necessary to verify whether the confirmations in both ledgers meet the plan requirements, and to handle potential regulatory interventions to achieve proactive compliance. Upon receiving confirmations from the rights ledger and the funds ledger, the submission execution unit matches and verifies them according to the event identifier, checking whether they meet the judgment interval and key observation summary of the plan summary. If both confirmations are compliant, the transfer confirmation result and clearing confirmation result are written into the event entries of the settlement event record, and the final reference positions and confirmation times for both types are fixed. If either confirmation is inconsistent or a regulatory freeze instruction is received through the regulatory channel (this instruction includes trigger condition fields and regulatory instruction receipt fields), a rollback instruction is immediately generated, further writing is suspended, and a correction path is prepared.

[0110] 4-4. Perform a rollback and record the trajectory, then write back the event log.

[0111] Following anomaly detection, targeted rollbacks and the solidification of audit trails are necessary to maintain ledger consistency. The execution unit locates the corresponding write position according to the pre-rollback plan and performs write reversal or cancellation operations, such as reversing transfer records in the rights ledger or returning clearing amounts in the funds ledger. Simultaneously, the event status field and two types of reference positions in the settlement event record are corrected. The rollback trail is then recorded, including a summary of the triggering reason (e.g., timing mismatch or regulatory freeze) and regulatory trigger information (e.g., instruction signature). The plan execution result, rollback trail references, and regulatory trigger information are written back to the plan summary and event entries, forming a complete replayable path. This supports the generation of a discrepancy list and consistency verification by the reconciliation unit.

[0112] The processing logic of the submitted execution unit achieves plan-driven write execution and exception response through the above steps, ensuring the atomicity confirmation and rollback of the rights ledger and the funds ledger. This effectively solves the reference drift problem caused by abnormal retries and supplementary entries in the two-layer settlement scenario of cultural and artistic transactions, and improves the review capability of the governance process and the closure of the evidence chain.

[0113] The commit execution unit has already achieved atomic commits or pre-rollbacks by executing transfer writes and clearing writes, listening for confirmations and regulatory instructions, and recording the trajectory to form a replayable path, providing a complete event state foundation for final verification. However, by introducing the reconciliation verification unit, multi-source records can be aggregated at the event identifier level to generate verifiable reconciliation vouchers and perform consistency and compliance verifications. This identifies and corrects potential discrepancies, ensures evidence closure and audit transparency across ledger transactions, and alleviates the problems of rising costs of proving disputes and difficulties in reviewing governance processes.

[0114] 5-1. Summarize the records and generate verifiable reconciliation vouchers.

[0115] Audits of cultural and artistic product trading platforms often struggle to establish a single domain of evidence closure due to concurrent writes to multiple ledgers. The reconciliation verification unit, using event identifiers as granularity, aggregates transaction confirmation identifiers, payment confirmation identifiers, transfer confirmation results, rollback trajectories, and regulatory entry records from settlement event records. These records include details of regulatory freeze and revocation entry points in the plan summary, as well as the confirmation time and final reference position of the submission to the execution unit. Subsequently, a verifiable reconciliation credential is generated. This credential is organized as a structured data object, containing the real-time status of the rights ledger reference position snapshot capture chain identifier, channel name, block height index, transaction hash digest, and block entry timestamp. The funds ledger reference position snapshot follows the same structure. The endorsement digest set snapshot extracts the most recently confirmed set of endorsement participants and signatures from both ledgers. The regulatory endorsement snapshot records the corresponding information of the regulatory node's endorsement participant set. The plan type snapshot solidifies the atomic commit or pre-rollback determination results. The step log of the trajectory index pointing to the order likelihood ratio test ensures that the credential covers the entire event lifecycle, supporting the evidentiary basis for public verification and dispute resolution.

[0116] 5-2. Verify the consistency between the cited location and the entry.

[0117] After verifiable reconciliation documents are generated, a basic check must be performed on the referenced locations to verify cross-ledger temporal consistency. The reconciliation verification unit performs consistency checks, first comparing the homology between the snapshots of the rights ledger referenced locations and the snapshots of the funds ledger referenced locations, checking whether the chain identifier and channel name match, whether the transaction hash digests are semantically related, and whether the order of the block timestamps matches the expected execution order. Subsequently, the consistency relationship of entries is checked, verifying whether the atomic bindings of the two types of referenced locations within the event entries are drift-free. For example, confirming the consistency between the work identifier and the counterparty identifier in the transfer confirmation result and the settlement confirmation result, ensuring that there is no position mismatch caused by partial commits, laying a reliable benchmark for subsequent advanced checks.

[0118] 5-3. Verify the consistency between the endorsement set and the plan execution.

[0119] After verifying the reference location, to assess compliance coverage and execution integrity, verification needs to be extended to the endorsement and planning levels. The reconciliation verification unit further verifies the intersection coverage relationship between the two ledger endorsement summary set snapshots and the regulatory endorsement snapshots. It calculates the proportion of co-endorsing participants through set operations and compares whether it meets the regulatory roster version field requirements set in the plan summary. Subsequently, it verifies the consistency relationship between the plan type snapshot, the final execution result, and the regulatory entry record. It checks whether the atomic submission plan corresponds to the non-abnormal state of the transfer confirmation result and the clearing confirmation result, or whether the pre-rollback plan matches the trigger reason summary of the rollback trajectory. At the same time, it verifies whether the regulatory freeze order or revocation order has been fully captured in the regulatory entry record, ensuring that the entire verification process covers the state competition and potential conflicts with regulatory intervention.

[0120] 5-4. Handle the discrepancies and trigger a limited-scope review.

[0121] During the consistency verification process, any discrepancies must be addressed systematically to maintain traceability. However, when the reconciliation verification unit detects inconsistencies in reference locations, endorsement set conflicts, discrepancies between plan execution and results, or unrecorded regulatory entry triggers, it generates a discrepancy list. This list indicates the generation stage, such as the writing or monitoring stage, and records the discrepancy details in the consistency verification field and plan summary of the settlement event record. Subsequently, a limited-scope review is triggered, specifically re-querying and verifying only the reference locations in the rights ledger, funds ledger, and related event entries involved in the discrepancy. This avoids a global reset to preserve the audit trail. Upon completion of the review, the consistency verification result is output, including the status of verification passed or corrected, and the final verifiable location of the reconciliation voucher reference, supporting closed-loop use for downstream auditing and dispute resolution.

[0122] The reconciliation and verification unit's processing logic, through the above steps, achieves event-level summary verification and difference correction, ensuring the final consistency and compliance verification of the rights ledger and the funds ledger. This effectively solves the problems of amplified reconciliation differences and broken evidence chains in the two-tier settlement scenario of cultural and artistic transactions, and improves the transparency of royalty distribution and the audit efficiency of governance processes.

[0123] The above formulas are all dimensionless calculations. The formulas are derived from software simulations based on a large amount of collected data to obtain the most recent real-world results. The preset parameters in the formulas are set by those skilled in the art according to the actual situation.

[0124] It should be noted that the system of the present invention can be deployed on the device itself to realize embedded applications, or it can run on a PC or other terminal with a user interface, thereby meeting a variety of hardware environments and usage requirements.

[0125] The foregoing has only described certain exemplary embodiments of the present invention by way of illustration. Undoubtedly, those skilled in the art can modify the described embodiments in various ways without departing from the spirit and scope of the present invention. Therefore, the foregoing drawings and descriptions are illustrative in nature and should not be construed as limiting the scope of protection of the claims of the present invention.

[0126] It should be noted that, in this document, the use of relational terms such as "first" and "second" is merely to distinguish one entity or operation from another, and does not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0127] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A two-tiered blockchain-based evidence storage system for cultural and artistic transactions integrating regulatory nodes, characterized in that: include: Event Filing Unit: Receives transaction confirmation identifiers, creates settlement event records and assigns unique event identifiers, binds work identifiers and counterparty identifiers, registers regulatory roster versions and regulatory strategy locations, and publishes event summaries to regulatory nodes for pre-emptive monitoring; Anchor Binding Unit: Acceptance and payment confirmation identifier, generates reconciliation anchor points and binds them one by one with event identifiers, records the reference positions of the rights ledger and funds ledger, writes them into the regulatory endorsement position and establishes a mapping between receipts and payments and transactions; The planning unit extracts the temporal consistency quantity and the intersection of endorsements, uses the order likelihood ratio test to generate an atomicity determination index, selects atomic submission, delayed review, or pre-rollback, and sets regulatory freeze and revocation entry points in the plan summary. Specifically, the temporal consistency quantity extracts the reference positions of the rights ledger and the funds ledger from settlement event records and reconciliation anchor points, compares the source relationship, summary structure correspondence, and generation order to form an order comparison table, and outputs it using a monotonic mapping function. It also parses the most recently confirmed set of endorsement summaries from the rights ledger, the most recently confirmed set of endorsement summaries from the funds ledger, and the endorsements from regulatory nodes. The process involves participating sets, calculating intersection coverage relationships, and applying a monotonic mapping function to output the endorsement intersection quantity. The temporal consistency quantity and the endorsement intersection quantity are input into the order likelihood ratio test process. The cumulative statistic is initialized to zero, and the log-likelihood difference is calculated for each piece of evidence and accumulated to obtain the cumulative statistic. This cumulative statistic is used as the atomicity determination index, compared with the upper and lower bound thresholds, and then outputs an atomic submission plan signal, a pre-rollback plan signal, or a delayed review plan signal, which is simultaneously stored in the settlement event record. Based on the plan signal, a plan summary is generated, which includes at least the determination interval, key observation summary, target reference location, and expected execution order. Submitting the execution unit: Write the transfer information in the rights ledger and the clearing information in the funds ledger according to the plan; monitor the confirmation and supervision instructions of the two ledgers; if the conditions are not met or a freeze instruction is received, correct the writing according to the pre-rollback and record the trajectory. Reconciliation and verification unit: Summarize transaction receipts, payments, transfers, rollbacks, and regulatory records at the event identifier level, generate verifiable reconciliation vouchers, complete consistency and compliance verification, update records and trigger limited-scope review when discrepancies exist.

2. The dual-layer settlement blockchain evidence storage system for cultural and artistic product transactions integrating regulatory nodes as described in claim 1, characterized in that: The event filing unit receives the transaction confirmation identifier from the transaction matching module, creates a settlement event record and generates a unique event identifier, writes the work identifier and the counterparty identifier into the same event entry, defines a fixed set of fields including source channel identifier, generation time tag, event status field, plan summary field, consistency check field, anchor reference field, regulatory roster field and regulatory strategy reference location, constructs a deduplicated fingerprint and performs idempotency verification before saving it to disk, and generates an event summary to send to the regulatory node cache area.

3. The dual-layer settlement blockchain evidence storage system for cultural and artistic transactions integrating regulatory nodes as described in claim 2, characterized in that: The anchor binding unit receives payment confirmation identifiers from the clearing channel, establishes reconciliation anchors in the settlement event record, binds the reconciliation anchors to the event identifiers one by one, records the reference positions of the rights ledger and the funds ledger, parses the most recent endorsement summary of the regulatory node to generate the regulatory endorsement reference position and writes it into the reconciliation anchor, establishes the mapping relationship between payment confirmation identifiers and transaction confirmation identifiers and the three-way association with the regulatory endorsement reference position, generates a source receipt snapshot and writes it back to the settlement event record.

4. The dual-layer settlement blockchain evidence storage system for cultural and artistic product transactions integrating regulatory nodes as described in claim 1, characterized in that: The execution unit performs transfer writing in the rights ledger and clearing writing in the funds ledger according to the plan summary. It registers the writing intent hash and starts the receipt listening. It verifies the rights ledger confirmation and funds ledger confirmation by matching the event identifier with the target reference position. When the plan summary requirements are met, it writes the transfer confirmation result in the settlement event record and fixes the rights ledger reference position, funds ledger reference position and confirmation time.

5. The dual-layer settlement blockchain evidence storage system for cultural and artistic transactions with integrated regulatory nodes as described in claim 4, characterized in that: When the submission execution unit fails to meet the plan summary requirements in the confirmation of the rights ledger or the funds ledger, or receives a regulatory freeze instruction through the regulatory channel, it generates a rollback instruction, writes and executes the corresponding write-back or cancellation write according to the pre-rollback plan location, synchronously corrects the event status field and the reference position of the rights ledger and the reference position of the funds ledger in the settlement event record, records the rollback trajectory, the summary of the triggering reason and the regulatory triggering information, and writes it back to the plan summary and event entry.

6. The dual-layer settlement blockchain evidence storage system for cultural and artistic transactions with integrated regulatory nodes as described in claim 5, characterized in that: The reconciliation verification unit summarizes transaction confirmation identifiers, payment confirmation identifiers, transfer confirmation results, rollback trajectories and regulatory freeze entry and regulatory revocation entry records at the event identifier granularity, and generates verifiable reconciliation vouchers including snapshots of the rights ledger reference location, snapshots of the funds ledger reference location, snapshots of the most recently confirmed endorsement summary set of the rights ledger, snapshots of the most recently confirmed endorsement summary set of the funds ledger, snapshots of the regulatory node endorsement participation set, snapshots of the atomic submission plan, and judgment trajectory index.

7. The dual-layer settlement blockchain evidence storage system for cultural and artistic transactions integrating regulatory nodes as described in claim 6, characterized in that: The reconciliation and verification unit performs consistency verification. First, it verifies the same-source relationship and entry consistency between the snapshot of the reference location in the rights ledger and the snapshot of the reference location in the funds ledger. Then, it verifies the intersection and coverage relationship between the snapshot of the most recently confirmed endorsement summary set in the rights ledger, the snapshot of the most recently confirmed endorsement summary set in the funds ledger, and the snapshot of the endorsement participation set in the regulatory node. Finally, it verifies the consistency relationship between the snapshot of the atomic submission plan and the transfer confirmation result, and between the rollback trajectory and the regulatory freeze entry record.

8. The dual-layer settlement blockchain evidence storage system for cultural and artistic transactions integrating regulatory nodes as described in claim 7, characterized in that: When the reconciliation and verification unit discovers inconsistencies in snapshots of the rights ledger reference locations, conflicts in snapshots of the most recently confirmed endorsement summary set of the rights ledger, inconsistencies between the execution of the atomic submission plan snapshot and the transfer confirmation result, or when the regulatory freeze entry trigger is not recorded, it generates a discrepancy list and marks the generation stage. The discrepancy list is written into the settlement event record and plan summary and triggers a limited-scope review. The review is only performed on the rights ledger reference location snapshots and related entries involved in the discrepancy list. After the review is completed, the consistency verification result and verifiable reconciliation voucher reference are output.

Images