IP Library Granted Patent US 12,165,154
Granted Patent B2
US 12,165,154 · App. 18/102,973 · Granted Dec 10, 2024

Decentralized safeguard against fraud

Inventors: Eric Bravick (Traverse City, MI); David Kuchar (San Francisco, CA); Malcolm Garland (San Francisco, CA); Harrison Dahme (San Francisco, CA); David Marc Grossblatt (San Francisco, CA)
Assignee: STRONG FORCE TX PORTFOLIO 2018, LLC
G06Q20/4016H04L9/0637G06Q2220/00H04L2209/56
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,165,154
App. No.
18/102,973
Granted
Dec 10, 2024
Kind
B2
Abstract

A method includes acquiring, at a node server, blockchain data for a blockchain address on a blockchain network. The blockchain data includes a plurality of transactions for the blockchain address. The method includes generating a local node trust score for the blockchain address based on the blockchain data. The local node trust score indicates a likelihood that the blockchain address is involved in fraudulent activity. The method includes receiving, from a plurality of remote servers, a plurality of additional local trust scores for the blockchain address. The method includes determining a consensus trust score based on the local node trust score and the plurality of additional local trust scores. Additionally, the method includes receiving a trust request for the blockchain address from a requesting device and sending the consensus trust score for the specified blockchain address to the requesting device.

Claims (76)

1. A method comprising:

acquiring, by a node server of a plurality of node servers that collectively implement a decentralized trust network, blockchain data for a blockchain address on a blockchain network, wherein the blockchain data includes a plurality of transactions for the blockchain address;

generating, by the node server, a local node trust score for the blockchain address based on the blockchain data for the blockchain address, wherein the local node trust score indicates a likelihood that the blockchain address is involved in fraudulent activity;

receiving a plurality of additional local trust scores for the blockchain address from two or more other node servers of the plurality of node servers, wherein each respective additional local trust score is generated by a respective node server of the two or more other node servers;

determining, by the node server, a consensus trust score based on the local node trust score and the plurality of additional local trust scores, wherein the consensus trust score indicates a consensus value for the local node trust score among the node server and the two or more other node servers;

receiving, by the node server, a trust request for the blockchain address from a centralized application executed by the blockchain, the trust request indicating the blockchain address, and

sending the consensus trust score for the blockchain address from the node server to the decentralized application.

2. The method of claim 1 , further comprising:

generating, by the node server, a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores;

identifying, by the node server, outlier trust scores included in the trust score list;

removing, by the node server, the identified outlier trust scores, and

determining, by the node server, the consensus trust score based on the trust scores included in the trust score list after removing the identified outlier trust scores.

3. The method of claim 1 , further comprising:

generating, by the node server, a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores;

and determining, by the node server, the consensus trust score based on a weighted average of the local node trust score and the plurality of additional local trust scores in the trust score list.

4. The method of claim 1 , further comprising:

generating, by the node server, a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores;

determining, by the node server, whether the trust score list includes greater than a threshold number of trust scores; and

determining, by the node server, the consensus trust score based on the trust scores included in the trust score list when the trust score list includes greater than the threshold number of trust scores.

5. The method of claim 1 , further comprising:

generating, by at the node server, a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores;

identifying, by at the node server, outlier trust scores included in the trust score list;

requesting new local trust scores from the two or more other node servers in response to identifying the outlier trust scores;

receiving, by the node server, the new local trust scores; and

determining, by the node server, the consensus trust score based on the new local trust scores.

6. The method of claim 1 , further comprising:

determining, by at the node server, a local candidate consensus trust score based on the local node trust score and the plurality of additional local trust scores; and

determining, by at the node server, the consensus trust score based on the candidate consensus trust score.

7. The method of claim 6 , further comprising:

receiving a plurality of additional candidate consensus trust scores for the blockchain address from the two or more other node servers; and

determining, by the node server, the consensus trust score based on the local candidate consensus trust score and the plurality of additional candidate consensus trust scores.

8. The method of claim 1 , further comprising receiving, by the node server, a reward payment based on calculation of at least one of the local node trust score or the consensus trust score.

9. The method of claim 1 , further comprising receiving, by the node server, a reward payment based on an amount of communication between the node server and the two or more other node servers.

10. The method of claim 1 , further comprising:

determining, by the node server, that the consensus trust score indicates that the blockchain address is likely involved in fraudulent activity; and

sending a fraud alert to a fraud alert requesting device in response to determining that the consensus trust score indicates that the blockchain address is likely involved in fraudulent activity.

11. The method of claim 1 , further comprising:

acquiring, by the node server, new blockchain data for the blockchain address;

generating, by the node server, a new local node trust score for the blockchain address based on the new blockchain data, and

determining, at the node server, a new consensus trust score based on the new local node trust score.

12. The method of claim 1 , further comprising:

receiving a plurality of new additional local trust scores for the blockchain address from the two or more other node servers; and

determining, by the node server, a consensus trust score based on the local node trust score and the plurality of new additional local trust scores.

13. A node server comprising:

one or more memory components configured to store blockchain data for a blockchain address on a blockchain network, wherein the blockchain data includes a plurality of transactions for the blockchain address; and

one or more processing units configured to execute computer-readable instructions that, when executed, cause the node server to:

generate a local node trust score for the blockchain address based on the blockchain data for the blockchain address, wherein the local node trust score indicates a likelihood that the blockchain address is involved in fraudulent activity;

receive a plurality of additional local trust scores for the blockchain address from two or more other node servers of a plurality of node servers that collectively implement a decentralized trust network, wherein each respective additional local trust score is generated by a respective node server of the two or more other node servers;

determine a consensus trust score based on the local node trust score and the plurality of additional local trust scores, wherein the consensus trust score indicates a consensus value for the local node trust score among the node server and the two or more other node servers;

receive a trust request for the blockchain address from a decentralized application executed by the blockchain, the trust request indicating the blockchain address; and

send the consensus trust score for the blockchain address from the node server to the decentralized application.

14. The node server of claim 13 , wherein the computer-readable instructions, when executed, cause the node server to:

generate a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores;

identify outlier trust scores included in the trust score list;

remove the identified outlier trust scores; and

determine the consensus trust score based on the trust scores included in the trust score list after removing the identified outlier trust scores.

15. The node server of claim 13 , wherein the computer-readable instructions, when executed, cause the node server to:

generate a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores; and

determine the consensus trust score based on a weighted average of the local node trust score and the plurality of additional local trust scores in the trust score list.

16. The node server of claim 13 , wherein the computer-readable instructions, when executed, cause the node server to:

generate a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores;

determine whether the trust score list includes greater than a threshold number of trust scores, and

determine the consensus trust score based on the trust scores included in the trust score list when the trust score list includes greater than the threshold number of trust scores.

17. The node server of claim 13 , wherein the computer-readable instructions, when executed, cause the node server to:

generate a trust score list including a frequency distribution that includes the local node trust score and the plurality of additional local trust scores;

identify outlier trust scores included in the trust score list;

request new local trust scores in response to identifying the outlier trust scores from the two or more other node servers;

receive the new local trust scores; and

determine the consensus trust score based on the new local trust scores.

18. The node server of claim 13 , wherein the computer-readable instructions, when executed, cause the node server to:

determine a local candidate consensus trust score based on the local node trust score and the plurality of additional local trust scores; and

determine the consensus trust score based on the candidate consensus trust score.

19. The node server of claim 18 , wherein the computer-readable instructions, when executed, cause the node server to:

receive a plurality of additional candidate consensus trust scores for the blockchain address from the two or mor other node servers; and

determine the consensus trust score based on the local candidate consensus trust score and the plurality of additional candidate consensus trust scores.

20. The node server of claim 13 , wherein the computer-readable instructions, when executed, cause the node server to receive a reward payment based on calculation of at least one of the local node trust score or the consensus trust score.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2023
From: BRAVICK, ERIC; KUCHAR, DAVID; GARLAND, MALCOLM; DAHME, HARRISON; GROSSBLATT, DAVID MARC
To: CORAL PROTOCOL
Reel/Frame 062530/0988 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2023
From: CORAL PROTOCOL
To: STRONG FORCE TX PORTFOLIO 2018, LLC
Reel/Frame 062531/0137 →
Continuity (3)
Continuation 16429562 · Jun 3, 2019
Provisional Application 62680017 · Jun 4, 2018
Related Publication 20230177515A1 · Jun 8, 2023