A method and system for on-chain coin-based digital RMB redemption
By generating locked transaction records in on-chain coin redemption requests and performing correlation verification, the problem of inconsistency between the on-chain locking state and the redemption result is solved. This achieves state closure under the same flow of on-chain locking and ledger updates, reduces the risk of duplicate redemption transfers and abnormal timeouts, and improves the traceability and security of the redemption process.
Patent Information
- Application Number
- CN202611356008.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-03
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2046-09-03
AI Technical Summary
In the current on-chain asset redemption process, there is a lack of a unified status connection between the on-chain locking status and the digital RMB redemption result, which leads to inconsistent redemption status and the risk of duplicate redemption. Furthermore, there is a lack of verifiable basis for unlocking or destroying after abnormal timeouts.
By receiving on-chain coin redemption requests, parsing the coin identifier and redemption quantity, generating a locked transaction record, querying the balance status and freeze status in the distributed ledger, generating a locked transaction record, and sending the redemption confirmation result, generating an on-chain destruction or unlock record, performing correlation verification and status index management, and ensuring the consistency between on-chain locking and ledger updates.
This achieves a closed-loop state between the on-chain locking state and the digital RMB redemption result under the same transaction flow, reducing inconsistencies in ledger state caused by duplicate redemption transfers and abnormal timeouts, and improving the traceability and security of the redemption process.
Smart Images

Figure CN122865568B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of distributed ledger technology, and in particular to an on-chain coin digital RMB redemption method and system. Background Technology
[0002] The field of distributed ledger technology involves networked ledger processing technology that records asset status, transaction status, and status change records through multi-node consensus. Among them, traditional on-chain asset redemption processing refers to establishing an asset transfer or value exchange process between on-chain accounts, on-chain transaction records, redemption interfaces, and ledger status, and completing the ledger-side status update through node records and interface return results.
[0003] The existing on-chain asset redemption process lacks a unified state connection between on-chain lock records and legal digital currency redemption results. After a redemption request enters an external redemption channel, the ledger side has difficulty distinguishing between redemption completion and redemption failure statuses while the lock is in progress. Users may repeatedly initiate redemption or transfer operations while the status is not closed. The channel return results and on-chain transaction records cannot be traced in the same order. After abnormal timeouts, there is a lack of verifiable unlocking or destruction evidence, leading to inconsistent redemption statuses and the risk of duplicate redemptions. Summary of the Invention
[0004] To address the lack of a closed loop between the on-chain locking state, the digital RMB redemption result, and the ledger update record during the aforementioned on-chain coin redemption process, this invention provides an on-chain coin digital RMB redemption method, comprising the following steps: Receive on-chain coin redemption requests and parse them to obtain the on-chain coin identifier, redemption amount, user wallet address, and digital RMB receiving identifier; Based on the on-chain coin identifier and redemption amount, query the on-chain coin status in the distributed ledger to generate a redeemable status record that includes balance status, frozen status, and redemption occupation status; When the redeemable status record meets the redemption conditions, the on-chain coin amount corresponding to the user's wallet address is locked according to the redemption amount, and a lock transaction record is generated. Send the digital RMB receiving identifier and redemption amount to the digital RMB redemption channel, and receive the redemption confirmation result; Based on the payment confirmation result, generate on-chain destruction records or on-chain unlock records, and write the locked transaction records, payment confirmation results, on-chain destruction records or on-chain unlock records into the distributed ledger.
[0005] Furthermore, when generating a redeemable status record, the ledger account balance, account freeze status identifier, unconfirmed transaction set, and locked amount corresponding to the on-chain coin identifier are read. The available amount is obtained by deducting the locked amount from the ledger account balance. The freeze status is determined independently based on the account freeze status identifier, and the redemption occupation status is determined based on whether there are unconfirmed redemption transactions occupying the same on-chain coin amount in the unconfirmed transaction set. When the available amount is greater than or equal to the redemption amount, the balance status is marked as satisfied; when the available amount is less than the redemption amount, the balance status is marked as unsatisfied. When the account freeze status identifier indicates that it is not frozen, the freeze status is marked as not triggered; when the account freeze status identifier indicates that it is frozen, the freeze status is marked as triggered. When there are no unconfirmed redemption transactions occupying the same on-chain coin amount in the unconfirmed transaction set, the redemption occupation status is marked as not triggered; when there are unconfirmed redemption transactions occupying the same on-chain coin amount, the redemption occupation status is marked as triggered.
[0006] As a progressive solution, the locked transaction record includes the locked transaction identifier, on-chain coin identifier, redemption amount, user wallet address, locked timestamp, and locked validity period. During the locked validity period, the distributed ledger marks the on-chain coin amount corresponding to the redemption amount as a redemption locked state and rejects duplicate transfer transactions and duplicate redemption transactions initiated with the on-chain coin identifier. When the locked validity period expires and no redemption confirmation result is received, an on-chain unlock record is generated.
[0007] As an optional solution, the redemption confirmation result includes the redemption processing status and the redemption channel transaction identifier. The redemption processing status is marked as either a successful redemption or a failed redemption in the same redemption confirmation result. When the redemption processing status in the redemption confirmation result is a successful redemption, an on-chain destruction record is generated. The on-chain destruction record is used to deduct the on-chain coin amount corresponding to the redemption amount from the user's wallet address. When the redemption processing status in the redemption confirmation result is a failed redemption, an on-chain unlock record is generated. The on-chain unlock record is used to unlock the redemption lock status of the on-chain coin amount corresponding to the redemption amount.
[0008] Furthermore, before writing to the distributed ledger, the locked transaction records, redemption confirmation results, on-chain destruction records, or on-chain unlocking records are correlated and verified. The correlation verification includes verifying whether the locked transaction identifiers are consistent, whether the redemption amounts are consistent, whether the user wallet addresses are consistent, and whether the redemption channel transaction identifier is empty. When the correlation verification passes, the verified record is written to the distributed ledger. When the correlation verification fails, the writing is rejected and an abnormal record is generated.
[0009] Furthermore, the digital RMB receiving identifier is converted into a redemption message before being sent to the digital RMB redemption channel. The redemption message includes a receiving identifier field, a redemption amount field, a request time field, and a request transaction field. After receiving the redemption confirmation result, the redemption message and the redemption confirmation result are matched according to the request transaction field. If the match is successful, an on-chain record is generated. If the match fails, an abnormal record is generated and returned by the channel.
[0010] Furthermore, the distributed ledger stores a redemption status index, which includes on-chain coin identifier, locked transaction identifier, redemption channel transaction identifier, and current redemption status. When a locked transaction record is generated, the current redemption status is written into the locked state. When an on-chain destruction record is generated, the current redemption status is updated to redemption completed. When an on-chain unlock record is generated, the current redemption status is updated to unlocked.
[0011] As a progressive solution, the redemption status index sets the status update time and status validity period. When the current redemption status is locked and the interval between the status update time and the current ledger time is greater than the status validity period, the locked transaction record and the redemption message record associated with the locked transaction record are read and an overdue verification record is generated. The overdue verification record includes the locked transaction identifier, on-chain coin identifier, digital RMB receiving identifier, redemption amount, request transaction field, status update time and overdue verification status. Based on the request transaction field, locked transaction identifier, on-chain coin identifier, digital RMB receiving identifier, and redemption amount in the timeout verification record, a redemption result query request is generated and sent to the digital RMB redemption channel; After receiving the query results returned by the digital RMB redemption channel, the returned transaction details, recipient, and redemption amount in the query results are compared with the request transaction details, digital RMB receiving identifier, and redemption quantity in the timeout verification record for consistency verification. When the consistency verification passes and the redemption processing status in the query results is "redemption successful," an on-chain destruction record is generated. When the consistency verification passes and the redemption processing status in the query results is "redemption failed," or when no valid redemption result consistent with the timeout verification record is found, an on-chain unlock record is generated.
[0012] Furthermore, the on-chain coin redemption request carries user signature data. After parsing the on-chain coin redemption request, the user signature data is verified using the public key data corresponding to the user's wallet address. If the verification is successful, the on-chain coin status query is executed. If the verification fails, the locking is refused and an invalid request record is generated. The invalid request record is written to the distributed ledger.
[0013] The present invention also provides an on-chain coin digital RMB redemption system, which corresponds to the above method and includes a request parsing module, a ledger query module, an on-chain locking module, a redemption interaction module, and a ledger update module; The request parsing module is used to receive on-chain coin redemption requests and parse them to obtain the on-chain coin identifier, redemption amount, user wallet address, and digital RMB receiving identifier; The ledger query module is used to query the status of on-chain coins in the distributed ledger based on the on-chain coin identifier and redemption amount, and generate a redeemable status record; The on-chain locking module is used to generate locked transaction records when the redeemable status record meets the redemption conditions; The redemption interaction module is used to send the digital RMB receiving identifier and redemption amount to the digital RMB redemption channel and receive the redemption confirmation result; The ledger update module is used to generate on-chain destruction records or on-chain unlock records based on the redemption confirmation results and write them into the distributed ledger.
[0014] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, on-chain coin redemption requests are parsed into on-chain coin identifiers, redemption quantity, user wallet address, and digital RMB receiving identifier. The balance status, freeze status, and redemption occupation status are first queried in the distributed ledger, and then a locked transaction record is generated. This ensures that the on-chain quota before entering the digital RMB redemption channel is occupied separately. The redemption confirmation result triggers the on-chain destruction record or the on-chain unlock record respectively. The association verification is completed with the locked transaction identifier and the redemption channel flow identifier. This creates a closed state under the same flow between on-chain locked external redemption and ledger update, reducing the inconsistency of ledger state caused by duplicate redemption transfer occupation and abnormal timeouts. Attached Figure Description
[0015] Figure 1 This is a schematic diagram illustrating the overall module interaction of the on-chain coin digital RMB redemption system; Figure 2 A schematic diagram of the data flow topology for on-chain coin digital RMB redemption methods; Figure 3 This is a diagram illustrating the redemption status index and status transition; Figure 4 A diagram illustrating the correlation and verification between locked transaction records and payment confirmation results; Figure 5 This is a schematic diagram of the input and output boundaries of the system modules; Figure 6 This is a schematic diagram of the exception handling path. Detailed Implementation
[0016] The technical solution described in this invention will be further explained below with reference to the accompanying drawings. On-chain coins refer to digital value objects recorded in a distributed ledger and characterized by ledger account balances, locking status, and transaction records. In some embodiments, a coin authenticator can serve as a front-end authentication device for on-chain coin redemption requests, used to verify the authenticity, quantity, or identification result of the coin carrier entering the redemption process, and using the device-side result formed by the authentication as auxiliary input in the request parsing stage. An on-chain coin redemption request refers to request data initiated by a user wallet to redeem a specified amount of on-chain coins for digital RMB, which includes at least an on-chain coin identifier, redemption quantity, user wallet address, and digital RMB receiving identifier. When a on-chain coin redemption request is triggered by a coin authenticator, the authentication result output by the coin authenticator can form a correspondence with the on-chain coin identifier, so as to perform device-side consistency confirmation of the object to be redeemed before ledger query. A redeemable status record refers to a status record formed based on the ledger account balance, unconfirmed transaction set, and locked amount in the distributed ledger, used to characterize whether a specified amount of on-chain coins can enter the redemption lock. Locked transaction records refer to transaction records in the distributed ledger that indicate the on-chain coin quota has been used in the redemption process. Redemption confirmation results refer to the processing results returned by the digital RMB redemption channel for redemption messages, including the redemption processing status and the redemption channel transaction identifier. The redemption processing status is marked as either a successful redemption or a failed redemption in the same return. On-chain destruction records are used to deduct the on-chain coin quota from the user's wallet address after a successful redemption, and on-chain unlock records are used to unlock the on-chain coin quota after a failed redemption or a redemption timeout.
[0017] Example 1 Please see Figure 1-4 This embodiment provides an on-chain coin digital RMB redemption method. This method takes an on-chain coin redemption request as input and on-chain coin status updates in the distributed ledger as output. Through continuous processing between on-chain locking, channel redemption, result confirmation, and ledger updates, the on-chain coin amount is made into a traceable occupied state before entering the digital RMB redemption channel, and correspondingly becomes destroyed or unlocked after redemption confirmation. In this method, a coin authentication device can act as an authentication trigger point outside the user's wallet, used to output the coin authentication result before the on-chain coin redemption request is generated, so that the device-side identification status, on-chain coin identifier, and redemption quantity can be verified together during the request parsing stage.
[0018] S1: Receive on-chain coin redemption requests and parse them to obtain the on-chain coin identifier, redemption amount, user wallet address, and digital RMB receiving identifier. The on-chain coin redemption request is initiated by the wallet corresponding to the user's wallet address. The on-chain coin identifier is used to locate the on-chain coin account or amount to be redeemed in the distributed ledger. The redemption amount indicates the amount of on-chain coins to be redeemed this time, and the digital RMB receiving identifier points to the recipient of the digital RMB after redemption. The parsing process reads the fields in the on-chain coin redemption request in a structured manner to form a request parsing result. The request parsing result serves as input for subsequent ledger status queries and redemption message construction. When the request source includes a coin authenticator, the request parsing result may also include an authentication result identifier output by the coin authenticator. This authentication result identifier indicates that the device has completed the identification of the coin carrier and is used for homology verification with the on-chain coin identifier.
[0019] In S1, on-chain coin redemption requests can also carry user signature data. The user signature data corresponds to the user's wallet address and is used to prove that the redemption request was initiated by an entity that can control the user's wallet address. After parsing the on-chain coin redemption request, the public key data corresponding to the user's wallet address can be read, and the user signature data can be verified using the public key data. If the verification passes, the on-chain coin identifier, redemption amount, user wallet address, and digital RMB receiving identifier proceed to subsequent processing; if the verification fails, on-chain locking is not performed, an invalid request record is generated, and the invalid request record is written to the distributed ledger. The invalid request record includes at least the user's wallet address, the on-chain coin identifier, the request time, and the verification failure status, used to create a traceable record of the invalid request on the ledger side. If the request also carries the authentication result identifier of the coin authentication device, the invalid request record can also record the state where a valid connection is not formed between the authentication result identifier and the user signature data, so that the user authorization failure and the coin authentication process can be separately recorded on the ledger side.
[0020] S2 queries the on-chain coin status in the distributed ledger based on the on-chain coin identifier and redemption amount, generating a redeemable status record including balance status, frozen status, and redemption occupation status. The ledger status query process reads the ledger account balance, account frozen status identifier, unconfirmed transaction set, and locked amount corresponding to the on-chain coin identifier. The ledger account balance represents the total on-chain coin amount under the user's wallet address corresponding to the on-chain coin identifier; the account frozen status identifier indicates whether the on-chain coin account or corresponding on-chain coin amount is marked as frozen by ledger rules; the unconfirmed transaction set represents the set of transaction records that have been initiated but not yet completed ledger confirmation; and the locked amount represents the on-chain coin amount that has been occupied by the redemption process but has not yet generated an on-chain destruction record or on-chain unlock record. When the on-chain coin identifier is confirmed by a coin authentication device, the ledger status query process can also read the corresponding status between the authentication result identifier and the on-chain coin identifier to determine whether the device-side identification object matches the ledger-side redemption object.
[0021] In S2, the available quota is obtained by subtracting the locked quota from the ledger account balance. The balance status is determined based on the correspondence between the available quota and the redemption amount, the frozen status is determined independently based on the account frozen status identifier, and the redemption occupancy status is determined based on whether there are any unconfirmed redemption transactions in the unconfirmed transaction set that occupy the same on-chain coin quota. If the available quota is greater than or equal to the redemption amount, the balance status is marked as satisfied; if the available quota is less than the redemption amount, the balance status is marked as unsatisfied. If the account frozen status identifier indicates that it is not frozen, the frozen status is marked as not triggered; if the account frozen status identifier indicates that it is frozen, the frozen status is marked as triggered. If there are no unconfirmed redemption transactions in the unconfirmed transaction set that occupy the same on-chain coin quota, the redemption occupancy status is marked as not triggered; if there are unconfirmed redemption transactions in the unconfirmed transaction set that occupy the same on-chain coin quota, the redemption occupancy status is marked as triggered. After the redeemable status record is formed, it is passed to the subsequent locking process and used to determine whether to generate a locked transaction record. If the identification result identifier output by the coin authenticator is inconsistent with the coin identifier on the chain, the redeemable status record can add a consistency status on the device side and mark the status as unsatisfactory to prevent inconsistent objects from entering the locking process.
[0022] S3, when the redeemable status record meets the redemption conditions, lock the on-chain coin amount corresponding to the user's wallet address according to the redemption amount, generating a lock transaction record. Redemption conditions include a balance status of "satisfied," a frozen status of "not triggered," and a redemption occupation status of "not triggered." When the redeemable status record meets the redemption conditions, the distributed ledger marks the on-chain coin amount corresponding to the on-chain coin identifier and redemption amount as a redemption lock state. The lock transaction record includes a lock transaction identifier, on-chain coin identifier, redemption amount, user wallet address, lock timestamp, and lock validity period. The lock transaction identifier is used to associate the same redemption process in subsequent on-chain destruction records, on-chain unlock records, and redemption status indexes. In implementations where the device participates in authentication, the lock transaction record can also receive the authentication result identifier output by the coin authentication instrument, ensuring that the lock transaction identifier, on-chain coin identifier, and authentication result identifier remain corresponding within the same redemption process.
[0023] During the lock-up period, the distributed ledger rejects duplicate transfer and redemption transactions that initiate and occupy the same on-chain coin amount using the same on-chain coin identifier. The rejection process does not alter already generated locked transaction records; instead, it generates a duplicate occupancy rejection record associated with the locked transaction identifier based on the duplicate request. This record can include the request time, user wallet address, on-chain coin identifier, and rejection status. This process ensures that the on-chain coin amount remains in a single occupied state until the digital RMB redemption channel returns a result, preventing the same amount from simultaneously entering the transfer and redemption processes. When duplicate requests originate from the same coin authenticator or different coin authenticators, the duplicate occupancy rejection record can record the device identification source, enabling the differentiation of duplicate occupancy states of the same on-chain coin identifier across multiple authentication triggers.
[0024] S4 sends the digital RMB receiving identifier and redemption quantity to the digital RMB redemption channel and receives the redemption confirmation result. Before sending, the digital RMB receiving identifier and redemption quantity can be converted into a redemption message. The redemption message includes a receiving identifier field, a redemption amount field, a request time field, and a request transaction field. The receiving identifier field is formed by the digital RMB receiving identifier, the redemption amount field is formed by the redemption quantity, the request time field is formed by the time the redemption message is initiated, and the request transaction field is used to correspond to the same redemption interaction between the digital RMB redemption channel and the distributed ledger. If the redemption message needs to undertake the authentication process of a coin authenticator, the redemption message can also save the authentication result identifier in the local record associated with the request transaction field, so that the channel interaction data does not directly expose the internal identification details of the device, while retaining the verifiable correspondence on the ledger side.
[0025] After receiving a payment message, the digital RMB payment channel returns a payment confirmation result. The confirmation result includes the payment processing status and the payment channel transaction identifier. The payment processing status is marked as either a successful payment or a failed payment within the same confirmation result. Upon receiving the confirmation result, the payment message and the confirmation result are matched according to the request transaction field. A successful match means that the payment channel transaction identifier in the confirmation result corresponds to the same payment interaction as the request transaction field. When a match is successful, an on-chain record is generated for the payment confirmation result; when a match fails, a channel return exception record is generated. The channel return exception record includes the request transaction field, the payment channel transaction identifier, and the channel return exception status, and is written to the distributed ledger to confirm in subsequent verification that a valid correspondence exists between the channel return result and the on-chain locked transaction record.
[0026] S5 generates an on-chain destruction record or an on-chain unlock record based on the redemption confirmation result, and writes the locked transaction record, redemption confirmation result, and on-chain destruction or unlock record into the distributed ledger. When the redemption processing status in the redemption confirmation result is "redemption successful," an on-chain destruction record is generated. The on-chain destruction record reads the locked transaction identifier, on-chain coin identifier, redemption quantity, and user wallet address from the locked transaction record, and deducts the on-chain coin amount corresponding to the redemption quantity from the user wallet address. After the deduction is completed, the redemption lock status corresponding to the on-chain coin amount in the distributed ledger terminates, and the on-chain destruction record becomes the ledger status basis for the completion of the on-chain coin amount redemption. When the locked transaction record inherits the authentication result identifier from the coin authenticator, the on-chain destruction record can use the association relationship of that authentication result identifier to indicate that the deducted on-chain coin amount has been triggered by the device-side authentication and the redemption closure has been completed.
[0027] When the redemption confirmation result shows a redemption failure status, an on-chain unlock record is generated. The on-chain unlock record reads the locked transaction identifier, on-chain coin identifier, redemption amount, and user wallet address from the locked transaction record, and unlocks the on-chain coin amount corresponding to the redemption amount. After unlocking, the on-chain coin amount is restored to a usable state allowed by the ledger rules, but whether it can be redeemed again in the future still requires re-processing through request parsing, ledger querying, and locking judgment in S1 to S3. Therefore, a redemption failure will not directly result in a deduction of the on-chain coin amount, nor will it cause the locked amount to remain locked indefinitely. If the request corresponding to the on-chain unlock record is triggered by the coin authentication tool, the on-chain unlock record can also retain the correspondence between the authentication result identifier and the locked transaction identifier, allowing for re-authentication or re-initiation of requests after a redemption failure to be reconfirmed based on a new request.
[0028] Before writing to the distributed ledger, a correlation verification is performed on locked transaction records, redemption confirmation results, on-chain destruction records, or on-chain unlocking records. This correlation verification includes checking if the locked transaction identifier, redemption amount, user wallet address, and redemption channel transaction identifier are consistent. If the locked transaction identifier, redemption amount, user wallet address, and the redemption channel transaction identifier are consistent, the correlation verification passes. When the correlation verification passes, the verified record is written to the distributed ledger; if the correlation verification fails, writing to the on-chain destruction or unlocking record is rejected, and an exception record is generated. The exception record can include the locked transaction identifier, exception fields, and exception status. After being written to the distributed ledger, the exception record is used for subsequent manual or interface verification. During the correlation verification process, if the locked transaction record contains an authentication result identifier corresponding to a coin authentication device, it can also be verified whether this authentication result identifier is consistent with the current on-chain coin identifier. If the verification fails, a device authentication exception record is generated.
[0029] In S5, the distributed ledger also stores a redemption status index. This index includes the on-chain coin identifier, the locked transaction identifier, the redemption channel transaction identifier, and the current redemption status. When a locked transaction record is generated, the current redemption status is written as "locked"; when an on-chain destruction record is generated, the current redemption status is updated to "redemption completed"; and when an on-chain unlock record is generated, the current redemption status is updated to "unlocked". The redemption status index is used to quickly determine whether the on-chain coin amount is locked, redeemed completed, or unlocked when querying the on-chain coin identifier, and to determine whether there is an unclosed redemption process when duplicate requests arrive. When a coin authentication device participates in a request trigger, the redemption status index can indirectly associate the authentication result identifier through the locked transaction identifier, thus preserving the device-side authentication link without changing the core fields of the index.
[0030] The redemption status index can also be configured with a status update time and a status validity period. The status update time represents the ledger time of the most recent write or update to the current redemption status, and the status validity period represents the allowed duration of the locked status. When the current redemption status is locked and the interval between the status update time and the current ledger time is greater than the status validity period, the locked transaction record and the redemption message record associated with the locked transaction record are read, and a timeout verification record is generated. The timeout verification record includes at least the locked transaction identifier, on-chain coin identifier, digital RMB receiving identifier, redemption amount, request transaction field, status update time, and timeout verification status. Specifically, the locked transaction identifier and on-chain coin identifier are used to determine the locked redemption process on the ledger side, the digital RMB receiving identifier and redemption amount are used to determine the receiving object and redemption amount that should be queried on the digital RMB redemption channel side, and the request transaction field is used to determine the correspondence between the redemption message and the channel's returned result.
[0031] Based on the request transaction field, locked transaction identifier, on-chain coin identifier, digital RMB receiving identifier, and redemption quantity in the timeout verification record, a redemption result query request is generated and sent to the digital RMB redemption channel. After the digital RMB redemption channel returns the query result, the ledger update module performs a consistency verification between the returned transaction, receiving object, and redemption amount in the query result and the request transaction field, digital RMB receiving identifier, and redemption quantity in the timeout verification record. If the consistency verification passes and the redemption processing status in the query result is "redemption successful," the ledger update module generates an on-chain destruction record; if the consistency verification passes and the redemption processing status in the query result is "redemption failed," or if no valid redemption result consistent with the timeout verification record is found, the ledger update module generates an on-chain unlock record. Through this process, the timeout verification record is not only used to trigger channel queries but also serves as the source of channel query parameters and the basis for query result matching, ensuring that on-chain destruction or on-chain unlocking in the timeout state can correspond to the same locked transaction record and the same redemption message record. If the locked transaction record corresponding to the timeout verification record originates from a request triggered by the coin authenticator, the timeout verification record can retain the associated fields of the device-side authentication result to distinguish between channel timeout and device authentication anomaly.
[0032] The above method begins each redemption process with an on-chain coin redemption request and ends with a ledger state update. The redeemable state record receives the on-chain coin state query result; the locked transaction record receives the redeemable state record; the redemption message receives the digital RMB receiving identifier and redemption quantity; the redemption confirmation result receives the return status of the digital RMB redemption channel; and the on-chain destruction record or on-chain unlock record receives the redemption confirmation result. Finally, a state closure is formed through writing to the distributed ledger. Through this sequential processing, any on-chain coin digital RMB redemption process can be traced back to the corresponding records of request parsing, quota locking, channel interaction, and state update in the distributed ledger. For implementation scenarios involving coin authenticators, this sequential processing also preserves the correspondence between the device-side authentication result and the on-chain coin identifier between request parsing, quota locking, and ledger update, ensuring that the coin authenticator's authentication action does not deviate from the on-chain redemption closed loop.
[0033] Example 2 Please see Figure 1 and Figure 5This embodiment provides an on-chain coin-based digital RMB redemption system. Compared to Embodiment 1, this embodiment explains how each module carries and executes the processing flow of the method described in Embodiment 1 from the perspective of system module collaboration. The system includes a request parsing module, a ledger query module, an on-chain locking module, a redemption interaction module, and a ledger update module. The modules form a redemption processing link through data input and output relationships. In a system configuration that includes a coin authenticator, the coin authenticator can communicate with the request parsing module to provide the request parsing module with an authentication result identifier or authentication result flag.
[0034] The request parsing module receives on-chain coin redemption requests and parses them to obtain the on-chain coin identifier, redemption amount, user wallet address, and digital RMB receiving identifier. The input to the request parsing module is the on-chain coin redemption request, and the output is the request parsing result. The request parsing result includes at least the on-chain coin identifier, redemption amount, user wallet address, and digital RMB receiving identifier, and is transmitted to the ledger query module. The request parsing module can also read the user signature data from the on-chain coin redemption request and use the public key data corresponding to the user wallet address to complete signature verification. When the signature verification is successful, the request parsing module outputs the request parsing result to the ledger query module; when the signature verification fails, the request parsing module outputs an invalid request record to the ledger update module. When a coin authenticator is connected to the request parsing module, the request parsing module can also receive the authentication result identifier output by the coin authenticator and encapsulate this authentication result identifier along with the on-chain coin identifier into the request parsing result.
[0035] The ledger query module is used to query the status of on-chain coins in the distributed ledger based on the on-chain coin identifier and redemption amount, and generate a redeemable status record. The inputs to the ledger query module include the on-chain coin identifier, redemption amount, and user wallet address from the request parsing module. The resources invoked are the ledger account balance, unconfirmed transaction set, and locked amount in the distributed ledger. After reading the above data, the ledger query module calculates the available amount and generates a redeemable status record based on the available amount, frozen status, and whether there are unconfirmed redemption transactions occupying the same on-chain coin amount in the unconfirmed transaction set. The redeemable status record is output to the on-chain locking module. If the request parsing result contains a coin authentication result identifier, the ledger query module can also write the corresponding status of that identifier and the on-chain coin identifier into the redeemable status record.
[0036] The on-chain locking module generates a locking transaction record when the redeemable status record meets the redemption conditions. The inputs to the on-chain locking module are the redeemable status record, the on-chain coin identifier, the redemption amount, and the user's wallet address. The on-chain locking module determines the balance status, frozen status, and redemption occupation status in the redeemable status record. If the balance status is satisfied, the frozen status is not triggered, and the redemption occupation status is not triggered, the on-chain coin amount corresponding to the redemption amount is marked as a redemption locked status, and a locking transaction record is generated. The locking transaction record is output to the redemption interaction module and the ledger update module. If the redeemable status record does not meet the redemption conditions, the on-chain locking module does not perform an amount lock and outputs a locking failure record to the ledger update module. When the device-side consistency status in the redeemable status record is not satisfied, the on-chain locking module also does not perform an amount lock and can write an inconsistent coin authenticator result status to the locking failure record.
[0037] The redemption interaction module sends the digital RMB receiving identifier and redemption amount to the digital RMB redemption channel and receives the redemption confirmation result. The inputs to the redemption interaction module include the digital RMB receiving identifier, redemption amount, and locked transaction record. The redemption interaction module constructs a redemption message based on the digital RMB receiving identifier and redemption amount. The redemption message includes a receiving identifier field, a redemption amount field, a request time field, and a request transaction record field. The redemption interaction module sends the redemption message to the digital RMB redemption channel and receives the redemption confirmation result returned by the digital RMB redemption channel. The redemption confirmation result includes the redemption processing status and the redemption channel transaction record identifier. The redemption processing status is marked as either a successful redemption or a failed redemption status in the same redemption confirmation result. The redemption interaction module matches the redemption message and the redemption confirmation result according to the request transaction record field. If the match is successful, the redemption confirmation result and the request transaction record field are output to the ledger update module; if the match fails, an exception record is returned to the ledger update module. The payment interaction module does not need to directly control the coin authentication device. Instead, it indirectly receives the authentication result identifier by locking transaction records, thereby maintaining the data boundary between the channel payment process and the device authentication process.
[0038] The ledger update module generates on-chain destruction or unlocking records and writes them to the distributed ledger based on the redemption confirmation results. The inputs to the ledger update module include locked transaction records, redemption confirmation results, invalid request records, locked failure records, or channel return exception records. For redemption confirmation results showing a successful redemption status, the ledger update module generates an on-chain destruction record and deducts the corresponding on-chain coin amount from the user's wallet address. For redemption confirmation results showing a failed redemption status, the ledger update module generates an on-chain unlocking record and unlocks the on-chain coin amount corresponding to the redemption quantity. The ledger update module performs a correlation verification before writing; if the correlation verification passes, it writes to the distributed ledger; if the correlation verification fails, it writes an exception record. When a locked transaction record contains a coin authentication result identifier, the ledger update module can use this identifier as an auxiliary object for correlation verification, ensuring that the on-chain destruction or unlocking record corresponds to the device-side authentication source.
[0039] The ledger update module can also maintain a redemption status index. This index consists of the on-chain coin identifier, the locked transaction identifier, the redemption channel transaction identifier, and the current redemption status. When the on-chain locking module generates a locked transaction record, the ledger update module writes the current redemption status as locked; when an on-chain destruction record is generated, the ledger update module updates the current redemption status to redemption completed; when an on-chain unlock record is generated, the ledger update module updates the current redemption status to unlocked. The current redemption status is used by the ledger query module to read when the next on-chain coin redemption request arrives, enabling duplicate redemption requests or duplicate transfer transactions to be identified and rejected. For redemption requests repeatedly triggered by the coin counter, the ledger query module can identify whether the same on-chain coin identifier is already locked based on the current redemption status, thereby preventing duplicate authentication on the device side from causing the same amount to be used repeatedly.
[0040] In this embodiment, a fixed data connection relationship is established between the request parsing module, ledger query module, on-chain locking module, redemption interaction module, and ledger update module. The request parsing result output by the request parsing module is read by the ledger query module; the redeemable status record output by the ledger query module is read by the on-chain locking module; the locked transaction record output by the on-chain locking module is read by the redemption interaction module and the ledger update module; the redemption confirmation result output by the redemption interaction module is read by the ledger update module; and the on-chain destruction record, on-chain unlock record, or anomaly record output by the ledger update module are written to the distributed ledger. Thus, the responsibilities, input sources, output recipients, and ledger writing objects of each module within the system remain consistent. The coin authenticator exists as a front-end authentication input source in this connection relationship; its output is processed by the request parsing module without altering the responsibilities of the ledger query module, on-chain locking module, redemption interaction module, and ledger update module.
[0041] Example 3 Please see Figure 2 , Figure 3 and Figure 6 This embodiment provides an exception handling implementation method for on-chain coin-based digital RMB redemption. Compared to Embodiment 1, this embodiment focuses on describing the state switching paths when lock timeout occurs, channel return anomalies occur, signature verification fails, and association verification fails, and ensures that the abnormal states can be recorded and subsequently read by the distributed ledger. In the embodiment including a coin authentication device, this embodiment also describes the exception recording method when the authentication results on the device side are inconsistent.
[0042] Once an on-chain coin redemption request enters the request parsing phase, if the user's signature data fails verification, the request parsing phase does not output the fields required for redemption determination to the ledger query phase. Instead, it generates an invalid request record. After the invalid request record is written to the distributed ledger, the current redemption process terminates. This termination status does not change the on-chain coin amount, does not generate a locked transaction record, and does not send a redemption message to the digital RMB redemption channel. Since the invalid request record already contains the user's wallet address, on-chain coin identifier, and signature failure status, the distributed ledger can display in subsequent queries that this request did not enter the amount lock. If the request also carries the authentication result identifier of the coin authentication device, the invalid request record can retain the correspondence between the authentication result identifier and the signature failure status, but this correspondence does not trigger on-chain locking.
[0043] If the signature verification passes but the redemption status record does not meet the redemption conditions, no locked transaction record will be generated during the on-chain locking phase. The balance status, frozen status, and redemption occupancy status in the redemption status record are used to determine the specific source of the locking failure. When the balance status is not met, the locking failure record points to insufficient available quota; when the frozen status is triggered, the locking failure record points to the on-chain coin quota being frozen; when the redemption occupancy status is triggered, the locking failure record points to an unclosed redemption occupancy of the same on-chain coin quota. After the locking failure record is written to the distributed ledger, this process will not enter the digital RMB redemption channel. If the authentication result identifier output by the coin authentication device is inconsistent with the on-chain coin identifier, the locking failure record can also point to a lack of consistency status on the device side, causing the request to stop at the abnormal branch after the ledger query.
[0044] If a locked transaction record has been generated, but the payment confirmation result returned by the digital RMB payment channel cannot be matched through the request transaction field, a channel return exception record will be generated during the payment interaction phase. This exception record is associated with the locked transaction record but does not directly trigger on-chain record destruction. At this time, the current payment status in the payment status index remains locked, awaiting subsequent timeout verification or a valid payment confirmation result. Through this process, channel return results that fail to confirm the corresponding relationship will not be used to deduct on-chain coin amounts.
[0045] If the payment confirmation result matches the request transaction field, but the association verification fails before being written to the distributed ledger, the ledger update phase will refuse to write the on-chain destruction or unlocking record and generate an anomaly record. Association verification failure can be caused by inconsistent locked transaction identifiers, inconsistent payment amounts, inconsistent user wallet addresses, or an empty payment channel transaction identifier. After the anomaly record is written to the distributed ledger, the current payment status can remain locked, and the timeout verification path will trigger a query for the payment result of the digital RMB payment channel. This process prevents inconsistent payment confirmation results from directly changing the on-chain coin status. When the association verification failure is related to inconsistent coin authentication result identifiers, the anomaly record can record the abnormal field as the authentication result identifier to distinguish it from the anomaly of the payment channel transaction identifier.
[0046] For timeout handling in the locked state, the redemption status index reads the status update time and status validity period, and compares the interval between the status update time and the current ledger time with the status validity period. When the current redemption status is locked, and the interval between the status update time and the current ledger time is greater than the status validity period, a timeout verification record is generated. When generating the timeout verification record, the ledger update module reads the locked transaction record and the redemption message record associated with the locked transaction record, and writes the locked transaction identifier, on-chain coin identifier, digital RMB receiving identifier, redemption amount, request transaction history field, status update time, and timeout verification status into the timeout verification record. The above fields in the timeout verification record are used to construct the redemption result query request, rather than just serving as a trigger for starting the query.
[0047] After a redemption result query request is sent to the digital RMB redemption channel, the channel returns the query result. The ledger update module verifies the consistency of the returned transaction details, recipient, and redemption amount in the query result with the request transaction fields, digital RMB receiving identifier, and redemption quantity in the timeout verification record. If the consistency verification passes and the redemption processing status in the query result is "redemption successful," an on-chain destruction record is generated. If the consistency verification passes and the redemption processing status in the query result is "redemption failed," or no valid redemption result consistent with the timeout verification record is found, an on-chain unlock record is generated. If the returned transaction details, recipient, or redemption amount in the query result cannot be consistently matched with the timeout verification record, the query result is not used as the basis for generating an on-chain destruction record, and a timeout query exception record is generated or the process enters the on-chain unlock processing path. The timeout verification record, query result, on-chain destruction record, or on-chain unlock record are all associated with the same redemption process through a locked transaction identifier. For processes triggered by a coin counter and for which locked transaction records have been generated, the timeout verification record will not call the coin counter again for repeated authentication. Instead, it will be traced back based on the authentication result identifier that has already been written into the locked transaction record.
[0048] The exception handling path in this embodiment does not change the main process order of Embodiment 1. Instead, it sets observable exception outputs at the request parsing, ledger query, on-chain locking, redemption interaction, and ledger update nodes of the main process. Each exception output has a clear triggering condition, ledger writing object, and subsequent state impact. Invalid request records terminate unauthorized requests, lock failure records terminate requests that do not meet redemption conditions, channel return exception records prevent mismatched channel results from changing ledger amounts, association verification failures generate exception records and retain subsequent verification entry points, and timeout verification records cause long-term locked states to enter the destruction or unlocking branch. Thus, exception states do not leave the distributed ledger's state recording chain. Inconsistent authentication results, duplicate authentication triggers, and device-side identification state anomalies related to coin authentication instruments can all enter the distributed ledger through the above exception recording chain, thereby maintaining the traceability relationship between the device authentication process and the on-chain redemption state.
[0049] Example 4 Please see Figure 1 , Figure 3 and Figure 5This embodiment provides a related implementation of an on-chain coin-based digital RMB redemption system. Compared to Embodiment 2, this embodiment illustrates the module integration relationships of the system under different deployment configurations. The system can be deployed on a computing device capable of accessing the distributed ledger and communicating with the digital RMB redemption channel. Alternatively, multiple computing nodes can respectively carry the request parsing module, ledger query module, on-chain locking module, redemption interaction module, and ledger update module. The coin authentication device can communicate as an independent device with the computing node carrying the request parsing module, or it can act as a front-end device with an identification output interface to provide authentication result identifiers to the system.
[0050] When all modules are deployed on the same computing device, the request parsing module writes the request parsing result into the local processing context. The ledger query module reads the on-chain coin identifier, redemption amount, and user wallet address from the local processing context and initiates a status read to the distributed ledger. The on-chain locking module receives the redeemable status record output by the ledger query module and submits the locked transaction record to the distributed ledger. The redemption interaction module reads the locked transaction identifier from the locked transaction record and the digital RMB receiving identifier from the request parsing result, constructs a redemption message, and communicates with the digital RMB redemption channel. The ledger update module receives the redemption confirmation result and performs correlation verification. After successful verification, it submits the on-chain destruction record or on-chain unlock record. In this deployment configuration, the authentication result identifier output by the coin authenticator can first enter the local processing context and then be read by the ledger query module along with the request parsing result.
[0051] When the modules are deployed across multiple computing nodes, the request parsing result transmitted between the request parsing module and the ledger query module includes at least the on-chain coin identifier, redemption quantity, user wallet address, and digital RMB receiving identifier; the redeemable status record transmitted between the ledger query module and the on-chain locking module includes at least the balance status, frozen status, and redemption occupied status; the locking transaction record transmitted between the on-chain locking module and the redemption interaction module includes at least the locking transaction identifier, on-chain coin identifier, redemption quantity, and user wallet address; the redemption confirmation result transmitted between the redemption interaction module and the ledger update module includes at least the redemption processing status and the redemption channel flow identifier, wherein the redemption processing status is marked as either a successful redemption status or a failed redemption status in the same redemption confirmation result. The nodes can transmit the above data objects through communication connections, but the specific protocol type of the communication connection is not specifically limited. When the coin authenticator and the request parsing module are in different physical locations, the content transmitted by the coin authenticator to the request parsing module can be limited to the authentication result identifier, the authentication result identifier, and the corresponding information of the on-chain coin identifier, without requiring subsequent nodes to directly access the coin authenticator.
[0052] During system operation, the ledger update module performs unified writing of all records that need to be written to the distributed ledger, including invalid request records, failed lock records, locked transaction records, channel return exception records, on-chain destruction records, on-chain unlock records, and exception records. Unified writing does not require all records to have identical fields; rather, it requires that each record can be traced back to the corresponding redemption process through an on-chain coin identifier or a locked transaction identifier. For invalid request records and failed lock records that have not generated locked transaction records, tracing can be done through the on-chain coin identifier and the user's wallet address; for subsequent records that have already generated locked transaction records, tracing can be done through the locked transaction identifier. Records generated with the participation of the coin authentication device can be further traced using the authentication result identifier, ensuring that device-side authentication, on-chain locking, and redemption results maintain a consistent relationship within the same process.
[0053] In this embodiment, the system deployment does not change the boundaries of module responsibilities. The request parsing module is responsible for parsing request fields and verifying signatures; the ledger query module is responsible for reading on-chain coin status and generating redeemable status records; the on-chain locking module is responsible for locking quotas and generating locked transaction records; the redemption interaction module is responsible for sending redemption messages and receiving redemption confirmation results; and the ledger update module is responsible for association verification, status record generation, and distributed ledger writing. Therefore, regardless of whether the system is deployed with a single node or multiple nodes, the on-chain coin digital RMB redemption process maintains the same data flow path and the same ledger state closure method. The integration of the coin authentication device does not change the above module division of labor, but adds authentication result input to the request parsing front end, enabling the authentication result identifier to be included in the same data flow path.
[0054] The specific embodiments described above illustrate the feasible implementation methods of the technical solutions described in this invention. The request fields, status records, module divisions, processing order, abnormal branches, ledger writing relationships, and channel interaction relationships in the embodiments can be equivalently replaced or combined without changing the substantial correspondence between the on-chain coin identifier, redemption quantity, user wallet address, digital RMB receiving identifier, locked transaction record, redemption confirmation result, on-chain destruction record, on-chain unlock record, and distributed ledger. In embodiments involving coin authentication devices, the device form, communication access method, and authentication result identifier field name of the coin authentication device can be equivalently changed without changing its technical function as a front-end authentication input source. For those skilled in the art, equivalent modifications made to field names, module carriers, communication connection forms, execution entity correspondences, or record storage forms without departing from the technical solutions described in this invention and the application documents should fall within the scope of patent protection of this application.
Claims
1. A method for on-chain coin-based digital RMB redemption, characterized in that, include: Receive on-chain coin redemption requests and parse them to obtain the on-chain coin identifier, redemption amount, user wallet address, and digital RMB receiving identifier; Based on the on-chain coin identifier and the redemption amount, query the on-chain coin status in the distributed ledger to generate a redeemable status record containing the balance status, frozen status, and redemption occupation status; When the redeemable status record meets the redemption conditions, the on-chain coin amount corresponding to the user's wallet address is locked according to the redemption amount, and a lock transaction record is generated. Send the digital RMB receiving identifier and the redemption amount to the digital RMB redemption channel, and receive the redemption confirmation result; Generate an on-chain destruction record or an on-chain unlock record based on the redemption confirmation result, and write the locked transaction record, the redemption confirmation result, the on-chain destruction record, or the on-chain unlock record into the distributed ledger; The distributed ledger stores a redemption status index, which includes the on-chain coin identifier, the locked transaction identifier, the redemption channel transaction identifier, and the current redemption status. When generating the locked transaction record, the current redemption status is written into the lock; When generating the on-chain destruction record, the current redemption status is updated to redemption completed; When generating the on-chain unlock record, the current redemption status is updated to "unlocked"; The payment status index is configured with a status update time and a status validity period. When the current redemption status is locked and the interval between the status update time and the current ledger time is greater than the status validity period, the locked transaction record and the redemption message record associated with the locked transaction record are read and an overtime verification record is generated. The overtime verification record includes the locked transaction identifier, on-chain coin identifier, digital RMB receiving identifier, redemption amount, request transaction field, status update time and overtime verification status. A redemption result query request is generated based on the request transaction field, the locked transaction identifier, the on-chain coin identifier, the digital RMB receiving identifier, and the redemption amount in the timeout verification record, and the redemption result query request is sent to the digital RMB redemption channel; The system receives the query results returned by the digital RMB redemption channel. The query results include the redemption processing status, the returned transaction record, the recipient, and the redemption amount. The redemption processing status is marked as either a successful redemption or a failed redemption in the same query result. The system then performs consistency verification between the returned transaction record, the recipient, and the redemption amount in the query result and the request transaction record field, the digital RMB receiving identifier, and the redemption quantity in the timeout verification record. When the consistency verification passes and the redemption processing status in the query result is the redemption success status, the on-chain destruction record is generated; When the consistency verification passes and the redemption processing status in the query result is the redemption failure status, or when no valid redemption result consistent with the timeout verification record is found, the on-chain unlock record is generated.
2. The on-chain coin digital RMB redemption method according to claim 1, characterized in that, Generating the redeemable status record includes: Read the ledger account balance, account freeze status indicator, unconfirmed transaction set, and locked amount corresponding to the on-chain coin identifier; The available credit is obtained by subtracting the locked amount from the account balance in the ledger. The freezing status is determined independently based on the account freezing status identifier, and the redemption occupation status is determined based on whether there are unconfirmed redemption transactions occupying the same on-chain coin quota in the unconfirmed transaction set; When the available credit is greater than or equal to the redemption amount, the balance status is marked as satisfied; when the available credit is less than the redemption amount, the balance status is marked as unsatisfactory. When the account freeze status indicator indicates that it is not frozen, the freeze status is marked as not triggered; when the account freeze status indicator indicates that it is frozen, the freeze status is marked as triggered. When there are no unconfirmed redemption transactions occupying the same on-chain coin quota in the unconfirmed transaction set, the redemption occupation status is marked as not triggered; when there are unconfirmed redemption transactions occupying the same on-chain coin quota, the redemption occupation status is marked as triggered.
3. The on-chain coin digital RMB redemption method according to claim 2, characterized in that, The locked transaction record includes the locked transaction identifier, the on-chain coin identifier, the redemption amount, the user wallet address, the locked timestamp, and the locked validity period; During the lock-up period, the distributed ledger marks the on-chain coin amount corresponding to the redemption amount as a redemption lock-up state and rejects duplicate transfer transactions and duplicate redemption transactions initiated with the on-chain coin identifier; When the lock-up period expires and no payment confirmation result is received, the on-chain unlock record is generated.
4. The on-chain coin digital RMB redemption method according to claim 1, characterized in that, The payment confirmation result includes the payment processing status and the payment channel flow identifier. The payment processing status is marked as either a payment success status or a payment failure status in the same payment confirmation result. When the redemption processing status in the redemption confirmation result is the redemption success status, the on-chain destruction record is generated. The on-chain destruction record is used to deduct the on-chain coin amount corresponding to the redemption amount from the user's wallet address. When the redemption processing status in the redemption confirmation result is the redemption failure status, the on-chain unlock record is generated. The on-chain unlock record is used to unlock the redemption lock status of the on-chain coin amount corresponding to the redemption quantity.
5. The on-chain coin digital RMB redemption method according to claim 4, characterized in that, Before writing to the distributed ledger, the locked transaction record, the redemption confirmation result, the on-chain destruction record, or the on-chain unlock record are correlated and verified. The association verification includes verifying whether the locked transaction identifier is consistent, whether the redemption amount is consistent, whether the user wallet address is consistent, and whether the redemption channel transaction identifier is empty; When the association verification passes, the verified record is written to the distributed ledger; when the association verification fails, the write is rejected and an abnormal record is generated.
6. The on-chain coin digital RMB redemption method according to claim 1, characterized in that, The digital RMB receiving identifier is converted into a payment message before being sent to the digital RMB payment channel; The payment message includes a receiving identifier field, a payment amount field, a request time field, and a request transaction record field; After receiving the payment confirmation result, the payment message and the payment confirmation result are matched according to the request transaction field. If the match is successful, an on-chain record is generated; if the match fails, a channel return exception record is generated.
7. The on-chain coin digital RMB redemption method according to claim 1, characterized in that, The on-chain coin redemption request carries user signature data; After parsing the on-chain coin redemption request, the user signature data is verified using the public key data corresponding to the user's wallet address; If the signature verification is successful, the on-chain coin status query is performed. If the signature verification fails, the locking is refused and an invalid request record is generated. The invalid request record is written into the distributed ledger.
8. An on-chain coin-based digital RMB redemption system, wherein the on-chain coin-based digital RMB redemption system corresponds to the on-chain coin-based digital RMB redemption method according to claim 1, characterized in that, include: The request parsing module is used to parse the on-chain coin redemption request and obtain the on-chain coin identifier, redemption amount, user wallet address and digital RMB receiving identifier; The ledger query module is used to query the status of the on-chain coin in the distributed ledger based on the on-chain coin identifier and the redemption amount, and generate a redeemable status record. The on-chain locking module is used to generate a locked transaction record when the redeemable status record meets the redemption conditions; The redemption interaction module is used to send the digital RMB receiving identifier and the redemption amount to the digital RMB redemption channel and receive the redemption confirmation result; The ledger update module is used to generate on-chain destruction records or on-chain unlock records based on the redemption confirmation results and write them into the distributed ledger.
Citation Information
Patent Citations
Method and system of exchanging digital currencies
CN107330784A
Cross-border payment processing method and device, electronic equipment, computer readable storage medium and computer program product
CN122636203A
