# US 2024/0177144 A1 · System and method for sharing a distributed revocation list on a blockchain

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

- Number: US 2024/0177144 A1
- Document ID: US20240177144A1
- Status: Published application
- Kind: A1
- Application number: 18/072,130
- Filed: 2022-11-30
- Published: 2024-05-30
- Earliest claimed: 2022-11-30
- Assignees: Nagravision Sarl
- Applicants: Nagravision Sarl
- Inventors: Yann BIEBER; Vishruta Gowda RUDRESH
- Web page: https://patentgrep.com/patent/US20240177144A1

## CPC

- G06Q 20/065: {using e-cash}
- G06Q 20/3674: {involving authentication}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/405: {Establishing or using transaction specific rules}
- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q 2220/00: Business processing using cryptography
- 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 sharing a distributed revocation list on a blockchain includes circuitry that identifies an access attempt by a wallet on a first blockchain network, and adds the wallet to a blacklist. The blacklist identifies the wallet as suspicious. The circuitry generates a soulbound token, and airdrops the soulbound token into the wallet. The soulbound token identifies that the wallet belongs to the distributed revocation list and identifies the wallet as a suspicious wallet to blockchain networks.

## Claims

### Claim 1

A system for sharing a distributed revocation list on a blockchain, comprising:
circuitry configured to
receive information indicating a first digital wallet on a first blockchain network is flagged,
add the first digital wallet to the distributed revocation list, the distributed revocation list including a list of digital wallets indicated as being flagged,
generate a first soulbound token, and
send the first soulbound token to the first digital wallet, wherein
the first soulbound token indicates that the first digital wallet belongs to the distributed revocation list and indicates the first digital wallet is a flagged digital wallet to blockchain networks, and
a flagged status follows the first digital wallet to any additional digital wallet associated with the first digital wallet.

### Claim 2 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to
upon detecting a transaction request from the first digital wallet to a second digital wallet, determine whether the first digital wallet includes the first soulbound token, and
upon determining the first digital wallet includes the first soulbound token, reject the transaction request.

### Claim 3 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to
upon detecting a transaction request from the first digital wallet to a second digital wallet,
add the second digital wallet to the distributed revocation list,
generate a second soulbound token, and
send the second soulbound token to the second digital wallet before the second digital wallet initiates a second transaction request.

### Claim 4 (depends on 3)

The system according to claim 3, wherein the circuitry is further configured to
upon detecting a transaction request from the second digital wallet, determine whether the second digital wallet includes the second soulbound token, and
upon determining the second digital wallet includes the second soulbound token, reject the transaction request.

### Claim 5 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to
monitor a transaction conducted by the first digital wallet on the first blockchain network to identify the transaction is a flagged event.

### Claim 6 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to
determine whether the first digital wallet being flagged is false, and
upon determining the first digital wallet being flagged is false,
revoke the first soulbound token in the first digital wallet, and
remove the first digital wallet from the distributed revocation list.

### Claim 7 (depends on 6)

The system according to claim 6, wherein the circuitry is further configured to
perform revocation of the first soulbound token by amending metadata of the first soulbound token.

### Claim 8 (depends on 5)

The system according to claim 5, wherein the circuitry is further configured to determine whether the flagged event is false based on context information related to the transaction.

### Claim 9 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to
upon detecting an attempt by the first digital wallet to transfer the first soulbound token, block the transfer of the first soulbound token.

### Claim 10 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to
upon detecting a transaction request from the first digital wallet, determine whether the first digital wallet is in the distributed revocation list, and
upon determining the first digital wallet is in the distributed revocation list, reject the transaction request.

### Claim 11 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to
upon receiving the information indicating the first digital wallet on the first blockchain network is flagged, pause transactions on the first blockchain network.

### Claim 12 (depends on 2)

The system according to claim 2, wherein upon the detecting the transaction request from the first digital wallet to the second digital wallet, the circuitry is further configured to
upon determining the first soulbound token was sent from a source in a local authorized source list, deny the transaction request, and
upon determining the first soulbound token was not sent from a source in the local authorized source list, process the transaction request based on a policy of a second blockchain network of the blockchain networks corresponding to the second digital wallet.

### Claim 13 (depends on 12)

The system according to claim 12, wherein the circuitry is further configured to generate a global authorized source list, and the second blockchain network obtains the global authorized source list, and updates the local authorized source list based on the obtained global authorized source list.

### Claim 14 (depends on 1)

The system according to claim 1, wherein the circuitry is further configured to send the first soulbound token with a highest priority.

### Claim 15 (depends on 3)

The system according to claim 3, wherein the circuitry is further configured to send the second soulbound token with a highest priority.

### Claim 16 (depends on 1)

The system according to claim 1, wherein the first digital wallet is flagged based on a transaction by the first digital wallet being a flagged event, the flagged event including at least one of an exploit, a heist, fund laundering, theft, a phishing attack, an unauthorized intrusion, and an unauthorized access attempt.

### Claim 17 (depends on 1)

The system according to claim 1, wherein the first blockchain network includes a first smart contract and the circuitry is further configured to generate the first soulbound token and send the first soulbound token to the first digital wallet by
generating a first soulbound token request, and
transmitting the first soulbound token request to the first smart contract, the first soulbound token request configured to instruct the first smart contract to generate the first soulbound token and transmit the first soulbound token to the first digital wallet.

### Claim 18

A method for sharing a distributed revocation list on a blockchain, comprising:
receiving, by circuitry, information indicating a first digital wallet on a first blockchain network is flagged;
adding, by the circuitry, the first digital wallet to the distributed revocation list the distributed revocation list including a list of digital wallets indicated as being flagged;
generating, by the circuitry, a first soulbound token; and
sending, by the circuitry, the first soulbound token to the first digital wallet, wherein
the first soulbound token indicates that the first digital wallet belongs to the distributed revocation list and indicates the first digital wallet is a flagged digital wallet to blockchain networks, and
a flagged status follows the first digital wallet to any additional digital wallet associated with the first digital wallet.

### Claim 19

A non-transitory computer readable medium including computer readable instructions, which when executed by at least one processor, causes the at least one processor to perform a method for sharing a distributed revocation list on a blockchain, the method comprising:
receiving information indicating a first digital wallet on a first blockchain network is flagged;
adding the first digital wallet to the distributed revocation list the distributed revocation list including a list of digital wallets indicated as being flagged;
generating a first soulbound token; and
sending the first soulbound token to the first digital wallet, wherein
the first soulbound token indicates that the first digital wallet belongs to the distributed revocation list and indicates the first digital wallet is a flagged digital wallet to blockchain networks, and
a flagged status follows the first digital wallet to any additional digital wallet associated with the first digital wallet.
