System and method for sharing a distributed revocation list on a blockchain

1 . A system for sharing a distributed revocation list on a blockchain, the system comprising:

circuitry configured to:

receive information indicating a first digital wallet on a first blockchain network is suspicious,

add the first digital wallet to the distributed revocation list, the distributed revocation list including a list of digital wallets indicated as being suspicious,

generate a first soulbound token request,

transmit the first soulbound token request to a first smart contract of the first blockchain network, wherein the first soulbound token request is configured to instruct the first smart contract to generate a first soulbound token and airdrop the first soulbound token to the first digital wallet,

upon detecting a transaction request from the first digital wallet to a second digital wallet on a second blockchain network separate from the first blockchain network, determine whether the first digital wallet includes the first soulbound token,

upon determining the first digital wallet includes the first soulbound token and upon determining the first soulbound token was airdropped from a source in a local authorized source list of the second blockchain network, deny the transaction request on the second blockchain network, and add the second digital wallet to the distributed revocation list, the second digital wallet marked as being associated with the first digital wallet, and

upon determining the distributed revocation list includes a new entry after adding the second digital wallet to the distributed revocation list, transmit an updated distributed revocation list to the second blockchain network,

wherein the first soulbound token indicates that the first digital wallet is on the distributed revocation list, and wherein a suspicious status follows the first digital wallet to any additional digital wallet associated with the first digital wallet.

2 . The system according to claim 1 , wherein the circuitry is further configured to:

upon detecting the transaction request from the first digital wallet to the second digital wallet, and upon determining the first digital wallet includes the first soulbound token and the first soulbound token was airdropped from the source in the local authorized source list of the second blockchain network,

generate a second soulbound token, and

airdrop the second soulbound token to the second digital wallet.

3 . The system according to claim 2 , 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 from the second digital wallet.

4 . 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 suspicious event.

5 . The system according to claim 1 , wherein the circuitry is further configured to:

determine whether the first digital wallet being suspicious is false, and

upon determining the first digital wallet being suspicious is false;

revoke the first soulbound token in the first digital wallet, and

remove the first digital wallet from the distributed revocation list.

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

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

8 . 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 transfer of the first soulbound token.

9 . 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.

10 . 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 suspicious, pause the first blockchain network.

11 . The system according to claim 1 , wherein upon 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 not sent from a source in the local authorized source list, process the transaction request based on a policy of the second blockchain network corresponding to the second digital wallet.

12 . The system according to claim 11 , 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.

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

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

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

16 . The system according to claim 1 , wherein the circuitry is further configured to, before determining the first digital wallet includes the first soulbound token and determining the first soulbound token was sent from the source in the local authorized source list of the second blockchain network, update the local authorized source list of the second blockchain network based on a global authorized source list of the first blockchain network.

17 . The system according to claim 1 , wherein:

the circuitry is further configured to transmit an investigation request to a remote processing device to determine whether the first digital wallet is suspicious, and

the circuitry receives the information indicating the first digital wallet on the first blockchain network is suspicious from the remote processing device.

18 . A method for sharing a distributed revocation list on a blockchain, the method comprising:

receiving, by circuitry, information indicating a first digital wallet on a first blockchain network is suspicious;

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 suspicious;

generating a first soulbound token request,

transmitting the first soulbound token request to a first smart contract of the first blockchain network, wherein the first soulbound token request is configured to instruct the first smart contract to generate a first soulbound token and airdrop the first soulbound token to the first digital wallet,

upon detecting a transaction request from the first digital wallet to a second digital wallet on a second blockchain network separate from the first blockchain network, determining whether the first digital wallet includes the first soulbound token;

upon determining the first digital wallet includes the first soulbound token and upon determining the first soulbound token was airdropped from a source in a local authorized source list of the second blockchain network, denying the transaction request on the second blockchain network; and adding the second digital wallet to the distributed revocation list, the second digital wallet marked as being associated with the first digital wallet; and

upon determining the distributed revocation list includes a new entry after adding the second digital wallet to the distributed revocation list, transmitting an updated distributed revocation list to the second blockchain network,

wherein the first soulbound token indicates that the first digital wallet is on the distributed revocation list, and wherein a suspicious status follows the first digital wallet to any additional digital wallet associated with the first digital wallet.

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 suspicious;

adding the first digital wallet to the distributed revocation list the distributed revocation list including a list of digital wallets indicated as being suspicious;

generating a first soulbound token request,

transmitting the first soulbound token request to a first smart contract of the first blockchain network, wherein the first soulbound token request is configured to instruct the first smart contract to generate a first soulbound token and airdrop the first soulbound token to the first digital wallet,

upon detecting a transaction request from the first digital wallet to a second digital wallet on a second blockchain network separate from the first blockchain network, determining whether the first digital wallet includes the first soulbound token;

upon determining the first digital wallet includes the first soulbound token and upon determining the first soulbound token was sent airdropped from a source in a local authorized source list of the second blockchain network, denying the transaction request on the second blockchain network; and adding the second digital wallet to the distributed revocation list, the second digital wallet marked as being associated with the first digital wallet; and

upon determining the distributed revocation list includes a new entry after adding the second digital wallet to the distributed revocation list, transmitting an updated distributed revocation list to the second blockchain network,

wherein the first soulbound token indicates that the first digital wallet is on the distributed revocation list, and wherein a suspicious status follows the first digital wallet to any additional digital wallet associated with the first digital wallet.