IP Library Granted Patent US 12,524,759
Granted Patent B2
US 12,524,759 · App. 17/872,250 · Granted Jan 13, 2026

Systems and methods for transacting over a network

Inventors: Drummond Reed (Seattle, WA); Brent Zundel (American Fork, UT); Martin Mesrsmid (Prague, CZ); Allan Thomson (Pleasanton, CA)
Assignee: Avast Software s.r.o.
G06Q20/38215G06Q20/4014H04L9/3218H04L9/3247H04L63/126
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,524,759
App. No.
17/872,250
Granted
Jan 13, 2026
Kind
B2
Abstract

Systems and methods for transacting over a network. A first agent and a second agent are provided. The second agent is operable to transact with a third agent for use of a service, the third agent enabled to communicate with a fourth agent. The first agent is operable to communicate with the second agent to facilitate the transacting by the second agent with the third agent for the use of the service. The first agent is further operable to communicate with the fourth agent to facilitate the transacting by the second agent with the third agent for the use of the service.

Claims (100)

1 . A method for transacting over a network comprising:

receiving by a third agent operating on a third computing system from a second agent operating on a second computing system a request to initiate a use of a service;

transmitting by the third agent to the second agent a request for at least one data point that supports verification of an entity to initiate the use of the service;

receiving by the third agent from the second agent at least one requirement for fulfilling the at least one data point;

generating by the third agent a digitally signed transaction comprising a digital signature based on the at least one requirement;

transmitting by the third agent to the second agent the digitally signed transaction;

receiving by a first agent operating on a first computing system the digitally signed transaction from the second agent;

cryptographically verifying by the first agent the digital signature by applying a cryptographic key;

receiving by the third agent from the second agent a second verifiable proof, the second verifiable proof based on a locked credential provided by a sixth agent to the second agent, the second verifiable proof comprising the at least one data point;

receiving by the first agent from a fourth agent a first verifiable proof;

transmitting by the first agent to a fifth agent the first verifiable proof;

receiving by the first agent from the fifth agent an unlock signature for the locked credential;

transmitting by the first agent to the fourth agent the unlock signature;

receiving by the third agent from the fourth agent the unlock signature;

cryptographically unlocking by the third agent the second verifiable proof using the unlock signature; and

enabling by the third agent the use of the service via the network responsive to the unlocking of the second verifiable proof by the third agent.

2 . The method of claim 1 , further comprising updating by the first agent a ledger based on the digitally signed transaction received from the second agent.

3 . The method of claim 1 , further comprising:

transmitting by the second agent a request to the sixth agent for the locked credential responsive to the request for the at least one data point from the third agent;

receiving by the second agent the locked credential from the sixth agent; and

generating by the second agent the second verifiable proof based on the locked credential.

4 . The method of claim 3 , further comprising:

receiving by the second agent from the sixth agent a request for entity-identifying information;

acquiring by the second agent from a user the entity-identifying information; and

transmitting by the second agent to the sixth agent the entity-identifying information.

5 . The method of claim 3 , further comprising:

receiving by the fourth agent from the third agent the digitally signed transaction and the second verifiable proof; and

transmitting by the fourth agent to the third agent the unlock signature.

6 . The method of claim 5 , further comprising updating by the fourth agent a ledger based on the digitally signed transaction and the second verifiable proof.

7 . The method of claim 4 , wherein the entity-identifying information comprises at least one of a driver license, business license, passport, or social security card.

8 . The method of claim 3 , wherein the second verifiable proof comprises the locked credential.

9 . The method of claim 1 , wherein the at least one data point comprises at least one of a first name, last name, date of birth, credit card number, social security number, or passport number.

10 . The method of claim 1 , wherein the at least one requirement comprises at least one of a price, a service level agreement (“SLA”), or a policy.

11 . The method of claim 1 , wherein the entity comprises at least one of a user of the second agent or an organization associated with the user of the second agent.

12 . The method of claim 1 , wherein the first verifiable proof comprises a proof of payment.

13 . The method of claim 1 , further comprising:

transmitting by the second agent to the third agent the request to initiate the use of the service;

receiving by the second agent from the third agent the request for the at least one data point to initiate the use of the service;

transmitting by the second agent to the third agent the at least one requirement for fulfilling the at least one data point;

receiving by the second agent from the third agent the digitally signed transaction; and

transmitting by the second agent to the third agent the second verifiable proof.

14 . A digital system for transacting over a network comprising a first computing system comprising a first processor and a first computer readable medium comprising a first agent comprising first instructions executable by the first processor for operating on the first computing system, comprising a second computing system comprising a second processor and a second computer readable medium comprising a second agent comprising second instructions executable by the second processor for operating on the second computing system, and comprising a third computing system comprising a third processor and a third computer readable medium comprising a third agent comprising third instructions executable by the third processor for operating on the third computing system, the first agent operable to cause the first computing system to:

receive a digitally signed transaction from the second agent, the digitally signed transaction received by the second agent from the third agent and comprising a digital signature;

receive from a fourth agent a first verifiable proof;

transmit to a fifth agent the first verifiable proof;

receive from the fifth agent an unlock signature for a locked credential provided by a sixth agent to the second agent; and

transmit to the fourth agent the unlock signature;

the second agent operable to cause the second computing system to:

transmit to the third agent a request to initiate a use of a service;

receive from the third agent a request for at least one data point to initiate the use of the service;

transmit a request to the sixth agent for the locked credential responsive to the request for the at least one data point from the third agent;

receive the locked credential from the sixth agent;

transmit to the third agent at least one requirement for fulfilling the at least one data point;

receive from the third agent the digitally signed transaction;

generate a second verifiable proof based on the locked credential, the second verifiable proof comprising the at least one data point; and

transmit to the third agent the second verifiable proof; and

the third agent operable to cause the third computing system to:

generate the digitally signed transaction comprising the digital signature based on the at least one requirement;

receive from the fourth agent the unlock signature;

cryptographically unlock the second verifiable proof using the unlock signature; and

enable the use of the service via the network responsive to the unlocking of the second verifiable proof.

15 . The digital system of claim 14 , further comprising a fourth computing system comprising a fourth processor and a fourth computer readable medium comprising the fourth agent, the fourth agent comprising fourth instructions executable by the fourth processor for operating on the fourth computing system, and the fourth agent operable to cause the fourth computing system to:

receive from the third agent the digitally signed transaction and the second verifiable proof; and

transmit to the third agent the unlock signature.

16 . A method for transacting over a network comprising:

transmitting by a second agent operating on a second computing system to a third agent operating on a third computing system a request to initiate a use of a service;

receiving by the second agent from the third agent a request for at least one data point to initiate the use of the service;

transmitting by the second agent a request to a sixth agent operating on a sixth computing system for a locked credential responsive to the request for the at least one data point from the third agent;

receiving by the second agent the locked credential from the sixth agent;

transmitting by the second agent to the third agent at least one requirement for fulfilling the at least one data point;

generating by the third agent a digitally signed transaction comprising a digital signature based on the at least one requirement;

receiving by the second agent from the third agent the digitally signed transaction;

receiving by a first agent the digitally signed transaction from the second agent;

generating by the second agent a second verifiable proof based on the locked credential, the second verifiable proof comprising the at least one data point;

transmitting by the second agent to the third agent the second verifiable proof;

receiving by a fourth agent operating on a fourth computing system from the third agent the digitally signed transaction and the second verifiable proof;

receiving by the first agent from the fourth agent a first verifiable proof;

transmitting by the first agent to a fifth agent operating on a fifth computing system the first verifiable proof;

receiving by the first agent from the fifth agent an unlock signature for the locked credential;

transmitting by the first agent to the fourth agent the unlock signature;

transmitting by the fourth agent to the third agent the unlock signature;

cryptographically unlocking by the third agent the second verifiable proof using the unlock signature; and

enabling by the third agent the use of the service via the network responsive to the unlocking of the second verifiable proof by the third agent.

17 . A method for transacting over a network comprising:

transmitting by a second agent operating on a second computing system to a third agent operating on a third computing system a request to initiate a use of a service;

receiving by the second agent from the third agent a request for at least one data point that supports verification of an entity to initiate the use of the service;

transmitting by the second agent to the third agent at least one requirement for fulfilling the at least one data point;

receiving by the second agent from the third agent a digitally signed transaction;

receiving by a first agent operating on a first computing system the digitally signed transaction from the second agent, the digitally signed transaction received by the second agent from the third agent and comprising a digital signature;

cryptographically verifying by the first agent the digital signature by applying a cryptographic key;

receiving by the second agent from a sixth agent operating on a sixth computing system a locked credential comprising the at least one data point;

generating by the second agent a second verifiable proof based on the locked credential;

transmitting by the second agent to the third agent the second verifiable proof;

receiving by the first agent from a fourth agent operating on a fourth computing system a first verifiable proof;

transmitting by the first agent to a fifth agent operating on a fifth computing system the first verifiable proof;

receiving by the first agent from the fifth agent an unlock signature for the locked credential; and

transmitting by the first agent to the fourth agent the unlock signature;

receiving by the third agent from the fourth agent the unlock signature;

unlocking by the third agent the second verifiable proof using the unlock signature; and

enabling by the third agent the use of the service responsive to the unlocking of the second verifiable proof by the third agent.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2025
From: GEN DIGITAL AMERICAS S.R.O.
To: GEN DIGITAL INC.
Reel/Frame 071771/0767 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2025
From: AVAST SOFTWARE S.R.O.
To: GEN DIGITAL AMERICAS S.R.O.
Reel/Frame 071777/0341 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 7, 2022
From: REED, DRUMMOND; ZUNDEL, BRENT; MESRSMID, MARTIN; THOMSON, ALLAN
To: AVAST SOFTWARE S.R.O.
Reel/Frame 061013/0779 →
Continuity (1)
Related Publication 20240029061A1 · Jan 25, 2024
References Cited (65)
US 5825880A · Sudia et al. · 1998 [cited by applicant]
US 6327578B1 · Linehan · 2001 [cited by applicant]
US 8316237B1 · Felsher et al. · 2012 [cited by applicant]
US 10373158B1 · James et al. · 2019 [cited by applicant]
US 11139955B1 · So et al. · 2021 [cited by applicant]
US 11184395B1 · Novotny · 2021 [cited by examiner]
US 20020188490A1 · Kruse · 2002 [cited by applicant]
US 20030158820A1 · Mathur et al. · 2003 [cited by applicant]
US 20090300747A1 · Ahn · 2009 [cited by applicant]
US 20140281491A1 · Zaverucha · 2014 [cited by applicant]
US 20150095999A1 · Toth · 2015 [cited by applicant]
US 20190097812A1 · Toth · 2019 [cited by applicant]
US 20200127845A1 · Yang et al. · 2020 [cited by applicant]
US 20200136921A1 · Doshi et al. · 2020 [cited by applicant]
US 20200302441A1 · Collinge et al. · 2020 [cited by applicant]
US 20210014060A1 · Giorgiadis et al. · 2021 [cited by applicant]
US 20210287770A1 · Anderson et al. · 2021 [cited by applicant]
US 20220272085A1 · Novotny · 2022 [cited by examiner]
US 20220329653A1 · Govindarajan · 2022 [cited by examiner]
US 20230259922A1 · Rao et al. · 2023 [cited by applicant]
US 20240187238A1 · Pourtabatabaie et al. · 2024 [cited by applicant]
CN 109716373A · 2019 [cited by applicant]
EP 254234A1 · 2023 [cited by applicant]
EP 4254234A1 · 2023 [cited by applicant]
JP 2019525645 · 2019 [cited by applicant]
JP 2021111412 · 2021 [cited by applicant]
WO 2018031856 · 2018 [cited by applicant]
WO WO2019191213 · 2019 [cited by applicant]
WO WO2020233236 · 2020 [cited by applicant]
WO WO2022096126 · 2022 [cited by applicant]
WO WO2022102930 · 2022 [cited by applicant]
Phillip J. Windley, How Sovrin Works, Oct. 3, 2016, Sovrin.org (Year: 2016). [cited by examiner]
Dmitry Khovratovich; Jason Law, Sovrin: Digital Identities in the Blockchain Era, Dec. 2016, Sovrin.org (Year: 2016). [cited by examiner]
Daniel Hardman, How DIDs, Keys, Credentials, and Agents Work in Sovrin, Apr. 2018, Sovrin.org (Year: 2018). [cited by examiner]
Alex Preukschat; Drummond Reed, Self-Sovereign Identity: Decentralized digital identity and verifiable credentials, Manning, 2021. (Year: 2021). [cited by examiner]
International Search Report dated Oct. 24, 2023 for International Patent Application No. PCTUS2370319. [cited by applicant]
International Patent Application No. PCTUS2370319, filed Jul. 17, 2023. [cited by applicant]
Aries RFC 0046: Mediators and Relays, Daniel Hardman, Dec. 1, 2018 through Feb. 1, 2019, GitHub, https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0046-mediators-and-relays/README.md, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0478: Coprotocols, Daniel Hardman, Feb. 3, 2020 through May 19, 2020, GitHub, https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0478-coprotocols/README.md, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0075: Payment Decorators, Sam Curren et al., Apr. 22, 2019 through Jun. 11, 2019,GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/features/0075-payment-decorators, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0453: Issue Credential Protocol 2.0, Nikita Khateev et al., Mar. 23, 2020 through Apr. 15, 2021, GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/features/0453-issue-credential-v2, accessed Sep. 28,… [cited by applicant]
Aries RFC 0454: Present Proof Protocol 2.0, Nikita Khateev et al., May 27, 2020 through Apr. 15, 2021, GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/features/0454-present-proof-v2, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0004: Agents, Daniel Hardman, Nov. 1, 2017 “(approx, backdated)” through Jan. 15, 2019, GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0004-agents, accessed Sep. 14, 2023. [cited by applicant]
DIDComm Messaging v2.x Editor's Draft, Sam Curren et al., The Decentralized Identity Foundation, https://identity.foundation/didcomm-messaging/spec/, accessed Sep. 14, 2023. [cited by applicant]
Credential.md, Dmitry Khovratoavich et al., GitHub, https://github.com/sovrin-foundation/protocol/blob/master/themis/credential.md, accessed Sep. 14, 2023. [cited by applicant]
“Decentralized Identity and Verifiable Credentials”, Microsoft Security, Sep. 28, 2022 pp. 1-11. [cited by applicant]
Machine Translation of WO 2020233236 A1 (Year: 2020). [cited by applicant]
Office Action dated Feb. 13, 2025 for U.S. Appl. No. 18/066,213. [cited by applicant]
Reply dated Apr. 9, 2025 for U.S. Appl. No. 18/066,213. [cited by applicant]
Notice of Allowance dated May 30, 2025 for U.S. Appl. No. 18/066,213. [cited by applicant]
Office Action dated Mar. 21, 2025 for U.S. Appl. No. 18/063,284. [cited by applicant]
Reply dated May 23, 2025 for U.S. Appl. No. 18/063,284. [cited by applicant]
Notice of Allowance dated Jun. 20, 2025 for U.S. Appl. No. 18/063,284. [cited by applicant]
Office Action dated Nov. 14, 2024 for U.S. Appl. No. 18/052,752. [cited by applicant]
Updated Office Action dated Dec. 3, 2024 for U.S. Appl. No. 18/052,752. [cited by applicant]
Reply dated Jan. 22, 2025 for U.S. Appl. No. 18/052,752. [cited by applicant]
Notice of Allowance dated May 14, 2025 for U.S. Appl. No. 18/052,752. [cited by applicant]
Notice of Allowance dated Jun. 25, 2025 for U.S. Appl. No. 18/446,068. [cited by applicant]
Japanese Office Action dated Jul. 8, 2025 for Japanese Patent Application No. 2025-504595 including English translation of Office Action. [cited by applicant]
Machine translation of JP2019525645. [cited by applicant]
Machine translation of WO2022102930. [cited by applicant]
Machine translation of JP2021111412. [cited by applicant]
Notice of Allowance dated Mar. 6, 2025 for U.S. Appl. No. 18/446,068. [cited by applicant]
Machine translation of CN109716373A. [cited by applicant]
Machine Translation of EP 4254234 A1 (Year: 2023). [cited by applicant]