# US 2020/0349556 A1 · Methods and devices for managing access to account in blockchain system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0349556 A1
- Document ID: US20200349556A1
- Status: Published application
- Kind: A1
- Application number: 16/773,235
- Filed: 2020-01-27
- Published: 2020-11-05
- Earliest claimed: 2019-04-30
- Assignees: Alibaba Group Holding Limited
- Applicants: Alibaba Group Holding Limited
- Inventors: Zhongxiao YAO
- Web page: https://patentgrep.com/patent/US20200349556A1

## CPC

- G06Q 20/3674: {involving authentication}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q 20/223: {based on the use of peer-to-peer networks}
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed herein are methods, devices, and apparatuses, including computer programs stored on computer-readable media for managing access to an account in a blockchain system. One of the methods includes: receiving, from a first account of the blockchain system, a request for accessing a second account of the blockchain system; determining an account level of the first account based on the request; determining an account level of the second account; determining whether the account level of the first account satisfies an account condition based on the account level of the second account; and permitting the request for accessing the second account based on a determination that the account level of the first account satisfies the account condition.

## Claims

### Claim 1

A computer-implemented method for managing access to an account in a blockchain system, comprising:
receiving, by a node of the blockchain system, a request from a first account of the blockchain system to access a second account of the blockchain system, the blockchain system comprising a plurality of nodes for maintaining a blockchain, the blockchain comprising a plurality of blocks, each block, other than a first block, of the plurality of blocks being linked to a previous block in the blockchain using a cryptographic hash of the previous block;
determining, by the node, an account level of the first account based on the request;
determining, by the node, an account level of the second account;
determining, by the node, whether the account level of the first account satisfies an account condition based on the account level of the second account; and
authorizing access to the second account, by the node, based on a determination that the account level of the first account satisfies the account condition.

### Claim 2 (depends on 1)

The method of claim 1, wherein the account condition comprises the account level of the first account being higher than or equal to the account level of the second account.

### Claim 3 (depends on 1)

The method of claim 1, wherein the second account is one of a contract account corresponding to a smart contract or a regular account that does not correspond to a smart contract.

### Claim 4 (depends on 3)

The method of claim 3, wherein when the second account is the contract account corresponding to a smart contract, and the smart contract comprises an interface related to a function of the smart contract, the method further comprises:
determining an interface level of the interface.

### Claim 5 (depends on 4)

The method of claim 4, wherein the request for accessing the second account further comprises a request for accessing the interface of the smart contract, and the method further comprises:
determining whether the account level of the first account satisfies an interface condition based on the interface level; and
in response to a determination that the account level of the first account satisfies the interface condition, authorizing access to the interface of the smart contract.

### Claim 6 (depends on 5)

The method of claim 5, wherein the interface condition comprises the account level of the first account being higher than or equal to the interface level.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
in response to a determination that the account level of the first account does not satisfy the interface condition, denying the request for accessing the interface of the smart contract.

### Claim 8 (depends on 7)

The method of claim 7, wherein the smart contract comprises a first interface having a first interface condition and a second interface having a second interface condition, the request for accessing the interface of the smart contract further comprises a first request for accessing the first interface and a second request for accessing the second interface, and the method further comprises at least one of:
in response to a determination that the account level of the first account satisfies the account condition and the first interface condition, authorizing the first request access to the first interface of the smart contract; and
in response to a determination that the account level of the first account does not satisfy the account condition and the second interface condition, denying the second request for accessing the second interface of the smart contract.

### Claim 9 (depends on 5)

The method of claim 5, further comprising:
after a determination that the first level of the first account satisfies the account condition, performing the determining whether the account level of the first account satisfies the interface condition based on the interface level; and in response to the determination that the account level of the first account satisfies the interface condition, authorizing access to the interface of the smart contract.

### Claim 10 (depends on 3)

The method of claim 3, wherein
the account level of the first account comprises a public level, a protected level, or a privileged level; and
the account level of the second account comprises the public level, the protected level, or the privileged level.

### Claim 11 (depends on 4)

The method of claim 4, wherein
the account level of the first account comprises a public level, a protected level, or a privileged level;
the account level of the second account comprises the public level, the protected level, or the privileged level; and
the interface level comprises the public level, the protected level, or the privileged level.

### Claim 12 (depends on 11)

The method of claim 11, wherein
the account level of the contract account is the public level by default; and
the interface level is the public level by default.

### Claim 13 (depends on 1)

The method of claim 1, wherein in determining the account level of the first account based on the request, the method further comprises:
determining an identity of the first account based on the request; and
determining the account level of the first account based on the determined identity.

### Claim 14

A device for managing access to a smart contract in a blockchain system that maintains a blockchain comprising a plurality of blocks, each block, other than a first block, of the plurality of blocks being linked to a previous block in the blockchain using a cryptographic hash of the previous block, the device comprising:
one or more processors; and
one or more computer-readable memories coupled to the one or more processors and having instructions stored thereon that are executable by the one or more processors, wherein the one or more processors are configured to:
receive, by the device, a request from a first account of the blockchain system to access a second account of the blockchain system;
determine, by the device, an account level of the first account based on the request;
determine, by the device, an account level of the second account;
determine, by the device, whether the account level of the first account satisfies an account condition based on the account level of the second account; and
authorize access to the second account, by the device, based on a determination that the account level of the first account satisfies the account condition.

### Claim 15

(canceled)

### Claim 16

A non-transitory computer-readable medium having stored therein instructions that, when executed by a processor of a device, cause the device to perform a method for managing access to an account in a blockchain system that maintains a blockchain comprising a plurality of blocks, each block, other than a first block, of the plurality of blocks being linked to a previous block in the blockchain using a cryptographic hash of the previous block, the method comprising:
receiving, by the device, a request from a first account of the blockchain system to access a second account of the blockchain system;
determining, by the device, an account level of the first account based on the request;
determining, by the device, an account level of the second account;
determining, by the device, whether the account level of the first account satisfies an account condition based on the account level of the second account; and
authorizing access to the second account, by the device, based on a determination that the account level of the first account satisfies the account condition.

### Claim 17 (depends on 14)

The device of claim 14, wherein the account condition comprises the account level of the first account being higher than or equal to the account level of the second account.

### Claim 18 (depends on 14)

The device of claim 14, wherein the second account is one of a contract account corresponding to a smart contract or a regular account that does not correspond to a smart contract.

### Claim 19 (depends on 18)

The device of claim 18, wherein when the second account is the contract account corresponding to a smart contract, and the smart contract comprises an interface related to a function of the smart contract, the one or more processors are further configured to:
determine an interface level of the interface.

### Claim 20 (depends on 19)

The device of claim 19, wherein the request for accessing the second account further comprises a request for accessing the interface of the smart contract, and the one or more processors are further configured to:
determine whether the account level of the first account satisfies an interface condition based on the interface level; and
in response to a determination that the account level of the first account satisfies the interface condition, authorize access to the interface of the smart contract.
