IP Library › Granted Patent US 12,463,823
Granted Patent B2
US 12,463,823 · App. 18/073,210 · Granted Nov 4, 2025

Systems and methods for digitally signed contracts with verifiable credentials

Inventors: James Fournier (Nicasio, CA); Victor Grey (Concord, CA)
Assignee: PORTABLE DATA CORPORATION
H04L9/3247H04L9/0825H04L9/3236H04L2209/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,463,823
App. No.
18/073,210
Granted
Nov 4, 2025
Kind
B2
Abstract

A method for seamlessly and automatically granting tailored permission for use and transference of internet data between databases with comprehensive consent is described. The method employs a graph language such as JSON-LD to integrate and employ cryptographically signed Information Sharing Agreements (ISAs) between parties. Data is serialized to be easily transferred between databases when appropriate permission is obtained. Granular data exchange under usage control contacts can be automated among any number of parties on the internet. As such, the method provides a means by which users may control not only what may be done with their data, but to what entity or entities the data may be transferred. Advertisements may then be served to the user according to his or her preferences as defined within a web or desktop app, which is then applied to all related ad publishers publishing to the domains visited by the user.

Claims (60)

1 . A link contract system, comprising:

one or more servers communicatively coupled with two or more communication devices;

wherein the one or more servers are configured to:

verify one or more verifiable credentials (VCs) of one of a first party and a second party;

facilitate communication of a proposed link contract, that includes the one or more VCs, between the parties;

generate a cryptographic hash of the proposed link contract;

add cryptographic signatures to the hash from the parties, thereby establishing a cryptographically signed hash which validates a digitally signed link contract with the verifiable credentials (DSLC-VC), wherein the cryptographic signatures are facilitated using private cryptographic keys and are one of generated and verified by computer system agents; and

provide the cryptographically signed hash to the parties as proof of agreement to the DSLC-VC;

wherein the DSLC-VC is machine readable and human readable.

2 . The system of claim 1 , further comprising a computer system agent of one of the parties facilitated by the one or more servers, wherein the computer system agent adds one of the cryptographic signatures to the hash.

3 . The system of claim 1 , wherein the first party and second party are identified by decentralized identifiers (DIDs), and wherein an exchange of the digital signatures generates or triggers one or more data events which provide non-repudiable audit records proving agreement to terms specified in the DSLC-VC.

4 . The system of claim 1 , wherein the system provides non-repudiable audit records of one or more subsequent data events occurring under terms of the DSLC-VC.

5 . The system of claim 1 , wherein the one or more servers govern, under terms of the DSLC-VC, an automated act occurring in response to one or more trigger events.

6 . The system of claim 1 , further comprising a computer system agent of a verifying party (verifying agent) facilitated by the one or more servers, and a computer system agent of the first party (first agent) facilitated by the one or more servers, wherein the system facilitates verification of an item—the item including one of a state, an attribute, data, sensor data, a document, and documentation—by the verifying agent receiving a decentralized identifier (DID), the first agent presenting a verifiable credential, signed by the first agent, representing the item to the verifying party or verifying agent, the verifying agent verifying the item and a DID of the first party, and the verifying agent countersigning the verifiable credential, the countersigned verifiable credential recorded as a data event by the one or more servers.

7 . The system of claim 1 , wherein the system facilitates multi-party interactions in which the first party enters the DSLC-VC with the second party, a computer system agent of the second party (second agent) signing with a key referenced by a decentralized identifier (DID), a computer system agent of the first party (first agent) signing the DSLC-VC to create a capability, the second agent transmitting the capability to one or more computer system agents of one or more third parties (one or more third agents), the one or more third agents confirming the existence of the DSLC-VC, and the one or more third agents and second agent executing one or more acts under terms of the DSLC-VC.

8 . The system of claim 1 , wherein the system records provenance of data relative to one or more third parties, each of the one or more third parties comprising part of a supply chain supplying a product or service to the first party, each of the one or more third parties signing the DSLC-VC.

9 . The system of claim 1 , wherein the one or more servers govern, under terms of the DSLC-VC, preferences of the first party, related to one of advertising and marketing communications, that are transmitted to the second party and to one or more third parties so that one of advertisements and marketing communications provided to the first party fall within the preferences of the first party.

10 . The system of claim 1 , wherein the DSLC-VC comprises a financial instrument and wherein the one or more servers are configured to automatically enforce terms of the financial instrument.

11 . The system of claim 1 , wherein the system facilitates accruing a plurality of digitally signed and auditable data events that are cleared to a separate financial system as a batch.

12 . The system of claim 1 , wherein the system facilitates a computer system agent acting as a fiduciary agent for secure file storage on behalf of one or more of the parties or a combination of the parties.

13 . The system of claim 1 , wherein the one or more servers govern, under terms of the DSLC-VC, an exchange of one of a commodity and a trade credit based on the commodity.

14 . The system of claim 1 , wherein the system facilitates a mutual credit system whereby debits and credits are created using data events associated with the DSLC-VC.

15 . The system of claim 1 , wherein the system facilitates verified testing by a decentralized identifier (DID) of the first party being provided to a testing device, by the testing device signing a record of test results using a DID of the testing device, and by the testing device sending the signed record to one of a computer system agent of the first party and a computer system agent of a third party.

16 . The system of claim 1 , wherein the system facilitates verified testing by a decentralized identifier (DID) of the first party being provided using a first of the communication devices, the system receiving through a second of the communication devices a signed record of test results associated with the DID of the first party, and the signed record being sent by the second of the communication devices to one of a computer system agent of the first party and a computer system agent of a third party.

17 . A link contract method, comprising:

communicatively coupling one or more servers with two or more communication devices, the two or more communication devices configured to facilitate digital communications between a first party and a second party; and

using the one or more servers:

verifying one or more verifiable credentials (VCs) of one of the first party and the second party;

facilitating communication of a proposed link contract, that includes the one or more VCs, between the parties;

generating a cryptographic hash of the proposed link contract;

adding cryptographic signatures to the hash from the parties, thereby establishing a cryptographically signed hash which validates a digitally signed link contract with the verifiable credentials (DSLC-VC), wherein the cryptographic signatures are facilitated using private cryptographic keys;

providing the cryptographically signed hash to the parties as proof of agreement to the DSLC-VC;

wherein the DSLC-VC is machine readable and human readable.

18 . The method of claim 17 , wherein the DSLC-VC comprises a legal contract having terms that are automatically enforced using the one or more servers.

19 . The method of claim 17 , further comprising the one or more servers facilitating verifiable provenance of an online published item by assigning a globally unique identifier to the published item, by identifying a decentralized identifier (DID) associated with an original content producer of the published item, and by identifying a DID associated with each republisher, in sequence, of the published item.

20 . The method of claim 19 , wherein the one or more servers facilitate sponsorship-based publication and sponsorship identification of the online published item by:

forming the DSLC-VC between a sponsor pledging financial support for the online published item and one of:

the original content producer; and

one or more of the republishers of the online published item;

assigning a DID to, or identifying a DID of, the sponsor; and

one of:

identifying the sponsor together with the online published item; and

providing a link with the online published item, the link navigating to a page identifying the sponsor;

wherein the verifiable provenance facilitates distribution of sponsorship revenue among the original content producer and the one or more republishers.

21 . The method of claim 19 , wherein the one or more servers facilitate subscription of the online published item by: assigning a DID to, or identifying a DID of, each subscriber of an online platform or system, the online platform or system providing access to the online published item; wherein the verifiable provenance facilitates distribution of subscription revenue, from one or more of the subscribers, to one of the original content producer and one or more of the republishers.

22 . The method of claim 19 , wherein the one or more servers facilitate consumer-based payments and sponsorship by: assigning a DID to, or identifying a DID of, each consumer user of an online platform or system, the online platform or system providing access to a plurality of online published items; facilitating one or more DSLC-VCs between the consumer users and a plurality of sponsors; facilitating payment, from one of a sponsor and a pool funded at least in part by the sponsor, to a digital wallet of one of the consumer users in response to the consumer user viewing content of the sponsor; and facilitating payment from the digital wallet to one of a content producer and a republisher of one of the online published items in response to input preferences of the consumer user.

23 . The method of claim 17 , wherein the one or more servers govern confidentiality of participants in an online group under terms of the DSLC-VC, the method further comprising the one or more servers generating a decentralized identifier (DID) for each participant and facilitating each participant sharing information and engaging in the group pseudonymously using its DID.

24 . The method of claim 23 , further comprising the one or more servers facilitating the formation of networks of online groups on an online platform or system, each network including a plurality of online groups, each online group having a DID assigned to it, the method further comprising the one or more servers managing a plurality of DSLC-VCs between and among the online groups and the networks, and facilitating each online group belonging to one or more networks.

25 . The method of claim 17 , further comprising facilitating voting or polling without revealing any personally identifiable information (PII) by: one or more computer system agents creating a voting or polling decentralized identifier (DID) for the first party; the one or more computer system agents creating one or more cryptographic hashes of attributes by which the first party is authenticated; and using these hashes as unique identifiers for the purpose of voting or polling.

26 . The method of claim 17 , further comprising transmitting a copy of the DSLC-VC to an audit service for recordation.

27 . A link contract method, comprising:

communicatively coupling one or more servers with two or more communication devices, the two or more communication devices configured to facilitate digital communications between a first party and a second party; and

using the one or more servers:

verifying one or more verifiable credentials (VCs) of one of the first party and the second party;

facilitating communication of a proposed link contract, that includes the one or more VCs, between computer system agents of the parties;

generating a cryptographic hash of the proposed link contract;

adding cryptographic signatures to the hash from the parties, thereby establishing a cryptographically signed hash which validates a digitally signed link contract with the verifiable credentials (DSLC-VC), wherein the cryptographic signatures are facilitated using private cryptographic keys;

providing the cryptographically signed hash to the parties as proof of agreement to the DSLC-VC; and

each computer system agent creating one or more entries using one or more decentralized identifiers (DIDs) pointing to a public key of a key pair;

wherein the DSLC-VC is machine readable and human readable.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 1, 2022
From: FOURNIER, JAMES; GREY, VICTOR
To: PORTABLE DATA CORPORATION
Reel/Frame 061945/0864 →
Continuity (6)
Continuation In Part 14681953 · Apr 8, 2015
Continuation In Part 16900971 · Jun 14, 2020
Continuation In Part 16772793
Provisional Application 62560714 · Sep 20, 2017
Provisional Application 62589334 · Nov 21, 2017
Related Publication 20230095123A1 · Mar 30, 2023
References Cited (35)
US 8228299B1 · Maloney · 2012 [cited by examiner]
US 20030177356A1 · Abela · 2003 [cited by examiner]
US 20050182773A1 · Feinsmith · 2005 [cited by applicant]
US 20070077981A1 · Hungate · 2007 [cited by examiner]
US 20100237151A1 · Bosselaers · 2010 [cited by examiner]
US 20120290427A1 · Reed et al. · 2012 [cited by applicant]
US 20130041755A1 · Ivanov et al. · 2013 [cited by applicant]
US 20130046582A1 · Ramer · 2013 [cited by examiner]
US 20130132547A1 · Reed · 2013 [cited by examiner]
US 20130246199A1 · Carlson · 2013 [cited by examiner]
US 20140020082A1 · Leggette · 2014 [cited by examiner]
US 20140279526A1 · Jackson · 2014 [cited by examiner]
US 20140316940A1 · Kirchenbauer · 2014 [cited by examiner]
US 20140370879A1 · Redding et al. · 2014 [cited by applicant]
US 20140373133A1 · Foresti · 2014 [cited by examiner]
US 20150134552A1 · Engels · 2015 [cited by examiner]
US 20160300223A1 · Grey et al. · 2016 [cited by applicant]
US 20190188701A1 · Parsons et al. · 2019 [cited by applicant]
US 20200058023A1 · Travizano et al. · 2020 [cited by applicant]
US 20200084051A1 · Bessonov et al. · 2020 [cited by applicant]
WO 2017147692 · 2017 [cited by applicant]
WO 2019070419 · 2019 [cited by applicant]
Sotos, J. et al., Blockchains for Data Sharing in Clinical Research: Trust in a Trustless World, Intel, Santa Clara, CA, USA, Blockchain Application Note #1, published May 2017 < URL: https://simplecore.intel.com/itpeer… [cited by applicant]
Arenas, A. E., “An Event-B approach to Data Sharing Agreements”, 8th International Conference on Integrated Formal Methods (IFM 2010), Nancy, France, published 2010 < URL: https://epubs.stfc.ac.uk/manifestation/48912666… [cited by applicant]
Matteucci, I. et al., “CNL4DSA: a controlled natural language for data sharing agreements”, Proceedings of the 2010 ACM Symposium on Applied Computing, published 2010 < URL: https://www.researchgate.net/profile/Marco-Sb… [cited by applicant]
“KERI: For every DID, a microledger,” published Oct. 19, 2020 by Decentralized Identity Foundation, available online at https://medium.com/decentralized-identity/keri-for-every-did-a-microledger-f9457fa80d2d, retrieved … [cited by applicant]
“Microledger, its importance in the world of crypto,” published Apr. 20, 2022, available online at https://www.coingabbar.com/en/crypto-blogs-details/microledger-its-importance-in-the-world-of-crypto, retrieved and last… [cited by applicant]
“Decentralized Identifiers (DIDs) v1.0: Core architecture, data model, and representations,” published online by W3C Jul. 19, 2022, available online at https://www.w3.org/TR/vc-data-model/, retrieved and last visited Ju… [cited by applicant]
JLINC Protocol Summary, published online by applicant at least as early as 2018, available online at https://jlinc.org/, retrieved and last visited Jun. 19, 2024. [cited by applicant]
Detailed JLINC Protocol, published online by applicant at least as early as Mar. 26, 2020, available online at https://protocol.jlinc.org/, retrieved and last visited Jun. 19, 2024. [cited by applicant]
JLINC Schema, published online by applicant at least as early as Feb. 12, 2019, available online at https://protocol.jlinc.org/schema/, retrieved and last visited Jun. 19, 2024. [cited by applicant]
Jlinc Did Method Specification, published online by applicant at least as early as Oct. 12, 2018, available online at https://did-spec.jlinc.org/, retrieved and last visited Jun. 19, 2024. [cited by applicant]
“Verifiable Credentials Data Model v1.1,” published online by W3C at least as early as Mar. 3, 2022, available online at https://www.w3.org/TR/vc-data-model/, retrieved and last visited Jun. 19, 2024. [cited by applicant]
“My first impressions of web3,” published online at least as early as Jan. 7, 2022, available online at https://moxie.org/2022/01/07/web3-first-impressions.html, retrieved and last visited Jun. 19, 2024. [cited by applicant]
“Hash Function,” Published online by Wikipedia at least as early as May 30, 2020, available online at https://en.wikipedia.org/w/index.php?title=Hash_function&oldid=959841170, retrieved and last visited Jun. 16, 2022. [cited by applicant]