# US 2021/0342330 A1 · Ledger data generation and storage for trusted recall of professional profiles

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

- Number: US 2021/0342330 A1
- Document ID: US20210342330A1
- Status: Published application
- Kind: A1
- Application number: 17/374,785
- Filed: 2021-07-13
- Published: 2021-11-04
- Earliest claimed: 2018-11-06
- Assignees: Workday, Inc.
- Applicants: Workday, Inc.
- Inventors: Parvinder Singh Thapar; Bradley Hoyle; Dirk Nicholas Dougherty
- Web page: https://patentgrep.com/patent/US20210342330A1

## CPC

- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/645: {using a third party}
- G06Q 10/1053: Employment or hiring
- G06Q 30/018: Certifying business or products
- 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 63/102: {Entity profiles}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- 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

A system for ledger data includes a block repository, a metadata database, and a processor. The block repository stores verified secure ledger data in one or more blocks that are cryptographically linked. The metadata database stores metadata information for the one or more blocks in the block repository. The processor is configured to receive a request to create a block content and to determine the block content for a block to be stored in the block repository and metadata content to be stored in the metadata database associated with the block to be stored in the block repository, wherein the metadata content includes one or more flags and source information; and broadcast the block to be stored in the block repository to be approved by participating nodes in a network.

## Claims

### Claim 1

A system for ledger data, comprising:
a block repository, wherein the block repository stores verified secure ledger data in one or more blocks that are cryptographically linked;
a metadata database, wherein the metadata database stores metadata information for the one or more blocks in the block repository; and
a processor configured to:
receive a request to create a block content and to determine the block content for a block to be stored in the block repository and metadata content to be stored in the metadata database associated with the block to be stored in the block repository, wherein the metadata content includes one or more flags and source information; and
broadcast the block to be stored in the block repository to be approved by participating nodes in a network.

### Claim 2 (depends on 1)

The system as in claim 1, wherein the processor is further configured to provide a flag display indication of the one or more flags for display to a candidate.

### Claim 3 (depends on 1)

The system as in claim 1, wherein a valid flag indicates whether data stored in the block has been reported as inaccurate.

### Claim 4 (depends on 1)

The system as in claim 1, wherein the one or more flags includes a share flag, wherein the share flag indicates whether a user has given permission to share the block.

### Claim 5 (depends on 1)

The system as in claim 1, wherein the source information comprises information on who provided a base content of the block content for the block.

### Claim 6 (depends on 5)

The system as in claim 5, wherein the block content comprises the base content, a block ID, and a previous block ID.

### Claim 7 (depends on 1)

The system as in claim 1, wherein the metadata content is provided to be displayed to a user.

### Claim 8 (depends on 1)

The system as in claim 1, wherein the metadata content also includes a block reference ID.

### Claim 9 (depends on 8)

The system as in claim 8, wherein the block reference ID comprises a hash.

### Claim 10 (depends on 1)

The system as in claim 1, wherein the metadata content also includes a timestamp.

### Claim 11 (depends on 1)

The system as in claim 1, wherein the metadata database includes a chain metadata.

### Claim 12 (depends on 11)

The system as in claim 11, wherein the chain metadata includes one or more of the following: a unique system ID, a chain root ID, and a forget-me flag.

### Claim 13 (depends on 12)

The system as in claim 12, wherein the forget-me flag indicates whether a user has chosen to forget a chain associated with the block.

### Claim 14 (depends on 1)

The system as in claim 1, wherein the metadata database includes a confidence metadata, wherein the confidence metadata is calculated based at least in part on a source for the block content stored in the block.

### Claim 15 (depends on 1)

The system as in claim 1, wherein the processor is further configured to store the block content as the block in the block repository.

### Claim 16 (depends on 15)

The system as in claim 15, wherein the block is stored linked to a previous block using a previous block ID.

### Claim 17 (depends on 1)

The system as in claim 1, wherein the processor is further configured to read the block content from the block repository in response to a request by a requestor.

### Claim 18 (depends on 17)

The system as in claim 17, wherein reading the block content includes reading the metadata content associated with the block.

### Claim 19 (depends on 18)

The system as in claim 18, wherein the block content is read or provided to the requestor based at least in part on the one or more flags.

### Claim 20 (depends on 19)

The system as in claim 19, wherein the block content is not provided to the requestor in response to a forget-me determination that a forget-me flag is true for a block chain associated with the block.

### Claim 21 (depends on 19)

The system as in claim 19, wherein the block content is not provided to the requestor in response to a not valid determination that a valid flag is not true for the block.

### Claim 22 (depends on 19)

The system as in claim 19, wherein the block content is not provided to the requestor in response to a not share determination that a share flag is not true for the block.

### Claim 23

A method for a ledger data system, comprising:
receive, using a processor, a request to create a block content and to determine the block content for a block to be stored in a block repository and metadata content to be stored in a metadata database associated with the block to be stored in the block repository, wherein the block repository stores verified secure ledger data in one or more blocks that are cryptographically linked, wherein the metadata database stores metadata information for the one or more blocks in the block repository, wherein the metadata content includes one or more flags and source information; and
broadcast the block to be stored in the block repository to be approved by participating nodes in a network.

### Claim 24

A computer program product for a ledger data system, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receive, using a processor, a request to create a block content and to determine the block content for a block to be stored in a block repository and metadata content to be stored in a metadata database associated with the block to be stored in the block repository, wherein the block repository stores verified secure ledger data in one or more blocks that are cryptographically linked, wherein the metadata database stores metadata information for the one or more blocks in the block repository, wherein the metadata content includes one or more flags and source information; and
broadcast the block to be stored in the block repository to be approved by participating nodes in a network.
