IP Library Granted Patent US 11,568,415
Granted Patent B2
US 11,568,415 · App. 16/429,562 · Granted Jan 31, 2023

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 11,568,415
App. No.
16/429,562
Filed
Jun 3, 2019
Granted
Jan 31, 2023
Kind
B2
Art Unit
3694
USPC
705/75
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 (89)

1. A method comprising:

acquiring, at a node server, blockchain data for a blockchain address on a blockchain network, wherein the blockchain data includes a plurality of transactions for the blockchain address;

generating, at 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, from a plurality of remote servers, a plurality of additional local trust scores for the blockchain address;

determining, at 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 plurality of remote servers;

updating, by the node server, a consensus trust score ledger with the consensus trust score, the consensus trust score ledger being distributed across the node server and at least a subset of the plurality of remote servers;

receiving, at the node server, a trust request for the blockchain address from a requesting device; and

sending, from the node server, the consensus trust score for the specified blockchain address to the requesting device.

2. The method of claim 1 , further comprising:

generating, 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, at the node server, outlier trust scores included in the trust score list;

removing, at the node server, the identified outlier trust scores; and

determining, at 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, 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; and

determining, at 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, 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;

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

determining, at 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, 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, at the node server, outlier trust scores included in the trust score list;

requesting, from the plurality of remote servers, new local trust scores in response to identifying the outlier trust scores;

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

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

6. The method of claim 1 , further comprising:

determining, 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, at the node server, the consensus trust score based on the candidate consensus trust score.

7. The method of claim 6 , further comprising:

receiving, from the plurality of remote servers, a plurality of additional candidate consensus trust scores for the blockchain address; and

determining, at 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, at the node server, a reward payment based on calculation of at least one of the local node trust score and the consensus trust score.

9. The method of claim 1 , further comprising receiving, at the node server, a reward payment based on an amount of communication between the node server and the plurality of remote servers.

10. The method of claim 1 , further comprising:

determining, at 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, at the node server, new blockchain data for the blockchain address;

generating, at 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, from the plurality of remote servers, a plurality of new additional local trust scores for the blockchain address; and

determining, at 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 system 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 cause the one or more processing units 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, from a plurality of remote servers, a plurality of additional local trust scores for the blockchain address;

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 plurality of remote servers;

update a consensus trust score ledger with the consensus trust score, the consensus trust score ledger being distributed across the node server and at least a subset of the plurality of remote servers;

receive a trust request for the blockchain address from a requesting device;

send the consensus trust score for the specified blockchain address to the requesting device.

14. The system of claim 13 , wherein the one or more processing units are configured 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 system of claim 13 , wherein the one or more processing units are configured 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 system of claim 13 , wherein the one or more processing units are configured 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 system of claim 13 , wherein the one or more processing units are configured 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, from the plurality of remote servers, new local trust scores in response to identifying the outlier trust scores;

receive the new local trust scores; and

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

18. The system of claim 13 , wherein the one or more processing units are configured 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 system of claim 18 , wherein the one or more processing units are configured to:

receive, from the plurality of remote servers, a plurality of additional candidate consensus trust scores for the blockchain address; 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 system of claim 13 , wherein the one or more processing units are configured to receive a reward payment based on calculation of at least one of the local node trust score and the consensus trust score.

21. The system of claim 13 , wherein the one or more processing units are configured to receive a reward payment based on an amount of communication with the plurality of remote servers.

22. The system of claim 13 , wherein the one or more processing units are configured to:

determine that the consensus trust score indicates that the blockchain address is likely involved in fraudulent activity; and

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

23. The system of claim 13 , wherein the one or more processing units are configured to:

acquire new blockchain data for the blockchain address;

generate a new local node trust score for the blockchain address based on the new blockchain data; and

determine a new consensus trust score based on the new local node trust score.

24. The system of claim 13 , wherein the one or more processing units are configured to:

receive, from the plurality of remote servers, a plurality of new additional local trust scores for the blockchain address; and

determine a consensus trust score based on the local node trust score and the plurality of new additional local trust scores.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2021
From: INDISPUTABLE LABS, INC.; CORAL PROTOCOL, INC.; CORAL PROTOCOL
To: STRONG FORCE TX PORTFOLIO 2018, LLC
Reel/Frame 056080/0355 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 20, 2020
From: BRAVICK, ERIC; KUCHAR, DAVID; GARLAND, MALCOLM; DAHME, HARRISON; GROSSBLATT, DAVID MARC
To: CORAL PROTOCOL
Reel/Frame 053254/0368 →
Continuity (2)
Provisional Application 62680017 · Jun 4, 2018
Related Publication 20190370813A1 · Dec 5, 2019