# US 2018/0025435 A1 · Method for secure ledger distribution and computer system using secure distributed ledger technology

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

- Number: US 2018/0025435 A1
- Document ID: US20180025435A1
- Status: Published application
- Kind: A1
- Application number: 15/216,709
- Filed: 2016-07-22
- Published: 2018-01-25
- Earliest claimed: 2016-07-22
- Assignees: NEC Europe Ltd.
- Applicants: NEC Europe Ltd.
- Inventors: Ghassan Karame; Wenting Li; Alessandro Sforzin
- Web page: https://patentgrep.com/patent/US20180025435A1

## CPC

- G06Q 40/12: Accounting
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- H04L 9/3236: {using cryptographic hash functions}
- G06Q 2220/00: Business processing using cryptography
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- 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

A method of providing secure ledger distribution for interbank settlement includes establishing a private sidechain among a centralized computer system of a central bank and computer systems of at least a sender bank and a receiver bank, each of which have an account with the central bank. The centralized computer system receives a transaction from the computer system of the sender bank as a payment request. The centralized computer system determines whether the transaction is valid. Consensus is reached within the private sidechain. The centralized computer system forwards the transaction to the computer system of the receiver bank along with a finality proof. The accounts of the sender bank and the receiver bank are updated and the transaction is added to a private ledger accessible only within the private sidechain.

## Claims

### Claim 1

A method of providing secure ledger distribution for interbank settlement, the method comprising:
establishing a first private sidechain among a centralized computer system of a central bank and computer systems of at least a first sender bank and a first receiver bank, each of which have an account with the central bank;
receiving, by the centralized computer system, a first transaction from the computer system of the first sender bank as a first payment request;
determining, by the centralized computer system, whether the first transaction is valid;
reaching consensus within the first private sidechain;
forwarding, by the centralized computer system, the first transaction to the computer system of the first receiver bank along with a first finality proof; and
updating the accounts of the first sender bank and the first receiver bank and adding the first transaction to a first private ledger accessible only within the first private sidechain.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the first transaction is a token transaction or a tokenize transaction, and wherein tokens generated or redeemed are used to facilitate an asset transfer among the first private sidechain and at least a second private sidechain.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising:
establishing a second private sidechain among the centralized computer system and computer systems of at least a second sender bank and a second receiver bank, each of which have an account with the central bank;
receiving, by the centralized computer system, a second transaction from the computer system of the second sender bank as a second payment request;
determining, by the centralized computer system, whether the second transaction is valid;
reaching consensus within the second private sidechain;
forwarding, by the centralized computer system, the second transaction to the computer system of the second receiver bank along with a second finality proof; and
updating the accounts of the second sender bank and the second receiver bank and adding the second transaction to a second private ledger accessible only within the second private sidechain,
wherein the first and second private sidechains have different participants from each other.

### Claim 4 (depends on 3)

The method according to claim 3, wherein the first transaction is a tokenize transaction and the second transaction is a token transaction, and wherein tokens generated or redeemed are used to facilitate an asset transfer among the first private sidechain and at least the second private sidechain.

### Claim 5 (depends on 4)

The method according to claim 4, wherein the first receiver bank and the second sender bank are the same bank, and wherein the centralized computer system applies tokens received from the tokenize transaction to the token transaction.

### Claim 6 (depends on 5)

The method according to claim 5, further comprising receiving, by the centralized computer system, a redeem request from the second receiver bank to redeem the tokens and updating a balance of the account of the second receiver bank.

### Claim 7 (depends on 6)

The method according to claim 6, wherein a balance of the account of the bank which is the first receiver bank and the second sender bank is not updated throughout the first and second transactions.

### Claim 8

A computer system of a central bank using secure distributed ledger technology for interbank settlement, the computer system comprising one or more processors or servers, which alone or in combination, are configured to:
establish a first private sidechain among itself and computer systems of at least a first sender bank and a first receiver bank, each of which have an account with the central bank;
receive a first transaction from the computer system of the first sender bank as a first payment request;
determine whether the first transaction is valid;
reach consensus within the first private sidechain;
forward the first transaction to the computer system of the first receiver bank along with a first finality proof; and
update the accounts of the first sender bank and the first receiver bank and add the first transaction to a first private ledger accessible only within the first private sidechain.

### Claim 9 (depends on 8)

The computer system according to claim 8, being further configured to perform the first transaction as a token transaction or a tokenize transaction based on whether the account of the first sender bank has tokens, and to use tokens generated or redeemed to facilitate an asset transfer among the first private sidechain and at least a second private sidechain.

### Claim 10 (depends on 8)

The computer system according to claim 8, being further configured to:
establish a second private sidechain among itself and computer systems of at least a second sender bank and a second receiver bank, each of which have an account with the central bank;
receive a second transaction from the computer system of the second sender bank as a second payment request;
determine whether the second transaction is valid;
reach consensus within the second private sidechain;
forward the second transaction to the computer system of the second receiver bank along with a second finality proof; and
update the accounts of the second sender bank and the second receiver bank and add the second transaction to a second private ledger accessible only within the second private sidechain,
wherein the first and second private sidechains have different participants from each other.

### Claim 11 (depends on 10)

The computer system according to claim 10, being further configured to perform the first transaction as a tokenize transaction based on the account of the first sender bank not having enough tokens to fulfill the first payment request, and to perform the second transaction as a token transaction based on the account of the second sender bank having enough tokens to fulfill the second payment request.

### Claim 12 (depends on 11)

The computer system according to claim 11, wherein the first receiver bank and the second sender bank are the same bank, and wherein tokens received from the tokenize transaction are used for the token transaction.

### Claim 13 (depends on 12)

The computer system according to claim 12, being further configured to update a balance of the account of the second receiver bank in response to a redeem request received from the second receiver bank to redeem the tokens.

### Claim 14 (depends on 13)

The computer system according to claim 13, wherein a balance of the account of the bank which is the first receiver bank and the second sender bank, stored in a memory of the computer system of the central bank, is not updated throughout the first and second transactions.

### Claim 15

A tangible, non-transitory computer-readable medium containing instructions thereon which, upon being executed by a computer system including one or more processors or servers, permits the following steps to be carried out:
establishing a private sidechain among a centralized computer system of a central bank and computer systems of at least a sender bank and a receiver bank, each of which have an account with the central bank;
receiving a transaction from the computer system of the sender bank as a payment request;
determining whether the transaction is valid;
reaching consensus within the private sidechain;
forwarding the transaction to the computer system of the receiver bank along with a finality proof; and
updating the accounts of the sender bank and the receiver bank and adding the transaction to a private ledger accessible only within the private sidechain.
