IP Library Granted Patent US 12,632,862
Granted Patent B2
US 12,632,862 · App. 18/790,705 · Granted May 19, 2026

Cosigning using tokenized reputation scores

Inventors: Shannon Bruce Vosseller (San Francisco, CA); Andrew Chalkley (Milwaukie, OR)
Assignee: eBay Inc.
G06Q20/401G06Q20/3821G06Q2220/00
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,632,862
App. No.
18/790,705
Granted
May 19, 2026
Kind
B2
Abstract

Techniques are described, as implemented by computing devices, to control access to transactions through use of cosigning based on tokenized reputation scores. This is performed by leveraging a blockchain such that tokenized reputation scores are generated based on amounts of cryptographic reputation tokens associated with blockchain account addresses associated with applicant and co-signer service provider accounts. Transactional functionality is made available to an applicant service provider account having an insufficient tokenized reputation score by using a co-signer service provider account having a sufficient tokenized reputation score to at least partially back an obligation of the applicant service provider for a transaction.

Claims (55)

1 . A system comprising:

a transaction manager module implemented at least partially in hardware of a computing device to receive a first request to participate in a transaction using a first service provider account;

a reputation management module implemented at least partially in the hardware of the computing device to obtain a first reputation score for the first service provider account, the first reputation score generated based on a first amount of reputation tokens associated with a first blockchain account identifier associated with the first service provider account;

a reputation assessment module implemented at least partially in the hardware of the computing device to determine that the transaction is denied for the first service provider account by comparing the first reputation score with a threshold score associated with the transaction;

a transaction holding module implemented at least partially in the hardware of the computing device to place a hold on the transaction responsive to the determining that the transaction is denied for the first service provider account;

a cosigning management module implemented at least partially in the hardware of the computing device to receive an indication from a second service provider account usable to at least partially back an obligation of the first service provider account for the transaction;

a co-signer reputation management module implemented at least partially in the hardware of the computing device to obtain a second reputation score for the second service provider account, the second reputation score generated based on a second amount of reputation tokens associated with a second blockchain account identifier associated with the second service provider account;

an access determination module implemented at least partially in the hardware of the computing device to determine that the transaction is permitted by comparing the second reputation score with the threshold score associated with the transaction; and

an access control module implemented at least partially in the hardware of the computing device to, responsive to determining that the transaction is permitted, provide access by the computing device to the first service provider account to participate in the transaction.

2 . The system of claim 1 , wherein:

the first reputation score further is generated based on a first transactional history of the first blockchain account identifier associated with the first service provider account; and

the second reputation score is generated based on a second transactional history of the second blockchain account identifier associated with the second service provider account.

3 . The system of claim 1 , wherein the threshold score is selected from a plurality of threshold scores, each threshold score of the plurality of threshold scores corresponding to a type of transaction.

4 . The system of claim 1 , wherein the threshold score is generated based on a currency amount involved in the transaction.

5 . The system of claim 1 , wherein the determining that the transaction is denied further comprises determining that the first reputation score is lower than the threshold score.

6 . The system of claim 1 , wherein the reputation tokens are cryptographic utility tokens.

7 . The system of claim 1 , wherein the determining that the transaction is permitted further comprises comparing a combined reputation score of the first reputation score and the second reputation score with the threshold score associated with the transaction.

8 . The system of claim 1 , wherein the access determination module implemented at least partially in the hardware of the computing device to determine that the transaction is permitted further comprises configurations to:

transmit, to the second service provider account, a notification specifying a third amount of reputation tokens to be transferred as collateral for the first service provider account to participate in the transaction; and

determine that a transfer of the third amount of reputation tokens from the second blockchain account identifier is complete.

9 . The system of claim 8 , further comprising a collateral management module implemented at least partially in the hardware of the computing device to:

determine a successful completion of the transaction; and

return the collateral to the second blockchain account identifier associated with the second service provider account responsive to the determining of the successful completion of the transaction.

10 . The system of claim 8 , further comprising a collateral management module implemented at least partially in the hardware of the computing device to:

determine an unsuccessful completion of the transaction; and

withhold return of the collateral to the second blockchain account identifier associated with the second service provider account responsive to the determining of the unsuccessful completion of the transaction.

11 . The system of claim 9 , further comprising the collateral management module implemented at least partially in the hardware of the computing device to transfer a fourth amount of reputation tokens to the second blockchain account identifier associated with the second service provider account responsive to the determining of the successful completion of the transaction.

12 . A system comprising:

a transaction manager module implemented at least partially in hardware of a computing device to receive a request to participate in a transaction using a first service provider account;

a reputation management module implemented at least partially in the hardware of the computing device to determine a first amount of reputation tokens associated with a first blockchain account identifier associated with the first service provider account;

a reputation assessment module implemented at least partially in the hardware of the computing device to determine that the transaction is denied for the first service provider account by comparing the first amount of reputation tokens with a collateral associated with the transaction, wherein the collateral specifies a second amount of reputation tokens to be transferred as the collateral for the first service provider account to participate in the transaction;

a transaction holding module implemented at least partially in the hardware of the computing device to place a hold on the transaction responsive to the determining that the transaction is denied for the first service provider account;

a cosigning management module implemented at least partially in the hardware of the computing device to receive an indication from a second service provider account usable to at least partially back the collateral of the first service provider account for the transaction;

a collateral management module implemented at least partially in the hardware of the computing device to determine a transfer of the second amount of reputation tokens from at least a second blockchain account identifier associated with the second service provider account as the collateral; and

an access control module implemented at least partially in the hardware of the computing device to provide access to the first service provider account to participate in the transaction.

13 . The system of claim 12 , wherein the collateral is based on at least a first reputation score affiliated with the first service provider account, the first reputation score generated based on the first amount of reputation tokens associated with the first blockchain account identifier associated with the first service provider account.

14 . The system of claim 12 , wherein the collateral is based on a currency amount involved in the transaction.

15 . The system of claim 12 , further comprising the collateral management module implemented at least partially in the hardware of the computing device to:

determine a successful completion of the transaction; and

responsive to the determining of the successful completion of the transaction, return the collateral to at least the second blockchain account identifier that transferred the second amount of reputation tokens as the collateral.

16 . The system of claim 12 , further comprising the collateral management module implemented at least partially in the hardware of the computing device to:

determine an unsuccessful completion of the transaction; and

withhold, responsive to the determining of the unsuccessful completion of the transaction, return of the second amount of reputation tokens of the collateral to at least the second blockchain account identifier that transferred the second amount of reputation tokens as the collateral.

17 . The system of claim 15 , further comprising the collateral management module implemented at least partially in the hardware of the computing device to, responsive to the determining of the successful completion of the transaction, transfer a third amount of reputation tokens as a reputation reward to the second blockchain account identifier associated with the second service provider account.

18 . The system of claim 17 , further comprising a reputation manager module implemented at least partially in the hardware of the computing device to generate a fourth reputation score affiliated with the second service provider account based on a fourth amount of reputation tokens associated with the second blockchain account identifier associated with the second service provider account, the fourth amount of reputation tokens including the third amount of reputation tokens transferred as the reputation reward.

19 . A system comprising:

a transaction manager module implemented at least partially in hardware of a computing device to receive a first request to receive a first request to participate in a transaction using a first service provider account;

a reputation management module implemented at least partially in the hardware of the computing device to obtain a first reputation score for the first service provider account, the first reputation score generated based on a first amount of reputation tokens associated with a first blockchain account identifier associated with the first service provider account;

a reputation assessment module implemented at least partially in the hardware of the computing device to determine that the transaction is denied for the first service provider account by comparing the first reputation score with a threshold score associated with the transaction;

a transaction holding module implemented at least partially in the hardware of the computing device to place a hold on the transaction responsive to the determining that the transaction is denied for the first service provider account;

a cosigning management module implemented at least partially in the hardware of the computing device to receive an indication from a second service provider account usable to at least partially back an obligation of the first service provider account for the transaction;

a co-signer reputation management module implemented at least partially in the hardware of the computing device to obtain a second reputation score for the second service provider account, the second reputation score generated based on a second amount of reputation tokens associated with a second blockchain account identifier associated with the second service provider account;

an access determination module implemented at least partially in the hardware of the computing device to determine that the transaction is permitted by comparing the second reputation score and the first reputation score with the threshold score associated with the transaction; and

an access control module implemented at least partially in the hardware of the computing device to, responsive to determining that the transaction is permitted, provide access to the first service provider account to participate in the transaction.

20 . The system of claim 19 , wherein the threshold score is based on a currency amount involved in the transaction.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2024
From: VOSSELLER, SHANNON BRUCE; CHALKLEY, ANDREW
To: EBAY, INC.
Reel/Frame 068165/0127 →
Continuity (2)
Continuation 17518820 · Nov 4, 2021
Related Publication 20240394704A1 · Nov 28, 2024
References Cited (75)
US 8194550B2 · Shorey et al. · 2012 [cited by applicant]
US 8719154B2 · Shastry et al. · 2014 [cited by applicant]
US 10268829B2 · Roets et al. · 2019 [cited by applicant]
US 10546296B2 · Narasimhan et al. · 2020 [cited by applicant]
US 11133936B1 · Branton · 2021 [cited by applicant]
US 11165787B2 · Sloane et al. · 2021 [cited by applicant]
US 11392947B1 · Prasad et al. · 2022 [cited by applicant]
US 11449819B2 · Heath et al. · 2022 [cited by applicant]
US 11652604B2 · Gundavelli et al. · 2023 [cited by applicant]
US 11748746B2 · Pillai et al. · 2023 [cited by applicant]
US 11748793B2 · Vosseller et al. · 2023 [cited by applicant]
US 11861400B2 · Wentz · 2024 [cited by applicant]
US 11922453B2 · Vlahovic et al. · 2024 [cited by applicant]
US 11983610B2 · Poletti et al. · 2024 [cited by applicant]
US 12100001B2 · Vosseller et al. · 2024 [cited by applicant]
US 12154151B2 · Vosseller et al. · 2024 [cited by applicant]
US 20060184440A1 · Britti et al. · 2006 [cited by applicant]
US 20090006115A1 · Schwarz · 2009 [cited by applicant]
US 20100201543A1 · Shorey et al. · 2010 [cited by applicant]
US 20110106643A1 · Berkowitz · 2011 [cited by applicant]
US 20140236749A1 · Yang · 2014 [cited by applicant]
US 20150356630A1 · Hussain · 2015 [cited by applicant]
US 20170011395A1 · Pillai et al. · 2017 [cited by applicant]
US 20170140394A1 · Cao et al. · 2017 [cited by applicant]
US 20170300912A1 · Narasimhan et al. · 2017 [cited by applicant]
US 20170364920A1 · Anand · 2017 [cited by applicant]
US 20190095631A1 · Roets et al. · 2019 [cited by applicant]
US 20190303807A1 · Gueye · 2019 [cited by applicant]
US 20190312734A1 · Wentz et al. · 2019 [cited by applicant]
US 20200027089A1 · Kuchar et al. · 2020 [cited by applicant]
US 20200034457A1 · Brody et al. · 2020 [cited by applicant]
US 20200052917A1 · Corral et al. · 2020 [cited by applicant]
US 20200067696A1 · Sarin · 2020 [cited by applicant]
US 20200162261A1 · Iyer · 2020 [cited by applicant]
US 20200219150A1 · Johnston · 2020 [cited by applicant]
US 20200313897A1 · Heath et al. · 2020 [cited by applicant]
US 20200410460A1 · Nissan et al. · 2020 [cited by applicant]
US 20210064780A1 · Riedel et al. · 2021 [cited by applicant]
US 20210067518A1 · Sloane et al. · 2021 [cited by applicant]
US 20210160082A1 · Wang · 2021 [cited by applicant]
US 20210174247A1 · Poletti et al. · 2021 [cited by applicant]
US 20210176340A1 · Rose et al. · 2021 [cited by applicant]
US 20210390531A1 · Voorhees et al. · 2021 [cited by applicant]
US 20220150050A1 · Gundavelli et al. · 2022 [cited by applicant]
US 20230103398A1 · Vosseller et al. · 2023 [cited by applicant]
US 20230108817A1 · Vosseller et al. · 2023 [cited by applicant]
US 20230108983A1 · Vosseller et al. · 2023 [cited by applicant]
US 20230113795A1 · Vlahovic et al. · 2023 [cited by applicant]
US 20230135294A1 · Vosseller et al. · 2023 [cited by applicant]
US 20230360097A1 · Vosseller et al. · 2023 [cited by applicant]
US 20240169388A1 · Vlahovic et al. · 2024 [cited by applicant]
WO WO2015191741 · 2015 [cited by applicant]
U.S. Appl. No. 17/492,924, Oct. 31, 2024 , “Examiner's Answer”, U.S. Appl. No. 17/492,924, Oct. 31, 2024, 10 pages. [cited by applicant]
U.S. Appl. No. 18/223,232, Nov. 1, 2024 , “Corrected Notice of Allowability”, U.S. Appl. No. 18/223,232, Nov. 1, 2024, 11 pages. [cited by applicant]
“A group of experts intends to sell the Colosseum . . . in digital format”, Translated by ContentEngine LLC. CE Noticias Financieras, English ed. [Miami], Jul. 27, 2021, 2 pages. [cited by applicant]
“Blockchain Video Platform Viuly.io Connects to Ethereum Mainnet”, Cision, PR Newswire [retrieved Mar. 28, 2023]. Retrieved from the Internet <https://www.prnewswire.com/news-releases/blockchain-video-platform-viulyio-c… [cited by applicant]
“The genesis, vision and what makes Decentralized Reputation System”, M2 Presswire [Coventry] Retrieved from the Internet <http://www.m2.com>, Jun. 1, 2018, 3 pages. [cited by applicant]
U.S. Appl. No. 17/492,894, Jun. 22, 2023, , “Corrected Notice of Allowability”, U.S. Appl. No. 17/492,894, Jun. 22, 2023, 11 pages. [cited by applicant]
U.S. Appl. No. 17/492,894, Mar. 28, 2023, , “Non-Final Office Action”, U.S. Appl. No. 17/492,894, Mar. 28, 2023, 26 pages. [cited by applicant]
U.S. Appl. No. 17/492,894, Jun. 7, 2023, , “Notice of Allowance”, U.S. Appl. No. 17/492,894, Jun. 7, 2023, 13 pages. [cited by applicant]
U.S. Appl. No. 17/492,924, Apr. 11, 2024, , “Final Office Action”, U.S. Appl. No. 17/492,924, Apr. 11, 2024, 20 pages. [cited by applicant]
U.S. Appl. No. 17/492,924, Aug. 15, 2023, , “Final Office Action”, U.S. Appl. No. 17/492,924, Aug. 15, 2023, 24 pages. [cited by applicant]
U.S. Appl. No. 17/492,924, Dec. 20, 2023, , “Non-Final Office Action”, U.S. Appl. No. 17/492,924, Dec. 20, 2023, 22 pages. [cited by applicant]
U.S. Appl. No. 17/492,924, Mar. 14, 2023, , “Non-Final Office Action”, U.S. Appl. No. 17/492,924, Mar. 14, 2023, 24 pages. [cited by applicant]
U.S. Appl. No. 17/518,820, Jan. 19, 2024, , “Non-Final Office Action”, U.S. Appl. No. 17/518,820, Jan. 19, 2024, 17 pages. [cited by applicant]
U.S. Appl. No. 17/518,820, Jun. 6, 2024, , “Notice of Allowance”, U.S. Appl. No. 17/518,820, Jun. 6, 2024, 8 pages. [cited by applicant]
U.S. Appl. No. 18/223,232, Sep. 25, 2024, , “Notice of Allowance”, U.S. Appl. No. 18/223,232, Sep. 25, 2024, 16 pages. [cited by applicant]
Abdo, et al., “Permissionless reputation-based consensus algorithm for blockchain”, Internet Technology Letters, 3(3), e151, Retrieved from Internet URL: https://doi.org/10.1002/it12.151, Apr. 10, 2020, 6 Pages. [cited by applicant]
Ahn, Jaehong et al., “A Model for Deriving Trust and Reputation on Blockchain-Based e-Payment System”, Applied Sciences, vol. 9, No. 24 [retrieved Mar. 28, 2023]. Retrieved from the Internet <https://doi.org/10.3390/app… [cited by applicant]
Eckhardt, Giana M. , “Playing the Trust Game Successfully in the Reputation Economy”, Volume & Issue: vol. 12, No. 2 [retrieved Mar. 28, 2023]. Retrieved from the Internet <https://doi.org/10.2478/nimmir-2020-0011>, Oct… [cited by applicant]
Khairuddin, Irni E. , “Understanding and Designing for Trust in Bitcoin Blockchain”, Lancaster University, School of Computing and Communications [retrieved Mar. 28, 2023]. Retrieved from the Internet <https://core.ac.u… [cited by applicant]
Levin, Richard B. et al., “Bitcoin Investment Vehicles Beware—The SEC is Watching”, BakerHostetler Blog, Baker & Hostetler LLP [retrieved Jun. 7, 2023]. Retrieved from the Internet <https://www.bakerlaw.com/alerts/bitco… [cited by applicant]
Brown, et al., “Reputation in Online Auctions: The Market for Trust”, California Management Review, vol. 49, No. 1, 2006, 22 pages. [cited by applicant]
Notice of Allowance issued in U.S. Appl. No. 17/492,924, mailed Dec. 30, 2025, 10 pages. [cited by applicant]
Sun, et al., “A Privacy-Preserving and Robust Reputation System Based on Blockchain”, 2019 IEEE Conference on Parallel and Distribution Processing with Applications, Big Data & Cloud Computing, Sustainable Computing & C… [cited by applicant]
Cited By (1)
US 12,682,381