Blockchain-based equity certificate management method, device, electronic device, and medium

Abstract

This application provides a blockchain-based equity certificate management method, apparatus, electronic device, and readable medium. The method includes: receiving an equity certificate minting request, the equity certificate minting request carrying an account address in the blockchain and equity data of the equity certificate to be minted; generating certificate metadata based on the equity certificate minting request, wherein the certificate metadata includes the account address and equity data; and creating an equity certificate minting transaction based on the certificate metadata to mint an equity certificate associated with the account address in the blockchain, wherein the equity certificate contains the certificate metadata, and the account address in the certificate metadata is used to indicate the binding of the equity certificate to the account address. This method can improve the sophistication of equity certificate management, thereby reducing management difficulty and improving management efficiency.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a blockchain-based equity certificate management method, device, electronic device, and readable medium. Background Art

[0002] With the development of blockchain technology, equity certificates represented by digital collections have been applied in related fields. As an irreplaceable and unique equity certificate, digital collections have been put into practical use in the transaction of digital products and the management of electronic certificates.

[0003] In related technologies, smart contracts are usually used to manage equity certificates such as digital collections, such as creation, transfer and destruction.

[0004] However, in the current management process of such equity certificates, the management of the ownership of the equity certificates depends on the certificate trading process. The ownership management process of the equity certificates is relatively rough, difficult to manage and has low management efficiency. Summary of the Invention

[0005] Based on the above technical problems, the present application provides a blockchain-based equity certificate management method, device, electronic device and readable medium to improve the level of refinement of equity certificate management, which is conducive to reducing management difficulty and improving management efficiency.

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

[0007] According to one aspect of an embodiment of the present application, a blockchain-based equity certificate management method is provided, comprising:

[0008] Receive a request for minting a stake certificate, the request carrying an account address in the blockchain and stake data of the stake certificate to be minted;

[0009] Generate certificate metadata according to the equity certificate minting request, wherein the certificate metadata includes the account address and the equity data;

[0010] Creating a stake certificate minting transaction based on the certificate metadata to mint a stake certificate associated with the account address in the blockchain, wherein the stake certificate contains the certificate metadata, and the account address in the certificate metadata is used to indicate that the stake certificate is bound to the account address.

[0011] According to one aspect of an embodiment of the present application, a blockchain-based equity certificate management device is provided, comprising:

[0012] A casting request receiving module, configured to receive a casting request for an equity certificate, wherein the casting request carries an account address in the blockchain and equity data of the equity certificate to be cast;

[0013] A metadata generation module, configured to generate certificate metadata according to the equity certificate casting request, wherein the certificate metadata includes the account address and the equity data;

[0014] A minting transaction creation module is configured to create a stake certificate minting transaction based on the certificate metadata, so as to mint a stake certificate associated with the account address in the blockchain, wherein the stake certificate contains the certificate metadata, and the account address in the certificate metadata is used to indicate that the stake certificate is bound to the account address.

[0015] In some embodiments of the present application, based on the above technical solution, the equity certificate minting request also carries the account identifier of the requesting account corresponding to the account address; the equity certificate management device further includes:

[0016] An account information acquisition module, configured to acquire the account information of the requesting account according to the account identifier of the requesting account;

[0017] An encryption calculation module, configured to perform encryption calculation based on the account information and the equity data to generate a token identifier;

[0018] The minting transaction creation module includes:

[0019] A transaction creation unit is configured to create a stake certificate casting transaction based on the token identifier and the certificate metadata, wherein the stake certificate casting transaction includes a correspondence between the token identifier and the certificate metadata.

[0020] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0021] A verification request receiving module, configured to receive a credential verification request, wherein the credential verification request includes a token identifier of the equity credential to be verified;

[0022] A first metadata acquisition module, configured to acquire the credential metadata of the equity credential to be verified according to the token identifier of the equity credential to be verified;

[0023] The verification information generation module is used to generate the ownership verification information of the equity certificate to be verified according to the account address in the certificate metadata of the equity certificate to be verified.

[0024] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0025] A transfer request receiving module, configured to receive a request for transferring an equity certificate, wherein the request contains a token identifier of a target equity certificate;

[0026] A second metadata acquisition module, configured to acquire the certificate metadata corresponding to the target equity certificate according to the token identifier in the equity certificate transfer request;

[0027] The failure message generation module is configured to generate a certificate transfer failure message if the certificate metadata of the target equity certificate contains an account address, so as to indicate that the transfer of the target equity certificate has failed.

[0028] In some embodiments of the present application, based on the above technical solution, the second metadata acquisition module includes:

[0029] a transfer transaction creating unit, configured to create an equity certificate transfer transaction according to the received equity certificate transfer request, wherein the equity certificate transfer transaction includes the token identifier in the equity certificate transfer request;

[0030] An on-chain unit, configured to upload the equity certificate transfer transaction to the blockchain, so that the blockchain parses the target equity certificate corresponding to the token identifier according to the equity certificate contract and feeds back the certificate metadata of the target equity certificate;

[0031] The metadata receiving unit is configured to receive the certificate metadata of the target equity certificate.

[0032] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0033] a generation request receiving module, configured to receive a request for generating equity data, wherein the request carries an account identifier of the requesting account corresponding to the account address;

[0034] a certificate information acquisition module, configured to acquire, based on the account identifier, the account information of the requesting account and the certificate information of the certificate obtained by the requesting account;

[0035] A rights and interests data generation module, configured to generate the rights and interests data according to the account information and the certificate information;

[0036] The storage address feedback module is used to feedback the storage address of the equity data to the client.

[0037] In some embodiments of the present application, based on the above technical solution, the certificate information acquisition module includes:

[0038] an account information obtaining unit, configured to obtain the account information of the requesting account from the blockchain according to the account identifier;

[0039] an authority verification unit, configured to verify, based on the account information, the permission of the requesting account to obtain the certificate corresponding to the certificate information;

[0040] An account information sending unit, configured to send the account information to the certificate authentication service if the verification is successful, so that the certificate authentication service feeds back a corresponding certificate number based on the account information;

[0041] The certificate number receiving unit is configured to receive the certificate number sent by the certificate authentication service as the certificate information.

[0042] In some embodiments of the present application, based on the above technical solution, the rights and interests data is a certificate image; and the rights and interests data generation module includes:

[0043] An image generation request receiving unit, configured to receive a certificate image generation request, wherein the certificate image generation request includes the account information, the certificate number, the certificate base map, and location coordinate information;

[0044] The certificate image generating unit is configured to superimpose the account information and the certificate number onto the certificate base map according to the location coordinate information to generate the certificate image.

[0045] In some embodiments of the present application, based on the above technical solution, after creating the equity certificate minting transaction according to the certificate metadata, the equity certificate management device further includes:

[0046] A minting transaction on-chain module, used to put the equity certificate minting transaction on-chain in the blockchain;

[0047] The response feedback module is used to feed back a minting response message of the equity certificate to the client, so that the client can display the equity certificate.

[0048] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0049] A registration request receiving module, configured to receive an account registration request, wherein the account registration request includes account information;

[0050] A requesting account generating module, configured to generate a requesting account in the blockchain according to the account information;

[0051] The account address feedback module is used to feedback the account address of the requesting account in the blockchain.

[0052] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the blockchain-based equity certificate management method in the above technical solution by executing the executable instructions.

[0053] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the blockchain-based equity certificate management method in the above technical solution is implemented.

[0054] According to one aspect of an embodiment of the present application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the blockchain-based equity certificate management method provided in the various optional implementations described above.

[0055] In an embodiment of the present application, in the process of minting equity certificates, the account address in the blockchain is added as an identifier in the certificate metadata of the equity certificate, the equity certificate is bound to the account address, and the owner information is directly added to the equity certificate, so that the equity certificate can be directly managed without relying on the transaction information of the blockchain, thereby improving the level of refinement of equity certificate management, reducing management difficulty and improving management efficiency.

[0056] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, explaining the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can derive other drawings based on these drawings without inventive effort. In the drawings:

[0058] Figure 1 A schematic diagram of an optional structure of the equity certificate management system provided by an embodiment of the present invention applied to a blockchain system;

[0059] Figure 2 This is an exemplary system architecture of the technical solution of this application in an application scenario;

[0060] Figure 3This is a schematic flow chart of a blockchain-based equity certificate management method in an embodiment of the present application;

[0061] Figure 4 This is a schematic structural diagram of a block in a blockchain for storing equity certificates in an embodiment of the present application;

[0062] Figure 5 This is a schematic diagram of the overall process of the equity certificate management method in the embodiment of this application;

[0063] Figure 6 This is a schematic flow chart of the equity certificate management method in one embodiment of the present application.

[0064] Figure 7 The following schematically shows a block diagram of a blockchain-based equity certificate management device in an embodiment of the present application;

[0065] Figure 8 A schematic diagram of the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

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

[0067] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner.In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, it will be appreciated by those skilled in the art that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps etc. can be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0068] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0069] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0070] It should be understood that the solution of this application can be applied to the management of digital collectibles and other equity certificates, and specifically to scenarios where the ownership of digital collectibles and virtual assets is tied to their owners when they are issued or minted. In such scenarios, digital collectibles or virtual assets are typically directly associated with their original recipients, such as qualifications or honorary awards issued to specific users or accounts. Ownership of such virtual assets belongs solely to the user who originally obtained the corresponding qualifications or awards. Therefore, such virtual assets are directly tied to the user or the account held by the user. It is understandable that a key difference between such virtual assets and digital collectibles such as images or audio is that they cannot or should not be traded to other users. In the solution of this application, such virtual assets are directly tied to their owners, allowing the relevant ownership relationship to be directly incorporated into the virtual asset's information. This eliminates the need to maintain additional management information for these non-tradable virtual assets in the blockchain or related information storage database, facilitating the ownership management of such non-tradable virtual assets.

[0071] The solution of this application can be applied in blockchain systems, and more specifically in consortium blockchain systems that implement smart contracts. A blockchain system can be a distributed system formed by connecting clients and multiple nodes (any type of computing device connected to the network, such as servers and user terminals) through network communication.

[0072] Taking the distributed system as the blockchain system as an example, see Figure 1 , Figure 1 This is an optional structural diagram of the equity certificate management system provided by an embodiment of the present invention applied to a blockchain system. The blockchain system of this embodiment of the application includes two blockchains: an identity contract blockchain 100 and an equity certificate blockchain 110. Each blockchain is composed of multiple nodes (any form of computing device connected to the network, such as servers and user terminals) and clients, forming a peer-to-peer (P2P) network between the nodes. In the equity certificate management system, any machine, such as a server or terminal, can join and become a node. A node includes a hardware layer, an intermediate layer, an operating system layer, and an application layer.

[0073] See also Figure 1 The functions of each node in the two blockchains shown in Figure 1 mainly involve:

[0074] Routing is a basic function of a node, used to support communication between nodes.

[0075] Identity contracts are deployed in some nodes of the identity contract blockchain 100. The identity contract is a smart contract, specifically a computerized protocol that can execute terms for account management. It is implemented through code deployed on the blockchain for execution when certain conditions are met. It completes account management functions based on actual account scenarios, such as generating new accounts, querying account information and account addresses, and performing account verification.

[0076] A stake certificate contract is deployed in some nodes of the stake certificate blockchain 110. The stake certificate contract is also a smart contract that is used to manage stake certificates, such as the minting, transfer, and ownership verification of stake certificates.

[0077] In the identity contract blockchain 100 and the equity certificate blockchain 110, each block includes the hash value of the transaction records stored in the block (the current block's hash value) and the hash value of the previous block. Blocks are connected by hash values ​​to form a blockchain. Blocks can also include transaction information used to record information, such as transactions to create new accounts or mint new equity certificates.

[0078] See also Figure 2 , Figure 2 This is an exemplary system architecture of the technical solution of this application in an application scenario. Figure 2As shown, the system architecture includes a terminal device 210, an identity server 220, an image server 230, a stake certificate server 240, an identity contract server 250, and a stake certificate contract server 260. The terminal device 210 is installed with an application for accessing and managing stake certificates. The terminal user accesses each server through the terminal device 210 to complete the stake certificate management process, including creation and transfer. Specifically, the terminal device 210 communicates with the identity server 220 to complete user registration, and the identity server 220 sends the user's registration information to the identity contract server 250 for on-chain storage. The terminal device 210 also uses the identity server 220 to retrieve or create new stake certificates. The identity server 220 verifies locally or through an external certificate that the user has appropriate permissions for the stake certificate, and then communicates with the image server 230 to generate the corresponding stake certificate content and obtain the actual storage address of the stake certificate. Subsequently, identity server 220 communicates with equity certificate server 240 to create an equity certificate. Equity certificate server 240, through equity certificate contract server 260, creates a corresponding equity certificate on the blockchain and feeds back the result to terminal device 210. Terminal device 210 will subsequently trade the equity certificate through equity certificate server 240. Equity certificate server 240, through equity certificate contract server 260, verifies whether the equity certificate can be traded and feeds back the transaction result or verification result to terminal device 210. The above-mentioned server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms, but this is not limited here. Each of the above-mentioned servers can actually be deployed on the same physical server, and the functions of each server constitute the functional modules of the management system. Terminal devices include, but are not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, etc. Terminal devices and servers may be connected directly or indirectly via wired or wireless communication, and this application does not impose any restrictions thereon. There is also no limit on the number of terminal devices and servers.

[0079] The solution of the present application can be applied in the process of managing ownership of equity certificates by the equity certificate management server. The technical solution provided by the present application is described in detail below in conjunction with specific implementation methods.

[0080] In the specific implementation of this application, user information, transaction data and other related data are involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent must be obtained, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0081] For ease of introduction, see Figure 3 , Figure 3 This is a schematic flow chart of a blockchain-based equity certificate management method in an embodiment of the present application. This method can be applied to the aforementioned equity certificate server. In this embodiment of the present application, the blockchain-based equity certificate management method is described using the equity certificate management device running on the server as the execution entity. The method may include the following steps S310 to S330:

[0082] Step S310: Receive a request for minting a stake certificate, where the request carries an account address in the blockchain and stake data of the stake certificate to be minted.

[0083] In this embodiment, the equity certificate management device receives an equity certificate minting request from a client. This equity certificate minting request is used to mint a new equity certificate in the equity certificate blockchain. Equity certificates are essentially unique, trusted digital equity certificates within a blockchain network. They are data objects that can record and process multi-dimensional, complex attributes on the blockchain. The equity certificate minting request carries an account address in the blockchain and the equity data of the equity certificate to be minted. The account address uniquely identifies a specific account in the blockchain used to store equity certificates, and can be, for example, a decentralized identifier generated by the blockchain. The account address can be generated based on a blockchain, but the blockchain used to generate the account address can be different from the blockchain used to store the equity certificates. That is, a separate account address blockchain is used to generate a corresponding account address for each account, allowing for easy use in the equity certificate blockchain used to store the equity certificates. The account address is the account address of the account in the equity certificate management system that initiated the equity certificate minting request. The information of these accounts can be managed in a blockchain format. Equity data refers to the physical content or storage address of the virtual asset or digital collectible stored in the equity certificate, such as an image of a certificate, medal, or authorization certificate. The storage address of equity data is typically a link address in a resource location system. Through this link address, you can access the content protected by the equity certificate, such as pictures or audio.

[0084] Step S320: Generate certificate metadata according to the equity certificate casting request, wherein the certificate metadata includes the account address and the equity data.

[0085] In this embodiment, the equity certificate management device generates certificate metadata based on the equity certificate minting request. The certificate metadata includes the account address and equity data. Certificate metadata is a data structure within the equity certificate used to store the equity certificate data content. Metadata typically includes various attributes of the equity certificate, such as the version number, the name of the equity certificate, the thumbnail address of the equity data, the original image address, and the certificate number. In this embodiment of the application, the certificate metadata of the equity certificate includes the account address of the requesting account.

[0086] Taking the equity certificate of the certificate image as an example, the example of the certificate metadata in this application is as follows:

[0087]

[0088] The credential metadata metaData contains metadata attributes, namely the version number version, name name, account address soul_owner, description description, and thumbnails for sharing posters and other pages. The credential metadata metaData also contains properties of the equity certificate content, such as the resource address resource_uri, equity certificate number seq_number, the total number of equity certificates issued issue_total_num, and corresponding element attributes.

[0089] It is understandable that for equity certificates that are not bound to an account, the account address soul_owner field is usually not included in the certificate metadata, and its ownership information is determined by the information in the corresponding block in the blockchain.

[0090] Step S330: Create a stake certificate minting transaction based on the certificate metadata to mint a stake certificate associated with the account address in the blockchain, wherein the stake certificate contains the certificate metadata, and the account address in the certificate metadata is used to indicate that the stake certificate is bound to the account address.

[0091] The equity certificate management device creates an equity certificate minting transaction based on the certificate metadata. The equity certificate minting transaction includes the previously generated certificate metadata. This equity certificate minting transaction is submitted to the blockchain storing the equity certificates. A smart contract within the blockchain packages the equity certificate minting transaction and mints the equity certificate associated with the account address. Therefore, the minted equity certificate on the blockchain includes the certificate metadata. The account address included in the certificate metadata indicates the binding relationship between the minted equity certificate and the corresponding account address. This binding relationship is a strong identity binding between the equity certificate and the account address, and it cannot be modified. Therefore, the bound equity certificate cannot be transferred to other accounts. Since equity certificates cannot be modified after minting on the blockchain, the minted equity certificate is fixedly owned by the account address. This ensures that the ownership information of the equity certificate is included in the equity certificate package itself. When the ownership of the equity certificate is required, the ownership information can be obtained directly from the equity certificate itself, without the need to query the blockchain or related databases for the ownership information.

[0092] In an embodiment of the present application, in the process of minting equity certificates, the account address in the blockchain is added as an identifier in the certificate metadata of the equity certificate, the equity certificate is bound to the account address, and the owner information is directly added to the equity certificate, so that the equity certificate can be directly managed without relying on the transaction information of the blockchain, thereby improving the level of refinement of equity certificate management, and helping to reduce management difficulty and improve management efficiency.

[0093] In one embodiment of the present application, based on the above technical solution, the equity certificate minting request also carries the account identifier of the requesting account in the blockchain; after receiving the equity certificate minting request in step S310, the method of the present application further includes the following steps:

[0094] Obtaining account information of the requesting account according to the account identifier of the requesting account;

[0095] Perform encryption calculation based on the account information and the equity data to generate a token identifier;

[0096] The above step S330, creating a stake certificate minting transaction based on the certificate metadata, specifically includes the following steps:

[0097] Creating a stake certificate minting transaction based on the token identifier and the certificate metadata, wherein the stake certificate minting transaction includes a correspondence between the token identifier and the certificate metadata.

[0098] In this embodiment, upon receiving a request to mint a staked ...

[0099] In an embodiment of the present application, when creating a stake certificate casting transaction, a token identifier generated outside the blockchain is used as the identifier of the stake certificate, which is conducive to improving the controllability of the stake certificate management process.

[0100] In one embodiment of the present application, based on the above technical solution, after the above step S230, in which the equity certificate minting transaction is created according to the certificate metadata, the method of the present application further includes the following steps:

[0101] Receive a credential verification request, wherein the credential verification request includes a token identifier of a stake certificate to be verified;

[0102] Acquire the credential metadata of the equity credential to be verified according to the token identifier of the equity credential to be verified;

[0103] Generate ownership verification information of the equity certificate to be verified according to the account address in the certificate metadata of the equity certificate to be verified.

[0104] In this embodiment, upon receiving a verification request for a stake certificate, the stake certificate management device directly verifies ownership based on the account address stored in the stake certificate's metadata. Specifically, a client can initiate a certificate verification request for a stake certificate if it possesses appropriate permissions. For example, if the permission certificate is a certificate, the user with the certificate can present it to other accounts through their account, and the account that receives the certificate can then initiate a verification request for the certificate. The certificate verification request is sent to the stake certificate management device. The stake certificate management device then receives the certificate verification request from the client, which includes the token identifier of the stake certificate to be verified. Based on this token identifier, the stake certificate management device retrieves the stake certificate to be verified from the blockchain where the stake certificate is stored. Subsequently, the stake certificate to be verified is parsed using the stake certificate's contract interface to obtain the stake certificate's metadata. The account address to which the stake certificate belongs can be read from the attribute corresponding to the account address in the certificate metadata. Based on this account address, the stake certificate's ownership can be verified, thereby obtaining ownership verification information for the stake certificate. The attribution verification information typically includes the attribution verification results or information used for further verification, such as the account address in the credential metadata. Attribution verification is typically determined by comparing the account address in the credential metadata with the account address of the account claiming to own the equity certificate. Specifically, for example, when the equity certificate management device receives a credential verification request, it may also receive the account information of the party presenting the equity certificate. After obtaining the account address to which the equity certificate belongs, the device then queries the corresponding account address based on the received account information and determines the attribution verification result based on whether the two match. Alternatively, the equity certificate management device may directly provide the account address to the client, which then initiates a query request to the blockchain managing the account to verify whether the account address matches the account requesting the transaction. In one embodiment, the credential verification request may also be initiated by the account owning the equity certificate. After obtaining the credential metadata, the device can directly determine the attribution verification result based on whether the account address in the credential metadata matches the account address of the verification requester, thereby generating attribution verification information for the equity certificate to be verified.

[0105] See also Figure 4 , Figure 4 This is a schematic structural diagram of a block in the blockchain used to store equity certificates in an embodiment of the present application. Figure 4 As shown in the figure, a block contains n minting transactions, each of which contains a key-value pair corresponding to the token identifier and account address, as well as a key-value pair corresponding to the token identifier and credential metadata.

[0106] In an embodiment of the present application, when it is necessary to verify the ownership information of a stake certificate, the account address to which it belongs is directly obtained from the metadata of the stake certificate, so that when performing the ownership verification, the verification process can be completed only through the metadata of the stake certificate without the need for an additional information query process, thereby simplifying the verification process and improving verification efficiency.

[0107] In one embodiment of the present application, based on the above technical solution, after the above step S230, in which the equity certificate minting transaction is created according to the certificate metadata, the method of the present application further includes the following steps:

[0108] receiving a request for transferring an equity certificate, wherein the request includes a token identifier of a target equity certificate;

[0109] Obtaining the certificate metadata corresponding to the target equity certificate according to the token identifier in the equity certificate transfer request;

[0110] If the certificate metadata of the target equity certificate contains an account address, a certificate transfer failure message is generated to indicate that the transfer of the target equity certificate has failed.

[0111] In this embodiment, when a client requests a transaction for a stake certificate, the stake certificate management device verifies whether there is a binding relationship between the stake certificate and the account address, and rejects the transaction request for a stake certificate that is already bound. Specifically, a client can initiate a stake certificate transfer request for a stake certificate it owns. This stake certificate transfer request is typically used to transfer ownership of the stake certificate to another account. It is understood that an account can have multiple stake certificates, some of which are bound to the account, such as honor certificates or skill qualification certificates, while others are not, such as assets such as images or multimedia resources. The stake certificate transfer request initiated by the client will include the token identifier of the target stake certificate. Upon receiving the stake certificate transfer request, the stake certificate management device retrieves the stake certificate metadata corresponding to the target stake certificate from the blockchain based on the token identifier. The stake certificate management device then parses the stake certificate metadata using the corresponding protocol's parsing interface to obtain the attributes and corresponding attribute values ​​contained in the stake certificate metadata. For the parsed result, the equity certificate management device can verify whether there is a binding relationship with the equity certificate based on the attribute of whether the account address is stored therein. If the account address is included in the certificate metadata, it means that the equity certificate is bound to the account address contained therein, that is, the equity certificate is data or information that is only valid for the account address and cannot be traded, such as a qualification certificate. The equity certificate management device will stop processing the equity certificate transfer request and generate a certificate transfer failure message. The certificate transfer failure message will be sent to the client requesting the transfer to indicate that the transfer of the target equity certificate has failed. It can be understood that if the account address is not included in the certificate metadata, it means that the equity certificate is an asset that can be traded. The equity certificate management device will then call the corresponding smart contract to generate a transaction for transferring the ownership of the equity certificate, thereby completing the transaction process and notifying the client of the transaction results.

[0112] In an embodiment of the present application, when processing a request to transfer an equity certificate, whether the equity certificate can be traded is directly determined based on the account address in the equity certificate metadata, which is conducive to simplifying the verification process in the equity certificate transfer and improving the execution efficiency of the transfer process.

[0113] In one embodiment of the present application, based on the above technical solution, step S230, obtaining the voucher metadata corresponding to the target equity voucher according to the token identifier in the equity voucher transfer request, specifically includes the following steps:

[0114] Creating an equity certificate transfer transaction according to the received equity certificate transfer request, wherein the equity certificate transfer transaction includes the token identifier in the equity certificate transfer request;

[0115] The equity certificate transfer transaction is uploaded to the blockchain, so that the blockchain parses the target equity certificate corresponding to the token identifier according to the equity certificate contract and feeds back the certificate metadata of the target equity certificate;

[0116] Credential metadata of the target equity certificate is received.

[0117] In this embodiment, when processing a certificate transfer request, the transfer transaction is first uploaded to the blockchain, and then the certificate is parsed through a smart contract within the blockchain. Specifically, the certificate management device first creates a certificate transfer transaction upon receiving the certificate transfer request. This transaction includes the token identifier from the certificate transfer request. The certificate management device then uploads the transaction to the blockchain used to store the certificate. Specifically, the certificate management device invokes the smart contract that manages the certificate to upload the generated certificate transfer transaction. During the upload process, the blockchain's computing device uses the token identifier in the certificate's smart contract to query the blockchain for the corresponding target certificate. The smart contract then parses the target certificate through an interface within the smart contract to obtain the certificate metadata. The blockchain then feeds the certificate metadata back to the certificate management device, which then uses the metadata to determine whether the transaction or transfer can proceed.

[0118] It is understood that in one embodiment, the blockchain can directly parse the certificate metadata of the equity certificate through a smart contract, confirm whether the account address attribute exists therein, and directly feedback the transaction result to the equity certificate management device. If it does exist, the transaction fails to be uploaded to the chain, and a transaction failure result is directly fed back.

[0119] In an embodiment of the present application, when conducting an equity certificate transaction, the transfer transaction of the equity certificate is uploaded to the blockchain to trigger the blockchain to parse the certificate metadata, so that the parsing calculation process is executed through the resources of the blockchain, thereby reducing the computing consumption of the computing equipment of the equity certificate processing device, distributing the computing load, avoiding centralized processing and resulting in resource bottlenecks, and improving the reliability of the solution.

[0120] In one embodiment of the present application, based on the above technical solution, before receiving the equity certificate minting request in step S310, the method of the present application further includes the following steps:

[0121] receiving a request for generating equity data, wherein the request carries an account identifier of the requesting account corresponding to the account address;

[0122] According to the account identifier, obtaining the account information of the requesting account and the certificate information of the certificate obtained by the requesting account;

[0123] generating the equity data according to the account information and the certificate information;

[0124] Feedback the storage address of the equity data to the client.

[0125] In this embodiment, a stake certificate is a certificate that an account wishes to receive, such as a qualification certificate or honorary certificate. In response to triggering the certificate redemption function, the client generates a stake data generation request. The stake certificate generation request carries the account identifier of the requesting account corresponding to the account address. Based on the account identifier, the stake certificate management device retrieves the corresponding account information and certificate information from the blockchain that stores the account information, allowing the account to obtain the certificate. This certificate information is typically an image of the certificate itself or a link to the image. The stake certificate management device then generates stake data based on the account information and certificate information. The method for generating stake data varies depending on the specific type of stake data. For example, for certificate-related stake data, the stake data generation process typically involves merging account information and certificate-related information into a base certificate image. For medal-related stake data, however, information such as the medal model corresponding to the account information may need to be uploaded from a specific image storage address. After generating the stake data, the stake certificate management device provides the client with the storage address of the stake data, allowing the client to initiate a stake certificate creation request based on the stake data.

[0126] In one embodiment of the present application, based on the above technical solution, the above steps of obtaining the account information of the requesting account and the certificate information of the certificate obtained by the requesting account according to the account identifier specifically include the following steps:

[0127] Obtaining, from the blockchain, account information of the requesting account according to the account identifier;

[0128] Verifying, based on the account information, the requesting account's authority to obtain the certificate corresponding to the certificate information;

[0129] If the verification is successful, the account information is sent to the certificate authentication service, so that the certificate authentication service can feedback the corresponding certificate number according to the account information;

[0130] The certificate number sent by the certificate authentication service is received as the certificate information.

[0131] In this embodiment, the certificate information is the certificate number, and the equity certificate management device obtains the certificate information through an external service. Specifically, the equity certificate management device first obtains the account information of the requesting account from the blockchain based on the account identifier. This account information typically includes the identity information of the account owner. Subsequently, based on the obtained account information, the equity certificate management device verifies whether the requesting account has access to the certificate corresponding to the certificate information. This verification process can be performed by an external verification service, for example, by sending the identity information of the requesting account to the certificate issuer's verification server and determining whether the account has access to the certificate based on the verification server's feedback. Alternatively, the equity certificate management device can pre-store or obtain from the certificate issuer a list of identities or accounts with access to the certificate, and perform a comparison against the list of identities or accounts during verification. After successful verification, the equity certificate management device sends the account information to a certificate authentication service. The certificate authentication service is a service provided by the certificate issuer or other third party with the ability or authority to issue certificates. This service generates a corresponding certificate number and further certificate-related information for accounts eligible to obtain the certificate, such as the coordinates of the new image to be added to the certificate image. The certificate authentication service will feedback the corresponding account number based on the received account information. The equity certificate management device will receive and save the corresponding certificate number and further feedback it to the client for the subsequent equity certificate minting process.

[0132] In one embodiment of the present application, based on the above technical solution, the rights and interests data is a certificate image; the above steps of generating the rights and interests data based on the account information and the certificate information specifically include the following steps:

[0133] Receive a certificate image generation request, wherein the certificate image generation request includes the account information, the certificate number, the certificate base map, and location coordinate information;

[0134] According to the location coordinate information, the account information and the certificate number are superimposed on the certificate base map to generate the certificate image.

[0135] In an embodiment of the present application, the equity data is an image of a certificate, and the certificate image is obtained by superimposing the relevant information of the certificate recipient and the information of the certificate itself on a base map. Specifically, when the equity certificate management device receives a certificate image generation request from the client, the request will include the account information of the certificate recipient, the certificate number, the certificate base map, and the location coordinate information. The certificate base map and the location coordinate information can be information obtained together when obtaining the certificate information, or information pre-stored in the requesting client. A service for synthesizing certificate images can be deployed in the equity certificate management device. In one embodiment, the service can read the certificate base map of the corresponding certificate based on information such as the certificate number. The location coordinate information will include the coordinate positions of each piece of information that needs to be added in the certificate image. The equity certificate management device then superimposes the account information and the certificate number on the certificate base map according to the indicated position based on the location coordinate information, thereby generating a certificate image.

[0136] In the embodiment of the present application, the certificate image is directly generated online without uploading the image externally, thereby simplifying the process of obtaining certificate information and improving the efficiency of generating rights data.

[0137] In one embodiment of the present application, based on the above technical solution, after the above step S330, in which the equity certificate minting transaction is created according to the certificate metadata, the method of the present application further includes the following steps:

[0138] Uploading the equity certificate minting transaction to the blockchain;

[0139] Feedback a minting response message of the equity certificate to the client, so that the client displays the equity certificate.

[0140] In this embodiment, after creating a stake certificate minting transaction, the stake certificate management device will upload the stake certificate minting transaction to the blockchain. Specifically, the stake certificate minting transaction is uploaded to the blockchain and submitted to the blockchain for packaging. When the blockchain is packaged into blocks, the minting transaction is packaged into blocks according to the smart contract. It is understood that a block can contain multiple transactions, each corresponding to a stake certificate. After the upload is completed, the stake certificate management device will feedback a stake certificate minting response message to the client. This minting response message will include the minted stake certificate, the access address of the stake certificate, or the specific content of the stake data in the stake certificate, such as a certificate image. The minting response message enables the client to display the received stake certificate to the user.

[0141] In one embodiment of the present application, based on the above technical solution, before receiving the equity certificate minting request in step S310, the method further includes:

[0142] receiving an account registration request, wherein the account registration request includes account information;

[0143] Generating a requesting account in the blockchain according to the account information;

[0144] Feedback the account address of the requesting account in the blockchain.

[0145] In this embodiment, the client can first register on the blockchain to obtain a corresponding account address. Specifically, the equity certificate management device receives an account registration request from the client, which includes account information. This account registration request typically includes the user's user information and relevant qualifications. Subsequently, the equity certificate management device generates a requesting account on the blockchain based on the account information in the registration request. Specifically, the requesting account can be generated by submitting a corresponding transaction to the blockchain based on the account information. The smart contract on the blockchain then packages the account information and generates the corresponding account address. The equity certificate management device then feeds the account address of the requesting account on the blockchain back to the corresponding client for use in the subsequent equity certificate minting and transfer process.

[0146] The following is an introduction to the complete embodiment of the equity certificate management method in this application. Figure 5 , Figure 5 This is a schematic diagram of the overall process of the equity certificate management method in the embodiment of this application. Figure 5 As shown,

[0147] In step 501, the equity certificate management device receives a request from a client to generate equity data. This request carries the account identifier of the requesting account. In step 502, the account information of the requesting account is retrieved from the blockchain based on the account identifier. In step 503, the requesting account's access rights to the certificate corresponding to the certificate information are verified based on the account information. If verification is successful, in step 504, the account information is sent to the certificate authentication service, which responds with the corresponding certificate number based on the account information. Subsequently, in step 505, the certificate number sent by the certificate authentication service is received as the certificate information. After obtaining the certificate number, in step 506, a certificate image generation request is received from the client. This certificate image generation request contains the account information, the certificate number, a certificate base image, and location coordinate information. In step 507, the account information and certificate number are superimposed on the certificate base image based on the location coordinate information to generate a certificate image. Subsequently, in step 508, the storage address of the equity data is fed back to the client. In step 509, a request for minting a stake certificate is received from a client. The request carries the account address of the requesting account in the blockchain, the equity data of the stake certificate to be minted, and the account identifier of the requesting account. Subsequently, in step 510, the account information of the requesting account is obtained based on the account identifier of the requesting account. In step 511, a cryptographic calculation is performed based on the account information and the equity data to generate a token identifier. Subsequently, in step 512, credential metadata is generated based on the stake certificate minting request, wherein the credential metadata includes the account address and the equity data. In step 513, the credential management device creates a stake certificate minting transaction based on the token identifier and the credential metadata to mint a stake certificate associated with the account address in the blockchain. The stake certificate minting transaction includes a correspondence between the token identifier and the credential metadata. The stake certificate contains the credential metadata, and the account address in the credential metadata is used to indicate that the stake certificate is bound to the requesting account. Then, in the subsequent use of the equity certificate, the equity certificate management device will receive a certificate verification request in step 514, which includes the token identifier of the equity certificate to be verified, and obtain the certificate metadata of the equity certificate to be verified based on the token identifier of the equity certificate to be verified in step 515; then, in step 516, the ownership verification information of the equity certificate to be verified is generated based on the account address in the certificate metadata of the equity certificate to be verified.In addition, the equity certificate management device also receives an equity certificate transfer request in step 517, which includes the token identifier of the target equity certificate. In step 518, based on the received equity certificate transfer request, the equity certificate transfer transaction is created, which includes the token identifier in the equity certificate transfer request. Subsequently, in step 519, the equity certificate transfer transaction is uploaded to the blockchain, so that the blockchain, based on the equity certificate contract, resolves the target equity certificate corresponding to the token identifier and returns the certificate metadata of the target equity certificate. In step 520, the equity certificate management device receives the certificate metadata of the target equity certificate and checks the certificate metadata. In step 521, if the certificate metadata of the target equity certificate includes an account address, a certificate transfer failure message is generated to indicate that the transfer of the target equity certificate has failed.

[0148] The following is an overall introduction to the equity certificate management method of this application in conjunction with specific embodiments. Figure 6 , Figure 6 This is a schematic flow chart of the equity certificate management method in one embodiment of the present application. Figure 6As shown, in this solution, the client is a blockchain mini-program, while the equity certificate management device specifically includes multiple services, each dedicated to a single function. Specifically, the user first registers with their real name on the blockchain mini-program. The decentralized service verifies the user's real name and, upon successful verification, returns the user's decentralized identifier. The user then clicks an activity icon or interactive area on the blockchain mini-program to claim the corresponding certificate-related collection. The blockchain mini-program queries the decentralized identity service to obtain the user's relevant identity information and check whether the user can obtain the certificate. If the user can obtain the certificate, the decentralized identity service calls an external certificate certification authority to obtain the user's certificate number based on the account's identity information. Finally, the decentralized identity service returns the user's identity information and the corresponding certificate number to the blockchain mini-program. The blockchain mini-program generates a link to the user's electronic certificate storage in real time by sending an overlay request to the overlay service. The overlay request includes the certificate overlay base image, the obtained identity information, the certificate number, and the overlay coordinates. After the overlay service completes the certificate overlay, it returns a link to the user's certificate storage to the blockchain mini-program. The blockchain mini-program creates a link to the certificate storage, creating a token minting request, and sends it to the backend token service. The token service first queries the user's information, generates a token identifier based on the token information, and obtains the user's corresponding on-chain address. The token service determines whether the token is strongly bound to the user's identity. Based on this determination, it generates metadata for the token. Finally, based on this metadata, it creates an on-chain minting transaction for the token collection (calling the create function of the token contract) and submits this transaction to the blockchain token contract for real-time minting. The minting is directly to the user's account address, which matches the content of the account address field in the metadata. The token returns the minting result of the token collection to the blockchain mini-program, and the token for the relevant certificate is displayed on the blockchain mini-program frontend, completing the real-time minting of the collection. Subsequently, when a user attempts to transfer a strongly bound token, the on-chain verification function verifies whether the account address field exists in the token metadata. If so, an error message is generated and the token cannot be transferred, effectively preventing the on-chain transfer of strongly bound tokens. Based on the corresponding interface of the smart contract, the on-chain metadata corresponding to the token identifier can be queried by passing in the token identifier parameter, thereby realizing the on-chain ownership verification of the equity certificate with strong identity binding to the user, thereby realizing the functions of various certificate certification scenarios.

[0149] It should be noted that although the steps of the method of the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all steps must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0150] The following introduces the device implementation of the present application, which can be used to execute the blockchain-based equity certificate management method in the above-mentioned embodiment of the present application. Figure 7 The block diagram of the block diagram of the equity certificate management device based on blockchain in the embodiment of the present application is schematically shown. Figure 7 As shown, the blockchain-based equity certificate management device 700 mainly includes:

[0151] A minting request receiving module 710 is configured to receive a minting request for an equity certificate, wherein the minting request carries an account address in the blockchain and equity data of the equity certificate to be minted;

[0152] A metadata generation module 720 is configured to generate certificate metadata according to the equity certificate casting request, wherein the certificate metadata includes the account address and the equity data;

[0153] The minting transaction creation module 730 is used to create a stake certificate minting transaction based on the certificate metadata to mint a stake certificate associated with the account address in the blockchain, wherein the stake certificate contains the certificate metadata, and the account address in the certificate metadata is used to indicate that the stake certificate is bound to the account address.

[0154] In some embodiments of the present application, based on the above technical solution, the equity certificate minting request also carries the account identifier of the requesting account corresponding to the account address; the equity certificate management device further includes:

[0155] An account information acquisition module, configured to acquire the account information of the requesting account according to the account identifier of the requesting account;

[0156] An encryption calculation module, configured to perform encryption calculation based on the account information and the equity data to generate a token identifier;

[0157] The minting transaction creation module includes:

[0158] A transaction creation unit is configured to create a stake certificate casting transaction based on the token identifier and the certificate metadata, wherein the stake certificate casting transaction includes a correspondence between the token identifier and the certificate metadata.

[0159] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0160] A verification request receiving module, configured to receive a credential verification request, wherein the credential verification request includes a token identifier of the equity credential to be verified;

[0161] A first metadata acquisition module, configured to acquire the credential metadata of the equity credential to be verified according to the token identifier of the equity credential to be verified;

[0162] The verification information generation module is used to generate the ownership verification information of the equity certificate to be verified according to the account address in the certificate metadata of the equity certificate to be verified.

[0163] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0164] A transfer request receiving module, configured to receive a request for transferring an equity certificate, wherein the request contains a token identifier of a target equity certificate;

[0165] A second metadata acquisition module, configured to acquire the certificate metadata corresponding to the target equity certificate according to the token identifier in the equity certificate transfer request;

[0166] The failure message generation module is configured to generate a certificate transfer failure message if the certificate metadata of the target equity certificate contains an account address, so as to indicate that the transfer of the target equity certificate has failed.

[0167] In some embodiments of the present application, based on the above technical solution, the second metadata acquisition module includes:

[0168] a transfer transaction creating unit, configured to create an equity certificate transfer transaction according to the received equity certificate transfer request, wherein the equity certificate transfer transaction includes the token identifier in the equity certificate transfer request;

[0169] An on-chain unit, configured to upload the equity certificate transfer transaction to the blockchain, so that the blockchain parses the target equity certificate corresponding to the token identifier according to the equity certificate contract and feeds back the certificate metadata of the target equity certificate;

[0170] The metadata receiving unit is configured to receive the certificate metadata of the target equity certificate.

[0171] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0172] a generation request receiving module, configured to receive a request for generating equity data, wherein the request carries an account identifier of the requesting account corresponding to the account address;

[0173] a certificate information acquisition module, configured to acquire, based on the account identifier, the account information of the requesting account and the certificate information of the certificate obtained by the requesting account;

[0174] A rights and interests data generation module, configured to generate the rights and interests data according to the account information and the certificate information;

[0175] The storage address feedback module is used to feedback the storage address of the equity data to the client.

[0176] In some embodiments of the present application, based on the above technical solution, the certificate information acquisition module includes:

[0177] an account information obtaining unit, configured to obtain the account information of the requesting account from the blockchain according to the account identifier;

[0178] an authority verification unit, configured to verify, based on the account information, the permission of the requesting account to obtain the certificate corresponding to the certificate information;

[0179] An account information sending unit, configured to send the account information to the certificate authentication service if the verification is successful, so that the certificate authentication service feeds back a corresponding certificate number based on the account information;

[0180] The certificate number receiving unit is configured to receive the certificate number sent by the certificate authentication service as the certificate information.

[0181] In some embodiments of the present application, based on the above technical solution, the rights and interests data is a certificate image; and the rights and interests data generation module includes:

[0182] An image generation request receiving unit, configured to receive a certificate image generation request, wherein the certificate image generation request includes the account information, the certificate number, the certificate base map, and location coordinate information;

[0183] The certificate image generating unit is configured to superimpose the account information and the certificate number onto the certificate base map according to the location coordinate information to generate the certificate image.

[0184] In some embodiments of the present application, based on the above technical solution, after creating the equity certificate minting transaction according to the certificate metadata, the equity certificate management device further includes:

[0185] A minting transaction on-chain module, used to put the equity certificate minting transaction on-chain in the blockchain;

[0186] The response feedback module is used to feed back a minting response message of the equity certificate to the client, so that the client can display the equity certificate.

[0187] In some embodiments of the present application, based on the above technical solution, the equity certificate management device further includes:

[0188] A registration request receiving module, configured to receive an account registration request, wherein the account registration request includes account information;

[0189] A requesting account generating module, configured to generate a requesting account in the blockchain according to the account information;

[0190] The account address feedback module is used to feedback the account address of the requesting account in the blockchain.

[0191] It should be noted that the apparatus provided in the above embodiment and the method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module performs the operation has been described in detail in the method embodiment and will not be repeated here.

[0192] Figure 8 A schematic diagram of the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application is shown.

[0193] It should be noted that Figure 8 The computer system 800 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0194] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 802 or the program loaded from the storage part 808 to the random access memory (RAM) 803. Various programs and data required for system operation are also stored in the RAM 803. The CPU 801, ROM 802 and RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0195] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, and the like; an output section 807 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. Removable media 811, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 810 as needed, so that computer programs read therefrom can be installed into the storage section 808 as needed.

[0196] In particular, according to an embodiment of the present application, the processes described in the various method flow charts can be implemented as computer software programs. For example, an embodiment of the present application includes a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 809, and / or installed from a removable medium 811. When the computer program is executed by the central processing unit (CPU) 801, the various functions defined in the system of the present application are executed.

[0197] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0198] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the above-mentioned module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of the boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0199] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the application, the features and functions of two or more modules or units described above can be concretized in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0200] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

[0201] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

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

Claims

1. A blockchain-based equity certificate management method, characterized in that: include: Receive a request for minting a stake certificate, the request carrying an account address in the blockchain, stake data of the stake certificate to be minted, and an account identifier of the requesting account corresponding to the account address; Obtaining account information of the requesting account according to the account identifier of the requesting account; Perform encryption calculation based on the account information and the equity data to generate a token identifier; Generate certificate metadata according to the equity certificate minting request, wherein the certificate metadata includes the account address and the equity data; Creating a stake certificate minting transaction based on the certificate metadata to mint a stake certificate associated with the account address in the blockchain, wherein the stake certificate contains the certificate metadata, and the account address in the certificate metadata is used to indicate that the stake certificate is bound to the account address; The step of creating a stake certificate minting transaction based on the certificate metadata includes: Creating a stake certificate minting transaction based on the token identifier and the certificate metadata, wherein the stake certificate minting transaction includes a correspondence between the token identifier and the certificate metadata.

2. The method according to claim 1, characterized in that After creating the equity certificate minting transaction according to the certificate metadata, the method further includes: Receive a credential verification request, wherein the credential verification request includes a token identifier of a stake certificate to be verified; Acquire the credential metadata of the equity credential to be verified according to the token identifier of the equity credential to be verified; Generate ownership verification information of the equity certificate to be verified according to the account address in the certificate metadata of the equity certificate to be verified.

3. The method according to claim 1, characterized in that After creating the equity certificate minting transaction according to the certificate metadata, the method further includes: receiving a request for transferring an equity certificate, wherein the request includes a token identifier of a target equity certificate; Obtaining the certificate metadata corresponding to the target equity certificate according to the token identifier in the equity certificate transfer request; If the certificate metadata of the target equity certificate contains an account address, a certificate transfer failure message is generated to indicate that the transfer of the target equity certificate has failed.

4. The method according to claim 3, characterized in that The acquiring, according to the token identifier in the equity certificate transfer request, the certificate metadata corresponding to the target equity certificate, includes: Creating an equity certificate transfer transaction according to the received equity certificate transfer request, wherein the equity certificate transfer transaction includes the token identifier in the equity certificate transfer request; The equity certificate transfer transaction is uploaded to the blockchain, so that the blockchain parses the target equity certificate corresponding to the token identifier according to the equity certificate contract and feeds back the certificate metadata of the target equity certificate; Credential metadata of the target equity certificate is received.

5. The method according to claim 1, wherein Before receiving the equity certificate minting request, the method further includes: receiving a request for generating equity data, wherein the request carries an account identifier of the requesting account corresponding to the account address; According to the account identifier, obtaining the account information of the requesting account and the certificate information of the certificate obtained by the requesting account; generating the equity data according to the account information and the certificate information; Feedback the storage address of the equity data to the client.

6. The method according to claim 5, characterized in that The acquiring, according to the account identifier, the account information of the requesting account and the certificate information of the certificate obtained by the requesting account includes: Obtaining, from the blockchain, account information of the requesting account according to the account identifier; Verifying, based on the account information, the requesting account's authority to obtain the certificate corresponding to the certificate information; If the verification is successful, the account information is sent to the certificate authentication service, so that the certificate authentication service can feedback the corresponding certificate number according to the account information; The certificate number sent by the certificate authentication service is received as the certificate information.

7. The method according to claim 6, characterized in that The rights and interests data is a certificate image; generating the rights and interests data according to the account information and the certificate information includes: Receive a certificate image generation request, wherein the certificate image generation request includes the account information, the certificate number, the certificate base map, and location coordinate information; According to the location coordinate information, the account information and the certificate number are superimposed on the certificate base map to generate the certificate image.

8. The method according to claim 1, characterized in that After creating the equity certificate minting transaction according to the certificate metadata, the method further includes: Uploading the equity certificate minting transaction to the blockchain; Feedback a minting response message of the equity certificate to the client, so that the client displays the equity certificate.

9. The method according to claim 1, characterized in that Before receiving the equity certificate minting request, the method further includes: receiving an account registration request, wherein the account registration request includes account information; Generating a requesting account in the blockchain according to the account information; Feedback the account address of the requesting account in the blockchain.

10. A blockchain-based equity certificate management device, characterized in that: include: A casting request receiving module, configured to receive a request for casting a stake certificate, wherein the request carries an account address in the blockchain, the stake data of the stake certificate to be cast, and the account identifier of the requesting account corresponding to the account address; An account information acquisition module, configured to acquire the account information of the requesting account according to the account identifier of the requesting account; An encryption calculation module, configured to perform encryption calculation based on the account information and the equity data to generate a token identifier; A metadata generation module, configured to generate certificate metadata according to the equity certificate casting request, wherein the certificate metadata includes the account address and the equity data; a minting transaction creation module, configured to create a stake certificate minting transaction based on the certificate metadata, so as to mint a stake certificate associated with the account address in the blockchain, wherein the stake certificate contains the certificate metadata, and the account address in the certificate metadata is used to indicate that the stake certificate is bound to the account address; The casting transaction creation module includes: A transaction creation unit is configured to create a stake certificate casting transaction based on the token identifier and the certificate metadata, wherein the stake certificate casting transaction includes a correspondence between the token identifier and the certificate metadata.

11. An electronic device, characterized in that: include: processor; a memory for storing executable instructions of the processor; The processor is configured to execute the blockchain-based equity certificate management method according to any one of claims 1 to 9 by executing the executable instructions.

12. A computer-readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the blockchain-based equity certificate management method as described in any one of claims 1 to 9 is implemented.

13. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the blockchain-based equity certificate management method as described in any one of claims 1 to 9.

Images