# US 2019/0379531 A1 · Method For Registration Of Data In A Blockchain Database And A Method For Verifying Data

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

- Number: US 2019/0379531 A1
- Document ID: US20190379531A1
- Status: Published application
- Kind: A1
- Application number: 16/231,367
- Filed: 2018-12-21
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Assignees: Coinfirm Blockchain Lab Sp. Zo.o.
- Applicants: Coinfirm Blockchain Lab Sp. Zo.o.
- Inventors: Pawel Zygmunt ALEKSANDER; Pawel KUSKOWSKI; Jakub FIJOLEK
- Web page: https://patentgrep.com/patent/US20190379531A1

## CPC

- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- G06F 16/152: {using file content signatures, e.g. hash values}
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The invention comprises a method for registration of data in a blockchain database, in which database transactions are constructed of standard data containers which may have a fixed size, in a system comprising one or more storage nodes for storing at least part of the blockchain database, one or more approval nodes for approving transactions in said blockchain database and a first computer for generating transactions in said blockchain database, said computer having access to said blockchain database and having access to a first private key. The invention further comprises a method for verifying data based on the aforementioned method for registration and an application of these methods to handle a selected type of document. The invention also comprises a computer program product comprising program code stored on a computer readable medium, said program code comprising computer instructions for performing these methods.

## Claims

### Claim at position 1

1-15. (canceled)

### Claim 16

A method for registration of a digital document as a digital file in a blockchain database and for verifying the digital document, in which a plurality of database transactions are constructed of a plurality of data containers, in a system comprising a plurality of storage nodes for storing at least a portion of the blockchain database, a plurality of approval nodes for approving transactions in the blockchain database and a first computer for generating transactions in the blockchain database, the computer having access to the blockchain database and having access to a first private key, comprising the steps of:
a) providing a first set of data, relating to the contents of the digital file;
b) providing a second set of data, relating to the origin of the digital file;
c) generating a third set of data by merging a header, the first set of data, the second set of data and a suffix into a data frame, where the header contains information about a size of the first set of data, while the size of the suffix is adjusted between zero and a size of a standard data container used in the blockchain database such that the size of the data frame is a multiple of the size of the standard data container used in the blockchain database;
d) dividing the third set of data into an integer number N≥1 of parts of equal size, the size corresponding to the size of the standard data container used in the blockchain database;
e) generating, by the first computer or an intermediary computer connected to the first computer and one or more of the approval nodes, a single blockchain database transaction for all the N parts obtained in the step d), signing the transaction by the first private key and sending the transaction and a first public key matching the first private key to one or more of the approval nodes for approval;
f) obtaining approval for the transaction from one or more of the approval nodes;
g) registering the transaction approved in the step f) in a block of the blockchain database with a timestamp of registration by the one or more storage nodes;
registering the digital document as the digital file in the blockchain database by the first entity;
and transmitting the digital document from the first entity to a second entity.

### Claim 17 (depends on 16)

The method of claim 16, where the following information is stored in a separate database, in relation to the first set of data by the first entity: a transaction hash corresponding to the transaction generated in step e), a block hash, a block height and a block timestamp of registration, corresponding to the block mentioned in the step g).

### Claim 18 (depends on 16)

The method of claim 16, further comprising a method of verifying the digital document, the method comprising the steps of:
h1) providing a test digital file by a user through a web browser;
i1) calculating a hash of the test digital file wherein the hash is generated by a SHA256 algorithm, a SHA3-256 algorithm, or a SHA3-512 algorithm, or any other suitable algorithm;
j1) checking if the hash of the test digital file matches a first set of data being a hash of the digital file, as stored in a block of the blockchain database; and
sending a confirmation to the user through the web browser, the confirmation comprising information relating to the contents of the test digital file and comprising information of an origin of the test digital file and information relating to a block timestamp of registration.

### Claim 19 (depends on 17)

The method of claim 17, further comprising a method for verifying data comprising the following steps:
h2) providing a test digital file by a user, preferably through a web browser;
i2) calculating the hash of the test digital file wherein the hash is generated by a SHA256 algorithm, a SHA3-256 algorithm, or a SHA3-512 algorithm, or any other suitable algorithm;
j2) checking if the hash of the test digital file matches the first set of data being a hash of the digital file, previously stored in the separate database; and
sending a confirmation to the user, preferably through the web browser, the confirmation comprising information relating to the contents of the test digital file and comprising information relating to the origin of the test digital file and information relating to the block timestamp of registration.

### Claim 20 (depends on 18)

The method of claim 18, where if the hash of the test digital file matches more than one of the data generated in the step j1) then only information corresponding to the transaction bearing the oldest timestamp of registration is used as a basis to generate the confirmation to the user.

### Claim 21 (depends on 18)

The method of claim 18, where if the hash of the test digital file matches more than one of the data generated in the step j1) then information corresponding to transactions bearing any timestamp of registration is used as a basis to generate the confirmation to the user

### Claim 22 (depends on 19)

The method of claim 19, where if the hash of the test digital file matches more than one of the data generated in the step j2), then only information corresponding to the transaction bearing the oldest timestamp of registration is used as a basis to generate the confirmation to the user.

### Claim 23 (depends on 19)

The method of claim 19, where if the hash of the test digital file matches more than one of the data generated in the step j2), then information corresponding to transactions bearing any timestamp of registration is used as a basis to generate the confirmation to the user.

### Claim 24 (depends on 18)

The method of claim 18, where the first set of data is a hash of the digital file, generated by a group consisting of: a SHA256 algorithm, a SHA3-256 algorithm, or a SHA3-512 algorithm.

### Claim 25 (depends on 24)

The method of claim 24, wherein the first set of data is a hash of the digital file and is generated by;
the SHA256 algorithm and has a size of 64 hex digits or a multiple thereof the SHA3-256 algorithm and has the size of 64 hex digits or a multiple thereof, or the SHA3-512 algorithm and has the size of 128 hex digits or a multiple thereof.

### Claim 26 (depends on 19)

The method of claim 19, where the first set of data is a hash of the digital file, generated by a group consisting of: a SHA256 algorithm, a SHA3-256 algorithm, or a SHA3-512 algorithm.

### Claim 27 (depends on 26)

The method of claim 26, wherein the first set of data is a hash of the digital file and is generated by;
the SHA256 algorithm and has a size of 64 hex digits or a multiple thereof the SHA3-256 algorithm and has the size of 64 hex digits or a multiple thereof, or the SHA3-512 algorithm and has the size of 128 hex digits or a multiple thereof.

### Claim 28 (depends on 16)

The method of claim 16, wherein the second set of data comprises a digital signature of the digital file, preferably calculated as a function of a group consisting of: the hash of the digital file, a private key corresponding to the origin of the digital file,

### Claim 29 (depends on 28)

The method according to claim 28, wherein the second set of data has a size of 130 hex digits.

### Claim 30 (depends on 16)

The method of claim 16, wherein the header has the size of 6 hex digits and comprises the following information: a version of the digital file, a type of the digital file, a number of hashes that are stored in the data frame, and a number of signatories of the digital file.

### Claim 31 (depends on 16)

The method of claim 16, wherein the blockchain database is a Dash database or a Bitcoin database, and a standard data container has a size of 40 hex digits.

### Claim 32 (depends on 16)

The method according to claim 16, wherein the digital document contains personal data of a client and the client's transaction history, and optionally the digital document comprises a bank statement, preferably the digital document is a bank statement or a similar document containing personal data of the client and transactions history on a bank account of the client.

### Claim 33 (depends on 16)

The method according to claim 16, wherein the step of transmitting the digital document from the first entity to the second entity includes transmitting the digital document through a user terminal.

### Claim 34 (depends on 16)

A computer program product comprising program code stored on a computer readable medium, the program code comprising computer instructions for performing the method according to claim 16.
