WO2020199135A1

WO2020199135A1 - Method and system for token design and token operation authorization management

Info

Publication number: WO2020199135A1
Application number: PCT/CN2019/081072
Authority: WO
Inventors: 程希冀; 蔡恒进; 王昊; 蔡天琪
Original assignee: 武汉龙津科技有限公司
Priority date: 2019-04-02
Filing date: 2019-04-02
Publication date: 2020-10-08

Abstract

A method and system for token design and token operation authorization management, comprising: first, defining the structure of a token, so as to determine authorization before a user performs various operations with respect to the token in a blockchain system; that is, determining, according to the sum of weights of respective authorized groups with corresponding authorizations and the magnitude of a configuration threshold, whether or not the user is authorized to perform operations with respect to the token. The method for authorization management is used to perform authorization classification and to form respective groups having specific authorizations, so as to flexibly control authorizations with respect to a token. The method is intrinsically flexible and extensible, and thus can address the majority of complex and diverse real-life authorization management situations.

Description

A method and system for token design and operation authority management

Technical field

The invention relates to the technical field of block chains, and in particular to a method and system for token design and operation authority management.

Background technique

With the rise of Bitcoin in recent years, blockchain technology has begun to attract people's attention, and digital currencies have risen. More and more people recognize the value of blockchain technology and begin to hold digital currencies. With everyone's understanding of blockchain technology, some people have begun to realize that blockchain can not only be used to build digital currencies, but also can build upper-level applications. Ethereum is currently doing the best in this regard.

The ensuing problem is that in order to reach a consensus, the traditional blockchain network adopts the POW method, which is a great waste of resources. Blockchain technology can be popularized on a large scale, and computing power needs to be concentrated on maintaining network operations rather than meaningless solutions. Many projects have emerged in order to solve these problems. Among them, EOS and others have solved this problem by adopting DPOS mechanism and intra-node parallelism.

However, all mainstream blockchain systems so far are a Turing-complete system built using smart contracts with Account as the center. We believe that the Tokenization of physical and virtual things is the real demand of the general public, and the Token economy will shine in the future. Although the existing mainstream systems are also launching new protocols to try to build a more suitable solution for Token operation, overall there are still the following shortcomings: users need to write their own code, the system is slow; second, it lacks a flexible rights management mechanism.

The present invention aims to design a specialized Token system, which specifically solves the problem of Token-related operations in the blockchain system, and proposes a brand-new method for the most important part of Token operation authority management.

Summary of the invention

The present invention provides a method for token design and operation authority management, which includes four main steps: domain creation, operation request, authority verification, and operation execution. The requested operation includes but is not limited to issuing tokens, transfer (or transaction) communication To authenticate and manage the created domains, all operations must pass authorization verification before they can be executed.

Preferably, for the creation of a domain (Domain), the information that needs to define the domain includes, but is not limited to, a non-repeatable domain name (Domain Name), issue threshold (Issue) threshold, transfer right (Transfer) threshold, and management right (Manage) threshold, A list of groups that can be issued for issuance rights, a list of groups that can be issued for transfer rights, and a list of groups that can be issued for management rights.

Preferably, the issuance right refers to the right to reissue or additional tokens based on the current domain, the transfer right refers to the right to change the owner of the current token, and the management right refers to the right to adjust the current domain information or structure.

Preferably, the group list is composed of one or more groups, and the information of each group includes group ID (group ID, automatically generated by the system), weight, required threshold in the group, and group members , The weight and group public key corresponding to each group member.

Preferably, the token is a unique number in the blockchain system, and it is an indivisible and smallest individual that can be issued and transferred. The ID of the Token includes the domain name and is not available under each domain name. Repeated personalized token name (Token Name).

Preferably, in the definition of the domain, each authority has a corresponding group list, and each group in the group list may not have the same weight in the authority. The weight of the group is determined by the user (individual) who owns the group private key. Or organization) and is publicly visible; at the same time, each operation has a threshold. When an operation is performed, the authorization verification process is to verify the sum of the weights of all successful issuing groups for the operation, Whether it is greater than or equal to the threshold of the operation, if it is, the operation request will be received by the system and wait for execution.

Preferably, the issuance means that each group that has the right to sign the operation request contains one or more members, and only the sum of the weights corresponding to all members in the group that has issued the operation request is added. If the threshold is greater than or equal to the required threshold in the group, the group is considered as a successful issuance group, otherwise it is a failed issuance group. At the same time, the person or organization holding the public key of the group can issue an operation to modify the members and weights in the group , That is, Group Autonomy.

The method according to claim 1, characterized in that when the issuer designs the Token type authority, it can directly quote the existing group ID to invoke the group into its authority system, because of the autonomy mechanism within the group, so Each group can be reused easily.

Preferably, Token holders have a special group whose name is fixed as Owner, which is a collection of Token holders. The special feature of this group is that each Token may be different, and the group is issued The condition is that each person in the group is issued to be valid, that is, the weight of each person in the group is equal, and the group threshold is the number of members in the group.

The present invention also provides a system for token design and operation authority management, including:

Create a domain module to generate new domains. Each domain has a unique domain name. The information that needs to define the domain includes but is not limited to non-repeatable domain name (Domain Name), issue threshold (Issue) threshold, and transfer threshold (Transfer) threshold , Management threshold, group list for issuing rights, group list for issuing transfer rights, and group list for issuing management rights;

The operation request module is used to send the operation request to the corresponding group according to the group list corresponding to the change operation request in the domain, to be issued within and between groups;

The authorization verification module is used to verify whether the sum of the weights of the successful issuance group of the operation reaches the required threshold. Only when the threshold is reached, the verification is deemed to be passed, and the operation can be executed;

The operation execution module is used to implement the operation after the verification is passed.

Preferably, each operation can charge all users or some of the users involved in the operation a fee based on consumption or established standards, which is determined by the specific implementation of the consensus mechanism.

Beneficial effect

Compared with the existing erc721 and other projects, the present invention does not require the user to write code or write smart contracts, but directly writes the interface into the system, and the user only needs to fill in the form, and the operation is simple and efficient. Currently, there is no blockchain system specifically for Token. For example, the management authority of erc721 for Token is very simple. The present invention establishes a complete set of authority management methods and systems for tokens, which greatly improves operation under the premise of ensuring safety. Efficiency, can truly realize the multi-threaded operation process.

Description of the drawings

Figure 1 depicts the specific structure of the transfer authority of a certain domain name (Domain Name) provided by the present invention.

Figure 2 describes the Token authority management structure provided by the present invention in scenario 1.

Figure 3 describes the Token authority management structure provided by the present invention in scenario 2.

Figure 4 depicts the Token authority management structure provided by the present invention in scenario 3.

Figure 5 describes the intra-group issuance process of the method described in the present invention.

Figure 6 describes the inter-group issuance process of the method described in the present invention.

detailed description

To facilitate understanding, we first introduce one of the most commonly used Transfer permissions. see picture 1.

This figure describes the transfer permission in a certain type of Token. Its threshold is 3, and there are three groups participating, namely Owner, Group A and Group B. Based on the current weight settings for each group (respectively 1, 2 and 3), Owner and Group A need to be issued jointly, or Group B can be issued separately to meet the Transfer threshold.

As far as each group is concerned, Owner only needs Alice’s public key for issuance; Group A requires at least Bob, Tony, or Tom and Tony to sign together to meet its threshold (4), and Group B needs to be signed Henry and Emma are all issued to meet the threshold (2).

The embodiments of the present invention will be described below through three scenarios, and examples of the embodiments are shown in the accompanying drawings. The embodiments described below with reference to the accompanying drawings are exemplary, and are intended to explain the present invention, but should not be construed as limiting the present invention.

Scenario 1: In real life, the holder of a Token may not be a person, but the holders. For example, the husband and wife (Alice and Bob) raise a pet dog together, and now it is necessary to obtain the consent of the husband and wife to trade this pet dog. A token is issued for this pet dog, and its structure is shown in Figure 2.

The issuer (may be Alice or Bob) sets the Token holder to be held by Alice and Bob. In the authority management part, because no additional changes and requirements are involved, the issuer sets the authority of both Issue and Manage to be empty, so that this type of Token will no longer be able to issue or modify the authority management structure (no group has authority ). In the transfer permission (the number in parentheses after the permission represents the threshold, the number in parentheses after the group represents the weight), only the Owner group. Then only when Alice and Bob sign the transfer operation at the same time, the operation will be accepted by the system. If only Alice or Bob’s private key signs, the system will deny the service and return an error message.

Scenario 2: Alice purchases a certain financial management token issued by company B. In order to ensure safety and risk control compliance requirements, company B requires that any transaction of this token needs to be confirmed by her own company and additional transaction fees will be charged. This kind of Token structure is shown in Figure 3.

Alice is the holder of the Token, but if you want to transfer the ownership of the Token, in addition to the Owner group (that is, Alice herself) issuance, you also need to be authorized by Group B. Group B is the Token used by company B to manage its financial management. Circulation group. When Alice transfers the token, she needs to pay company B an additional fee, and then company B can check the transfer of the token at the same time, and after confirmation, it will be issued through Group B (through a third-party service), and then the transfer will be finally received by the system .

Based on this mechanism, third parties can provide many services. For example, company C specializes in password protection services. Alice is afraid that she will forget or lose the secret key and thus lose her Token. The transfer authority of this type of Token can be managed as: Owner(1), Group C(1), and at the same time The threshold is set to 1. In this case, if Alice forgets her secret key and cannot obtain the permissions of the Transfer group, she can still obtain Group C's issuance by proving to company C that she is Alice herself (through ID fingerprints, etc.). In this way, Alice can transfer this type of Token to her new account to retrieve her secret key.

Of course, Group C can do evil and transfer Alice's Token maliciously, but all operations will be recorded on the chain, which is not worth the gain for a credible company C.

Scenario 3: Here we will introduce the most complicated scenario to demonstrate the complex problems that can be solved in the authority management mechanism provided by the present invention. A company built a new office building and hoped to issue 1,000 tokens for the property rights of the building. The company set up an SPV to be responsible for issuing and maintaining these tokens. In specific life, the issuance and transfer of Token related to real estate needs to be reviewed and approved by the local real estate bureau. Only if it meets local regulations can it be approved. Then the detailed information of the relevant Token of the office building will be displayed on its official platform (total, Issuer, authority management structure, etc.). On top of this, the national real estate department has the highest authority to restrict and manage local real estate bureaus and holders. The permission structure of this type of Token may be shown in Figure 4.

The initial issuer and holder of this type of token is SPV, where Group S stands for SPV, Group L stands for local real estate bureaus, and Group C stands for central real estate department.

Generally speaking, the transfer of a Token only needs to be jointly issued by the original holder and the local real estate bureau. During this process, the local real estate bureau will review the transfer process. Under unexpected circumstances, such as the accidental death of a certain token holder or the loss of the secret key, after a judgment or review by the court or relevant department, the central real estate department can issue the token and transfer the ownership of the token to the legal successor. .

Even speaking, if part of the Token ID is accidentally lost (this is possible), or SPV and other token holders have negotiated and agreed to issue new tokens, the Central Real Estate Department can pass the issued Issue Permission to issue new tokens to meet actual needs. In addition, in some very special circumstances, for example, the Central Real Estate Department needs to temporarily freeze the circulation of this type of token, it can change the transfer authority threshold through the Manage authority it holds, thereby freezing the circulation of this type of token.

In summary, the Token structure design and Token operation authority management method in the blockchain proposed by the present invention can be specialized for Token operation, reduce the burden on the blockchain system, reduce unnecessary resource consumption, and satisfy various requirements. The ability to manage the actual situation with complex rights.

In the description of this specification, the description of Token, permission type, group, account, etc. in the blockchain does not necessarily refer to the same instance or example. Specific descriptions or features can be combined in one or more examples in a suitable manner. In addition, if there is no conflict with each other, those skilled in the art can combine different embodiments or examples and different embodiments described in this specification. Or the features of the examples are combined and combined.

Although the embodiments of the present invention have been shown and described above, it can be understood that the above-mentioned embodiments are exemplary and should not be construed as limiting the present invention.

Claims

A method for token design and operation authority management, which is characterized in that it includes four main steps: domain creation, operation request, authority verification, and operation execution. Request operations include but are not limited to issuing tokens, transferring (or trading) tokens To authenticate and manage the created domains, all operations must pass authorization verification before they can be executed.
The method according to claim 1, characterized in that, for creating a domain (Domain), information that needs to define the domain includes, but is not limited to, a non-repeatable domain name (Domain Name), issue threshold (Issue) threshold, and transfer right (Transfer). ) Threshold, Management threshold, group list for issuing rights, group list for issuing transfer rights, and group list for issuing management rights.
The method according to claim 1, wherein the issuance right refers to the right to reissue or additional tokens based on the current Domain, the transfer right refers to the right to change the current Token owner, and the management right refers to adjusting the current Domain information or structure permission.
The method according to claim 1-3, wherein the group list is composed of one or more groups, and the information of each group includes group ID (group ID, automatically generated by the system), weight (weight), the required threshold in the group, the group members, the weight corresponding to each group member, and the group public key.
The method according to claim 1, characterized in that the token is a unique number in the blockchain system, and is an indivisible and smallest individual that can be issued and transferred. The ID of the Token Including the domain name and the personalized token name (Token Name) that cannot be repeated under each domain name.
The method according to claim 1-5, characterized in that, in the definition of a domain, each permission has a corresponding group list, and each group in the group list may not have the same weight in the permission, and the group The weight of is determined by the user (individual or organization) who owns the group’s private key, and is publicly visible; at the same time, each operation has a threshold. When an operation is performed, the authorization verification process is the verification pair Whether the sum of the weights of all successful issuance groups of this operation is greater than or equal to the threshold of this operation, if it is, the operation request will be received by the system and wait for execution.
The method according to claim 6, wherein the issuance refers to that each group that has the right to issue the operation request includes one or more members, and only all members in the group have issued the operation request If the sum of the weights corresponding to the members of the group is greater than or equal to the required threshold in the group, the group is considered as a successful issuance group, otherwise it is a failed issuance group. At the same time, the person or organization holding the public key of the group can Issue an operation to modify the members and weights in the group, that is, Group Autonomy.
The method according to claim 1, characterized in that when the issuer designs the Token type authority, it can directly quote the existing group ID to invoke the group into its authority system, because of the autonomy mechanism within the group, so Each group can be reused easily.
The method according to claim 1, wherein the holders of the Token have a special group, the name of the group is fixed as Owner, which is a collection of holders of the Token, and the special feature of the group is that each Token They may be different. At the same time, the issuance condition of the group is valid only if everyone in the group issues it, that is, the weight of each person in the group is equal, and the group threshold is the number of members in the group.
A system for token design and operation authority management, including:

Create a domain module to generate new domains. Each domain has a unique domain name. The information that needs to define the domain includes but is not limited to non-repeatable domain name (Domain Name), issue threshold (Issue) threshold, and transfer threshold (Transfer) threshold , Management threshold, group list for issuing rights, group list for issuing transfer rights, and group list for issuing management rights;

The operation request module is used to send the operation request to the corresponding group according to the group list corresponding to the change operation request in the domain, to be issued within and between groups;

The authorization verification module is used to verify whether the sum of the weights of the successful issuance group of the operation reaches the required threshold. Only when the threshold is reached, the verification is deemed to be passed, and the operation can be executed;

The operation execution module is used to implement the operation after the verification is passed.
The method and system according to claims 1-10, wherein the various operations can charge all users or some of the users involved in the operation based on consumption or established standards, and it is determined by the specific implementation of the consensus mechanism .