A privacy-conscious collaborative accounting mapping method for carbon assets

By constructing a carbon asset privacy state carrier and combining it with current anchor point data to generate state lifecycle control values, the problem of carbon asset state mapping mismatch is solved, and efficient and accurate carbon asset state judgment is achieved under privacy protection.

CN122310587BActive Publication Date: 2026-11-10LINGSHU TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202610787407.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2026-06-03
Publication Date
2026-11-10
Estimated Expiration
2046-06-03

AI Technical Summary

Technical Problem

In the context of carbon asset privacy collaborative accounting, existing technologies rely on accounting snapshot data that has been encapsulated or verified to determine the status of carbon assets. This results in a mismatch between the mapping results and the actual status, and fails to effectively protect the privacy of the underlying data of carbon assets.

Method used

By constructing a carbon asset privacy status carrier and combining current registration anchor data and transaction settlement anchor data, a status lifecycle control value is generated for dynamic mapping control, including effective mapping, re-anchoring mapping, and invalid mapping, to ensure that the carbon asset status is consistent with the current transaction settlement status.

Benefits of technology

It improves the timeliness and reliability of carbon asset state mapping results, reduces the risk of misjudgment due to historical snapshots or delayed proof, and achieves a match between privacy and business applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122310587B_ABST
    Figure CN122310587B_ABST
Patent Text Reader

Abstract

This invention relates to the fields of carbon asset management, carbon emission trading, privacy-based collaborative accounting, and state mapping processing. Specifically, it relates to a carbon asset privacy-based collaborative accounting mapping method. This method constructs a carbon asset privacy state carrier through a state mapping request, generates a state lifecycle control value by combining current registration anchor data and current transaction settlement anchor data, and calls a preset state power mapping matrix to perform effective mapping control, re-anchoring mapping control, or ineffective mapping control. It outputs the carbon asset state after mapping and proof of the validity of the updated state. This invention collaboratively processes the carbon asset privacy state carrier, current registration anchor data, current transaction settlement anchor data, and use identifier to generate a state lifecycle control value and call the mapping matrix to achieve effective, re-anchoring, or ineffective control, thereby improving the scenario matching, timeliness, and reliability of state mapping.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the fields of carbon asset management, carbon emission trading, privacy-based collaborative accounting, and state mapping processing; more specifically, it relates to a carbon asset privacy-based collaborative accounting mapping method. Background Technology

[0002] As carbon emission trading, carbon quota compliance settlement, carbon credit offsetting, carbon asset-backed financing, and compliance gap verification gradually develop, carbon asset objects need to be calculated, verified, and mapped to corresponding rights and statuses in different business scenarios. For example, in a trading scenario, it is necessary to determine whether the same target carbon asset object is currently tradable; in a compliance scenario, it is necessary to determine whether it is currently settleable; in an offsetting scenario, it is necessary to determine whether it is currently offsettable; in a pledge scenario, it is necessary to determine whether there are any restrictions on its rights; and in a compliance assessment scenario, it is also necessary to determine whether it can support the formation of a compliance gap-free state.

[0003] In existing technologies, carbon asset status assessment typically relies on data such as registration records, transaction settlement records, accounting snapshots, or supporting documents. This approach can meet general needs for ownership verification, quantity calculation, and status confirmation, and can also support cross-entity collaborative carbon asset accounting to some extent. However, in privacy-sensitive collaborative accounting scenarios, participating parties often find it inconvenient to directly disclose complete registration details, transaction settlement details, and underlying accounting data. Status assessment then relies more heavily on encapsulated or certified carbon asset accounting snapshot data and proof of the validity of the status to be verified.

[0004] In the aforementioned scenarios, carbon asset accounting snapshot data typically corresponds to a specific snapshot point in time, and the validity proof of the pending verification status also has a certain lifespan. When the target carbon asset object experiences events such as registration event level updates, changes in registration status commitment values, cancellation, freezing, liquidation lockout, rights restrictions, account anomalies, pending settlement of transactions, pending settlement confirmation after settlement completion, settlement completion, or settlement objections after the snapshot is formed, mapping the status solely based on the original carbon asset accounting snapshot data or the original validity proof of the pending verification status may result in the mapped carbon asset status not fully matching the current registration status, the current transaction settlement phase, or the specific carbon asset use request.

[0005] Therefore, there is still room for further improvement in the relevant technologies, and there is an urgent need for a technical solution that can protect the privacy of the underlying data of carbon assets while coordinating the processing of the carbon asset privacy status carrier, the current registration anchor data, the current transaction settlement anchor data, and the carbon asset use request identifier. Summary of the Invention

[0006] To address the shortcomings of existing technologies, the present invention aims to provide a carbon asset privacy collaborative accounting mapping method.

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

[0008] A carbon asset privacy collaborative accounting mapping method includes:

[0009] Step 1: Receive a state mapping request for the target carbon asset object. The state mapping request carries or indicates a carbon asset use request identifier. Based on the state mapping request, construct a carbon asset privacy state carrier. The carbon asset privacy state carrier includes carbon asset accounting snapshot data and a proof of the validity of the state to be verified.

[0010] Step 2: Obtain the current registration anchor point data and the current transaction settlement anchor point data for the target carbon asset.

[0011] Step 3: Generate a state lifecycle control value based on the carbon asset privacy status carrier, current registration anchor data, current transaction settlement anchor data, and carbon asset use request identifier;

[0012] Step 4: Based on the state lifecycle control value, call the preset state power mapping matrix to dynamically map and control the carbon asset state corresponding to the carbon asset privacy state carrier and the validity proof of the state to be verified, and output the mapped carbon asset state and the updated validity proof of the state.

[0013] Among them, dynamic mapping control includes effective mapping control, re-anchoring mapping control and failure mapping control. Failure mapping control is used to prevent expired unverified status validity certificates or expired carbon asset accounting snapshots from being mapped to the current available carbon asset status. The current available carbon asset status includes at least one of the following: current tradable status, current offsetting status, current liquidation status, current pledgeable status, and no compliance gap status.

[0014] In one embodiment, the carbon asset privacy status carrier satisfies the following field configuration: the carbon asset accounting snapshot data includes a carbon asset use request identifier corresponding to the status mapping request, a snapshot registration anchor field, and a snapshot transaction settlement anchor field;

[0015] The proof of validity pending verification includes the proof registration event level, the proof transaction settlement event level, the proof purpose binding identifier, and the proof lifecycle status identifier. The proof lifecycle status identifier is used to characterize the proof of validity pending verification as being in one of the following states: initial state, valid state, state requiring re-anchoring, or invalid state.

[0016] In one embodiment, the snapshot registration anchor field and the snapshot transaction settlement anchor field are configured as follows: the snapshot registration anchor field includes the snapshot registration event level and the snapshot registration status commitment value; the snapshot transaction settlement anchor field includes the snapshot transaction settlement event level and the snapshot transaction settlement phase identifier.

[0017] In one embodiment, the current registration anchor data is configured as follows: the current registration anchor data includes the current registration event level, the current registration status commitment value, and the status finality identifier. The status finality identifier is used to indicate whether the target carbon asset object has at least one finality restriction status among cancellation, freezing, liquidation and locking, rights restriction, or account abnormality.

[0018] In one embodiment, the current transaction settlement anchor data is configured as follows: the current transaction settlement anchor data includes the current transaction settlement event level, the current transaction settlement phase identifier, and the phase confirmation identifier; the current transaction settlement phase identifier is used to indicate that the target carbon asset object is in one of the following states: undeclared, declared frozen, declared withdrawn and restored, transaction pending settlement, settlement completed pending settlement confirmation, settlement completed, or settlement objection.

[0019] In one embodiment, generating a state lifecycle control value includes: calculating the registration finality deviation based on the registration state offset relationship between carbon asset accounting snapshot data and current registration anchor data; calculating the transaction settlement phase difference based on the transaction settlement phase offset relationship between carbon asset accounting snapshot data and current transaction settlement anchor data; calculating the proof lifecycle failure value based on the proof binding offset relationship between the proof of validity to be verified and the current registration anchor data, the current transaction settlement anchor data, and the carbon asset use request identifier; and generating a state lifecycle control value based on the registration finality deviation, the transaction settlement phase difference, and the proof lifecycle failure value.

[0020] In one embodiment, calculating the registration finality deviation includes: performing differential processing on the snapshot registration event level and the current registration event level to obtain the registration level difference; performing commitment consistency verification on the snapshot registration status commitment value and the current registration status commitment value to obtain the registration status consistency result; and calculating the registration finality deviation based on the registration level difference, the registration status consistency result, and the status finality identifier.

[0021] In one embodiment, calculating the transaction settlement phase difference includes: determining the phase topology distance between the snapshot transaction settlement phase identifier and the current transaction settlement phase identifier based on a preset phase topology relationship; performing differential processing on the snapshot transaction settlement event level and the current transaction settlement event level to obtain the transaction settlement level difference; and calculating the transaction settlement phase difference based on the phase topology distance, the transaction settlement level difference, and the phase confirmation identifier; wherein, the preset phase topology relationship is used to define the flow order, mutual exclusion relationship, and abnormal jump relationship between different transaction settlement phases.

[0022] In one embodiment, the preset state power mapping matrix includes the mapping relationship between state lifecycle control value, carbon asset use request identifier, candidate carbon asset state, proof lifecycle state identifier, and proof update action.

[0023] In one embodiment, step four includes: when the state life cycle control value corresponds to effective mapping control, determining the mapped carbon asset state from the currently available carbon asset states based on the carbon asset use request identifier, and generating an updated state validity certificate that binds the current registration anchor data and the current transaction settlement anchor data.

[0024] When the state lifecycle control value corresponds to the re-anchoring mapping control, the mapped carbon asset state will be determined as one of the following: trading process locked state, delivery in transit state, time-limited and use-limited available state, or state requiring re-anchoring. The proof lifecycle state identifier of the proof of the validity of the state to be verified will be updated to the state requiring re-anchoring.

[0025] Compared with the prior art, the present invention has the following beneficial effects:

[0026] This invention receives state mapping requests and constructs a carbon asset privacy state carrier, establishing a link between carbon asset accounting snapshot data, proof of the validity of the state to be verified, and carbon asset use request identifier. This enables the target carbon asset object to have a unified privacy collaborative accounting basis in different scenarios such as trading, offsetting, liquidation, pledging, and verification of performance gaps, thereby improving the matching between state mapping requests and specific business uses.

[0027] By introducing current registration anchor data and current transaction settlement anchor data, and combining them with carbon asset privacy status carriers to generate status lifecycle control values, the mapping judgment can reflect the differences between carbon asset accounting snapshot data, the validity proof of the status to be verified, and the current registration status and current transaction settlement status, thereby reducing the risk of misjudgment of carbon asset status due to the lag of historical snapshots or historical proofs.

[0028] By using a preset state-weight mapping matrix, effective mapping, re-anchoring mapping, and invalidation mapping are implemented for carbon asset states and proofs of validity of states to be verified. When a state is valid, the mapped carbon asset state and the updated state validity proof that match the use request are output. When a state needs to be updated, re-anchoring processing is triggered. When a proof or snapshot expires, it is prevented from being mapped to a current tradable state, a current offsettable state, a current liquidation state, a current pledgeable state, or a state with no performance gap. This improves the timeliness, reliability, and risk isolation capability of carbon asset state mapping results. Attached Figure Description

[0029] Figure 1 A flowchart of a carbon asset privacy collaborative accounting mapping method;

[0030] Figure 2 This is a schematic diagram illustrating the field configuration of the carbon asset privacy status carrier in this invention;

[0031] Figure 3 This is a schematic diagram illustrating the generation of state lifecycle control values ​​in this invention. Detailed Implementation

[0032] Reference Figure 1 A carbon asset privacy collaborative accounting mapping method, comprising:

[0033] Step one involves receiving a state mapping request for the target carbon asset object. This request carries or indicates a carbon asset use request identifier. Based on the state mapping request, a carbon asset privacy state carrier is constructed. This carrier includes carbon asset accounting snapshot data and a certificate of validity to be verified, establishing the input basis for the target carbon asset object to enter the privacy-collaborative accounting mapping process. The state mapping request carries the mapping trigger information for the target carbon asset object, and the carbon asset use request identifier limits the corresponding rights and scenarios for this mapping. Constructing a carbon asset privacy state carrier based on the state mapping request integrates the carbon asset accounting snapshot data and the certificate of validity to be verified within the same carrier structure, forming a unified data object for state verification, use binding, and certificate updates. This avoids judging the carbon asset status based solely on a single accounting snapshot or a single certificate.

[0034] Reference Figure 2In one specific implementation, a state mapping request for a target carbon asset object is received. The state mapping request carries or indicates a carbon asset use request identifier, which corresponds to the power scenario that the target carbon asset object intends to enter. Taking a batch of carbon emission allowances held by a key emission unit as an example, the state mapping request points to the settlement and offset verification scenario. The historical accounting results, registration anchor records, and transaction settlement process records corresponding to the target carbon asset object are included in the same processing scope. A carbon asset privacy state carrier is constructed based on the state mapping request. The carbon asset privacy state carrier includes carbon asset accounting snapshot data and a certificate of validity of the state to be verified. The carbon asset accounting snapshot data records the carbon asset use request identifier, snapshot registration anchor field, and snapshot transaction settlement anchor field corresponding to the state mapping request. The snapshot registration anchor field includes the snapshot registration event level and the snapshot registration status commitment value. The snapshot transaction settlement anchor field includes the snapshot transaction settlement event level and the snapshot transaction settlement phase identifier. Thus, the registration status, transaction settlement phase, and use request relationship of the target carbon asset object at the time of the accounting snapshot are solidified into privacy state data that can participate in verification.

[0035] The snapshot generation time is denoted as The snapshot registration event level, snapshot registration status commitment value, snapshot transaction settlement event level, and snapshot transaction settlement phase identifier respectively satisfy the following:

[0036]

[0037]

[0038]

[0039]

[0040] Carbon asset accounting snapshot data satisfy:

[0041]

[0042]

[0043] in, This is the registration status commitment value corresponding to the snapshot generation time. This is the transaction settlement phase identifier corresponding to the snapshot generation time;

[0044] The carbon asset privacy status carrier is configured with a certificate of validity of the status to be verified. The certificate of validity of the status to be verified includes the certificate of registration event level, the certificate of transaction settlement event level, the certificate of use binding identifier, and the certificate of life cycle status identifier. The certificate of registration event level and the snapshot registration event level form the certificate benchmark for the registration dimension. The certificate of transaction settlement event level and the snapshot transaction settlement event level form the certificate benchmark for the transaction settlement dimension. The certificate of use binding identifier maintains a corresponding relationship with the carbon asset use request identifier. The certificate of life cycle status identifier records that the certificate of validity of the status to be verified is in one of the following states: initial state, valid state, state requiring re-anchoring, or invalid state.

[0045] Proof of the validity of the state to be verified This includes the target carbon asset's commitment value, proof of use binding identifier, proof of registration event level, proof of registration status commitment value, proof of transaction settlement event level, proof of transaction settlement phase identifier, proof of phase confirmation identifier, proof of lifecycle status identifier, proof of generation time, proof of validity duration, and proof of signature value, satisfying the following:

[0046]

[0047]

[0048] Prove that the hash value and the signature verification result satisfy:

[0049]

[0050]

[0051] Corrected proof of lifecycle status identifier satisfy:

[0052]

[0053] in, To prove the revocation of the hash set, To prove the issuing node's public key. The proof's lifecycle state identifier is... Subject to;

[0054] For example, when the target carbon asset is in a completed settlement state at the time of snapshot generation, and the snapshot registration status commitment value corresponds to a registration status that is not frozen, not cancelled, and not locked, the proof lifecycle status identifier in the proof of validity to be verified can be recorded as a valid state. When the transaction settlement phase has changed or the proof use binding identifier is inconsistent with the carbon asset use request identifier, the proof lifecycle status identifier can be recorded as a state that needs to be re-anchored or an invalid state. In this way, the group construction of carbon asset accounting snapshot data and proof of validity to be verified can be completed without directly exposing the complete underlying registration data and transaction settlement data.

[0055] The commitment algorithm is denoted as Com, the collision-resistant hash function as H, the signature verification function as VerifySig, and the commitment equivalence verification function as VerifyEq. The registration status commitment value is generated in the following fixed field order: target carbon asset object identifier, holder commitment value, quantity balance commitment value, rights and obligations identifier, status finality identifier, registration event level, and random salt value, satisfying the following:

[0056]

[0057] in, This is the committed value for the registration status. Identify the target carbon asset object. The value committed by the holding entity. The quantity balance commitment value, For the purpose of identifying the burden of rights, This is a state finality identifier. For the registration of event water levels, The salt value is random. The registration status consistency result is... Determined according to the following formula:

[0058]

[0059] in, This is a snapshot of the registration status commitment value. This is the committed value for the current registration status. As proof of the commitment to equivalent value, Sign the source of the current registration anchor data;

[0060] Safety parameters are denoted as The random salt value is generated by a cryptographically secure random number generator and satisfies:

[0061]

[0062] The commitments of the holding entity, the quantity balance, and the target carbon asset object respectively satisfy the following:

[0063]

[0064]

[0065]

[0066] HID stands for Holder Identifier. To record the balance amount, Identify the target carbon asset object.

[0067] Step two involves acquiring the current registration anchor data and current transaction settlement anchor data for the target carbon asset. This provides the target carbon asset's current anchoring information in both the registration and transaction settlement dimensions. The current registration anchor data reflects the target carbon asset's current status in areas such as registration, freezing, cancellation, liquidation lock-up, rights restrictions, or account anomalies. The current transaction settlement anchor data reflects the target carbon asset's current phase in the transaction settlement process, including declaration, freezing, transaction, clearing, settlement, and objection. Through these two dimensions of anchor data, the carbon asset's privacy status carrier no longer relies solely on historical snapshots but is constrained by both the current registration status and the current transaction process status.

[0068] In one specific implementation, current registration anchor data for the target carbon asset object is obtained. The current registration anchor data includes the current registration event level, the current registration status commitment value, and the status finality identifier. The current registration event level is generated according to the latest registration event sequence of the target carbon asset object in the register. The current registration status commitment value is calculated based on the target carbon asset object's current holder, quantity balance, rights and obligations, freeze records, cancellation records, liquidation and lock records, and account status. The status finality identifier records whether the target carbon asset object has at least one final restriction status among cancellation, freeze, liquidation and lock, rights restriction, or account abnormality.

[0069] The set of registration events is denoted as This collection includes query time. Previous identification of target carbon asset objects Related registration events. The registration event number is denoted as... Registration event water level satisfy:

[0070]

[0071]

[0072] The query time is recorded as At that time, the current registered event level was The current registration status commitment values ​​meet the following requirements:

[0073]

[0074] Current registration anchor point main data and source signature verification results satisfy:

[0075]

[0076]

[0077] in, For registering the node's public key, For the registration node to sign the main data of the current registration anchor point;

[0078] For example, if a key emission unit holds 100 tons of carbon emission quotas that have been cleared and locked in the register, then the current registration event level is taken as the latest event number corresponding to the clearing and locking registration, the current registration status commitment value is bound to the registration status after clearing and locking, and the status finality identifier is recorded as a state with finality restriction.

[0079] Obtain current transaction settlement anchor point data for the target carbon asset. The current transaction settlement anchor point data includes the current transaction settlement event level, the current transaction settlement phase identifier, and the phase confirmation identifier. The current transaction settlement event level is generated according to the latest event sequence of the target carbon asset in the transaction settlement chain. The current transaction settlement phase identifier records one of the following states for the target carbon asset: undeclared, declared frozen, declared withdrawn and restored, traded pending settlement, settlement completed pending settlement confirmation, settlement completed, or settlement dispute. The phase confirmation identifier records whether the current transaction settlement phase identifier has been confirmed.

[0080] The set of transaction settlement events is denoted as This collection includes query time. Previous identification of target carbon asset objects Related events include declarations, freezes, cancellations, trades, clearing, settlements, and objections. The transaction settlement event number is denoted as follows: Transaction settlement event level satisfy:

[0081]

[0082]

[0083] The current transaction settlement phase identifier satisfies:

[0084]

[0085] Current transaction settlement anchor data and phase confirmation mark satisfy:

[0086]

[0087]

[0088] in, For the public key of the transaction settlement node, This is the signature of the transaction settlement node on the main data of the current transaction settlement anchor point. This is a pre-defined set of confirmed phases;

[0089] For example, if a target carbon asset has been traded and entered the settlement completion pending confirmation state, but the settlement confirmation has not yet been completed, then the current transaction settlement event level is taken as the latest event sequence number corresponding to the settlement completion event, the current transaction settlement phase identifier is recorded as the settlement completion pending confirmation state, and the phase confirmation identifier is recorded as the unconfirmed state, so that the current registration anchor data and the current transaction settlement anchor data jointly reflect the current real constraints of the target carbon asset in the registration dimension and the transaction settlement dimension.

[0090] Step 3: Based on the carbon asset privacy status carrier, current registration anchor data, current transaction settlement anchor data, and carbon asset use request identifier, a status lifecycle control value is generated. This value is then jointly calculated to form the status lifecycle control value. The status lifecycle control value reflects the status offset between the carbon asset accounting snapshot data and the current registration anchor data, the phase offset between the carbon asset accounting snapshot data and the current transaction settlement anchor data, and the binding offset between the validity proof of the status to be verified and the current anchor data and carbon asset use request identifier. This value serves as the basis for dynamic mapping control, indicating whether the target carbon asset remains valid under the current use request, whether re-anchoring is required, or whether it should enter a failure blocking phase.

[0091] Reference Figure 3In one specific implementation, the registration finality deviation is calculated based on the registration status offset relationship between the carbon asset accounting snapshot data in the carbon asset privacy status carrier and the current registration anchor data. Specifically, the registration event level of the snapshot is differentially processed with the current registration event level to obtain the registration level difference, and the commitment value of the snapshot registration status is verified with the commitment value of the current registration status to obtain the registration status consistency result. When the registration level difference is zero and the registration status consistency result is consistent, the registration finality deviation is recorded as a low deviation level. When the registration level difference is greater than zero but the status finality identifier does not record cancellation, freezing, liquidation and locking, rights restriction, or account abnormality, the registration finality deviation is recorded as a medium deviation level. When the status finality identifier records any of the above-mentioned finality restriction statuses, the registration finality deviation is recorded as a high deviation level.

[0092] Registered water level difference Calculate according to the following formula:

[0093]

[0094] in, This represents the current registered event level. The snapshot registration event level. Status finality identifier. Determined according to the following formula:

[0095]

[0096] when , , , , If any one of them is true, True. Registration final deviation. Determined according to the following formula:

[0097]

[0098] Current registration events The standardized set of state labels is denoted as Any status label State values satisfy:

[0099]

[0100] Rights and obligations identifier satisfy:

[0101]

[0102] State finality identifier satisfy:

[0103]

[0104] in, It is generated by normalizing the status field, rights restriction field, account status field, and judicial assistance field in the registration event;

[0105] For example, if the snapshot registration event level of the target carbon asset is 120, the current registration event level is 125, and the current registration status commitment value shows that it is frozen, then the final deviation of the registration is directly classified as a high deviation level.

[0106] Based on the phase offset relationship between carbon asset accounting snapshot data and current transaction settlement anchor data, the transaction settlement phase difference is calculated. Specifically, the phase topology distance between the snapshot transaction settlement phase identifier and the current transaction settlement phase identifier is determined according to the preset phase topology relationship. The transaction settlement event level of the snapshot and the current transaction settlement event level are then differentially processed to obtain the transaction settlement level difference. The preset phase topology relationship records the flow order, mutual exclusion relationship, and abnormal jump relationship between the unreported state, the reported frozen state, the reported cancelled and restored state, the trade pending settlement state, the settlement completed and pending settlement confirmation state, the settlement completed state, and the settlement objection state. When the snapshot transaction settlement phase identifier is in the trade pending settlement state, the current transaction settlement phase identifier is in the settlement completed and pending settlement confirmation state, and the phase confirmation identifier is in the confirmed state, the transaction settlement phase difference is recorded as the normal progress difference. When the current transaction settlement phase identifier jumps to the settlement objection state or the phase confirmation identifier is in the unconfirmed state, the transaction settlement phase difference is recorded as the abnormal phase difference.

[0107] The preset phase topology is denoted as . This includes the following statuses: no declaration, declaration frozen, declaration cancelled and restored, transaction pending settlement, settlement completed and pending delivery confirmation, delivery completed, and settlement objection. This includes normal flow edges and abnormal jump edges. Normal flow edges are:

[0108]

[0109]

[0110]

[0111]

[0112]

[0113]

[0114] The abnormal jump edge is:

[0115]

[0116] The preset phase topology is denoted as From phase To phase The set of directed paths satisfy:

[0117]

[0118] Phase topological distance satisfy:

[0119]

[0120] in, This represents the number of phase nodes in the path.

[0121] Phase topological distance Determined according to the following formula:

[0122]

[0123] in, This serves as a snapshot transaction settlement phase identifier. This indicates the current transaction settlement phase. Transaction settlement level difference. Calculate according to the following formula:

[0124]

[0125] In one specific implementation, the transaction settlement phase difference Determined according to the following formula:

[0126]

[0127] When the transaction settlement phase difference is an abnormal phase difference, there is a blocking offset between the current transaction settlement anchor data and the snapshot transaction settlement anchor field; when the transaction settlement phase difference is a normal advance difference, the phase change between the current transaction settlement anchor data and the snapshot transaction settlement anchor field does not trigger a blocking offset.

[0128] Based on the proof binding offset relationship between the proof of validity to be verified and the current registration anchor data, the current transaction settlement anchor data, and the carbon asset use request identifier, the proof lifecycle failure value is calculated, and a state lifecycle adjustment value is generated by combining the registration finality deviation and the transaction settlement phase difference. Specifically, the degree of correspondence between the proof registration event level and the current registration event level, the degree of correspondence between the proof transaction settlement event level and the current transaction settlement event level, the degree of consistency between the proof use binding identifier and the carbon asset use request identifier, and the proof lifecycle status identifier are all included in the judgment. When the proof... When the lifecycle status identifier is valid, the proof of use binding identifier is consistent with the carbon asset use request identifier, the registration finality deviation is low, and the transaction settlement phase difference is normal progress difference, the lifecycle status control value is recorded as the valid mapping control value; when there is an event level update but no final restriction status appears, the lifecycle status control value is recorded as the re-anchor mapping control value; when the proof of lifecycle status identifier is invalid, or the finality status identifier is cancelled, frozen, liquidated and locked, restricted in rights, or the account is abnormal, the lifecycle status control value is recorded as the invalid mapping control value.

[0129] Proof of Purpose Binding Identifier Proof of validity from the state to be verified Extracted from, the carbon asset use request identifier is recorded as Proof of purpose: binding hash values. and purpose request hash value They respectively satisfy:

[0130]

[0131]

[0132] Proof of consistent use value satisfy:

[0133]

[0134] U includes one of the following scenarios: transaction scenario, offsetting scenario, settlement scenario, pledge scenario, or performance gap verification scenario;

[0135] Proof of consistent use value Determined according to the following formula:

[0136]

[0137] Proof of registration water level difference and proof of the settlement level difference Calculate according to the following formula:

[0138]

[0139]

[0140] in, To prove the water level of the registration event, To demonstrate the level of transaction settlement events.

[0141] Proof of failure conditions and conditions for proof of validity They respectively satisfy:

[0142]

[0143]

[0144] Prove lifecycle failure value Determined according to the following formula:

[0145]

[0146] State lifecycle regulation value For the deviation from the final registration Transaction settlement phase difference and proof of lifecycle failure value The combined values ​​satisfy:

[0147]

[0148] State lifecycle regulation value The type of regulation shall be determined according to the following priorities:

[0149]

[0150] In the above rules, the priority of the corresponding value of the failure mapping control is higher than that of the corresponding value of the effective mapping control and the corresponding value of the re-anchoring mapping control.

[0151] Step four involves invoking a preset state power mapping matrix based on the state lifecycle control value to dynamically map and control the carbon asset state corresponding to the carbon asset privacy state carrier and the validity proof of the state to be verified. The mapped carbon asset state and the updated validity proof of the state are then output. The preset state power mapping matrix incorporates the carbon asset state corresponding to the carbon asset privacy state carrier and the validity proof of the state to be verified into the dynamic mapping control. The preset state power mapping matrix defines the correspondence between the state lifecycle control value, the carbon asset use request identifier, the candidate carbon asset state, the proof lifecycle state identifier, and the proof update action, ensuring that the mapped carbon asset state does not deviate from the current registration anchor data and the current transaction settlement anchor data. The output of the mapped carbon asset state and the updated validity proof of the state reflects the power and proof results of the target carbon asset object under this state mapping request.

[0152] Dynamic mapping control includes effective mapping control, re-anchoring mapping control, and ineffective mapping control. Effective mapping control addresses situations where the carbon asset privacy status carrier, current registration anchor data, current transaction settlement anchor data, and carbon asset use request identifier are consistent, ensuring the mapped carbon asset status falls within the currently usable carbon asset category. Re-anchoring mapping control addresses situations where the registration status, transaction settlement phase, or proof binding relationship deviates but has not yet reached the level of ineffective blocking; after mapping, the carbon asset status enters a transaction process locked state, a settlement in transit state, a time-limited and use-limited usable state, or a state requiring re-anchoring. Ineffective mapping control addresses situations where expired pending verification status validity certificates or expired carbon asset accounting snapshots should not be recognized as currently usable carbon asset statuses, preventing the erroneous generation of current tradable, current offsettable, current liquidable, current pledgeable, or no compliance gap states.

[0153] In one specific implementation, a preset state power mapping matrix is ​​invoked based on the state lifecycle control value. The preset state power mapping matrix records the mapping relationship between the state lifecycle control value, carbon asset use request identifier, candidate carbon asset status, proof lifecycle status identifier, and proof update action. The carbon asset status corresponding to the carbon asset privacy status carrier and the proof of validity of the status to be verified are included in the dynamic mapping control. The dynamic mapping control includes effective mapping control, re-anchoring mapping control, and invalid mapping control. The matrix row items are divided into candidate carbon asset statuses such as current tradable status, current offsetting status, current liquidation status, current pledgeable status, and no performance gap status according to the carbon asset use request identifier. The initial status, effective status, re-anchoring status, and invalid status are distinguished according to the proof lifecycle status identifier. The invalid mapping control is responsible for blocking expired proof of validity of the status to be verified or expired carbon asset accounting snapshots to prevent such data from entering the current available carbon asset status.

[0154] State validity basic conditions satisfy:

[0155]

[0156] No. The available quantity of each carbon asset object satisfy:

[0157]

[0158] Current tradable conditions Current offsetting conditions Current conditions for collection and current pledgeable conditions They respectively satisfy:

[0159]

[0160]

[0161]

[0162]

[0163] Asset Collection Available amount of clearance commitment value Commitment value of performance requirements Verification certificate by comparison of quantity satisfy:

[0164]

[0165]

[0166]

[0167] Conditions for no gap to be established satisfy:

[0168]

[0169] Expired carbon asset accounting snapshots are marked as expired. It is confirmed that expired certificates of validity pending verification will be issued according to the certificate expiration indicator. Confirmed. Snapshot expired flag. satisfy:

[0170]

[0171] Expired certificate satisfy:

[0172]

[0173] when or At that time, the preset state power mapping matrix does not output the current tradable state, current offsetting state, current liquidation state, current staking state, or no performance gap state;

[0174] The version number of the preset state-weight mapping matrix is ​​denoted as ,Version The mapping matrix below satisfy:

[0175]

[0176] For state lifecycle control values And carbon asset use request identifier U, hit item set satisfy:

[0177]

[0178] Prove the update action code They respectively satisfy:

[0179]

[0180]

[0181]

[0182] Mapping output results satisfy:

[0183]

[0184]

[0185] when At that time, the mapping output result is fixed as It does not output the current tradable status, current offsetting status, current liquidation status, current pledgeable status, or status with no performance gap.

[0186] Based on the mapping relationship, the mapped carbon asset status and the proof update action are determined. When the status lifecycle control value corresponds to an effective mapping control, the mapped carbon asset status is determined from the current available carbon asset status according to the carbon asset use request identifier, and an updated status validity certificate is generated that binds the current registration anchor data and the current transaction settlement anchor data. Taking the above-mentioned cleanup scenario as an example, if the current registration anchor data does not record cancellation, freezing, cleanup lock, rights restriction, or account abnormality, and the current transaction settlement anchor data records the settlement completion status and the phase confirmation identifier is confirmed, then the mapped carbon asset status is determined to be the current cleanupable status. The proof update action is recorded as rebinding the current registration event level, the current registration status commitment value, the current transaction settlement event level, the current transaction settlement phase identifier, and the carbon asset use request identifier to generate an updated status validity certificate. This updated status validity certificate replaces the unverified status validity certificate in the output of this status mapping result.

[0187] Update state validity proof This includes the target carbon asset's commitment value, carbon asset use request identifier, current registration event level, current registration status commitment value, current transaction settlement event level, current transaction settlement phase identifier, phase confirmation identifier, certificate lifecycle status identifier, certificate generation time, certificate validity window, and certificate signature value, satisfying the following:

[0188]

[0189] Prove signature value Generate according to the following formula:

[0190]

[0191] in, Where U represents the committed value of the target carbon asset and U is the carbon asset use request identifier. For phase confirmation, For the updated proof lifecycle status identifier, To prove the generation time, To prove the validity of the window, To prove the signature key.

[0192] No. The number of registered balances for each carbon asset object is denoted as The amount frozen in the transaction is recorded as The quantity seized and locked is recorded as The existing pledged quantity is recorded as The number of items frozen is recorded as follows: . No. The available quantity of each carbon asset object satisfy:

[0193]

[0194] Asset Collection Available amount of clearance commitment value Commitment value of performance requirements Committed value of pledged request quantity They respectively satisfy:

[0195]

[0196]

[0197]

[0198] The quantity comparison verification proves that:

[0199]

[0200]

[0201] in, To meet the contract fulfillment requirements, The amount of the pledge request. Generate a greater than or equal to proof;

[0202] When a carbon asset use request corresponds to a compliance gap verification scenario, the target carbon asset object can be a single carbon asset object or an asset set consisting of multiple carbon asset objects. Once each carbon asset object in the asset set is determined to be in a currently salvageable state through a preset state-weight mapping matrix, a commitment value for the available salvageable quantity is generated. :

[0203]

[0204] The commitment value for the performance requirement is denoted as :

[0205]

[0206] Verification of the status of no performance gap based on quantity comparison. Sure:

[0207] Conditions for no gap to be established satisfy:

[0208]

[0209]

[0210] The state of having no performance gap is determined by the following formula:

[0211]

[0212] in, For the first The available amount of each carbon asset object to be settled, where I is the set of carbon asset objects participating in the compliance gap verification. To meet the contract fulfillment requirements, and This is a random salt value.

[0213] 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 carbon asset privacy collaborative accounting mapping method, characterized in that, include: Step 1: Receive a state mapping request for the target carbon asset object. The state mapping request carries or indicates a carbon asset use request identifier. Based on the state mapping request, construct a carbon asset privacy state carrier. The carbon asset privacy state carrier includes carbon asset accounting snapshot data and a proof of the validity of the state to be verified. Step 2: Obtain the current registration anchor point data and the current transaction settlement anchor point data for the target carbon asset. Step 3: Generate a state lifecycle control value based on the carbon asset privacy status carrier, current registration anchor data, current transaction settlement anchor data, and carbon asset use request identifier; The generation of state lifecycle adjustment values ​​includes: calculating the registration finality deviation based on the registration status offset relationship between carbon asset accounting snapshot data and current registration anchor data; calculating the transaction settlement phase difference based on the transaction settlement phase offset relationship between carbon asset accounting snapshot data and current transaction settlement anchor data; calculating the proof lifecycle failure value based on the proof binding offset relationship between the proof of the validity of the unverified state and the current registration anchor data, the current transaction settlement anchor data, and the carbon asset use request identifier; and generating state lifecycle adjustment values ​​based on the registration finality deviation, the transaction settlement phase difference, and the proof lifecycle failure value. Step 4: Based on the state lifecycle control value, call the preset state power mapping matrix to dynamically map and control the carbon asset state corresponding to the carbon asset privacy state carrier and the validity proof of the state to be verified, and output the mapped carbon asset state and the updated validity proof of the state. Among them, dynamic mapping control includes effective mapping control, re-anchoring mapping control and failure mapping control. Failure mapping control is used to prevent expired unverified status validity certificates or expired carbon asset accounting snapshots from being mapped to the current available carbon asset status. The current available carbon asset status includes at least one of the following: current tradable status, current offsetting status, current liquidation status, current pledgeable status, and no compliance gap status.

2. The carbon asset privacy collaborative accounting mapping method according to claim 1, characterized in that, The carbon asset privacy status carrier meets the following field configuration: the carbon asset accounting snapshot data includes the carbon asset use request identifier corresponding to the status mapping request, the snapshot registration anchor field, and the snapshot transaction settlement anchor field; The proof of validity pending verification includes the proof registration event level, the proof transaction settlement event level, the proof purpose binding identifier, and the proof lifecycle status identifier. The proof lifecycle status identifier is used to characterize the proof of validity pending verification as being in one of the following states: initial state, valid state, state requiring re-anchoring, or invalid state.

3. The carbon asset privacy collaborative accounting mapping method according to claim 2, characterized in that, The snapshot registration anchor field and the snapshot transaction settlement anchor field meet the following configuration: the snapshot registration anchor field includes the snapshot registration event level and the snapshot registration status commitment value; the snapshot transaction settlement anchor field includes the snapshot transaction settlement event level and the snapshot transaction settlement phase identifier.

4. The carbon asset privacy collaborative accounting mapping method according to claim 3, characterized in that, The current registration anchor data meets the following configuration: The current registration anchor data includes the current registration event level, the current registration status commitment value, and the status finality identifier. The status finality identifier is used to indicate whether the target carbon asset object has at least one finality restriction status among cancellation, freezing, liquidation and locking, rights restriction, or account abnormality.

5. The carbon asset privacy collaborative accounting mapping method according to claim 1, characterized in that, The current transaction settlement anchor data meets the following configuration: The current transaction settlement anchor data includes the current transaction settlement event level, the current transaction settlement phase identifier, and the phase confirmation identifier; the current transaction settlement phase identifier is used to indicate that the target carbon asset object is in one of the following states: unreported, reported frozen, reported withdrawn and restored, traded pending settlement, settlement completed pending settlement confirmation, settlement completed, or settlement objection.

6. The carbon asset privacy collaborative accounting mapping method according to claim 5, characterized in that, The calculation of the registration final deviation includes: performing differential processing on the snapshot registration event water level and the current registration event water level to obtain the registration water level difference; performing commitment consistency verification on the snapshot registration status commitment value and the current registration status commitment value to obtain the registration status consistency result; and calculating the registration final deviation based on the registration water level difference, the registration status consistency result, and the status finality identifier.

7. The carbon asset privacy collaborative accounting mapping method according to claim 6, characterized in that, Calculating the transaction settlement phase difference includes: determining the phase topology distance between the snapshot transaction settlement phase identifier and the current transaction settlement phase identifier based on a preset phase topology relationship; performing differential processing on the snapshot transaction settlement event level and the current transaction settlement event level to obtain the transaction settlement level difference; and calculating the transaction settlement phase difference based on the phase topology distance, the transaction settlement level difference, and the phase confirmation identifier. The preset phase topology relationship is used to define the flow order, mutual exclusion relationship, and abnormal jump relationship between different transaction settlement phases.

8. The carbon asset privacy collaborative accounting mapping method according to claim 1, characterized in that, The preset state-capability mapping matrix includes the mapping relationship between state lifecycle control values, carbon asset use request identifiers, candidate carbon asset states, proof lifecycle state identifiers, and proof update actions.

9. A carbon asset privacy collaborative accounting mapping method according to any one of claims 1-8, characterized in that, Step four includes: when the state lifecycle control value corresponds to an effective mapping control, determining the mapped carbon asset state from the currently available carbon asset states based on the carbon asset use request identifier, and generating an updated state validity certificate that binds the current registration anchor data and the current transaction settlement anchor data; When the state lifecycle control value corresponds to the re-anchoring mapping control, the mapped carbon asset state will be determined as one of the following: trading process locked state, delivery in transit state, time-limited and use-limited available state, or state requiring re-anchoring. The proof lifecycle state identifier of the proof of the validity of the state to be verified will be updated to the state requiring re-anchoring.

Citation Information

Patent Citations

  • Running integral incentive method based on zero-knowledge proof and cross-chain carbon credit mapping

    CN120707162A

  • Property registration core data security protection method based on block chain technology

    CN120995507A