IP Library › Granted Patent US 12,732,390
Granted Patent B2
US 12,732,390 · App. 18/337,937 · Granted Sep 8, 2026

Referencing documents using multiple blockchains

Inventors: Suresh Anisetti (Hyderabad, IN); Kanaka Srinivas Chikkala (Hyderabad, IN)
Assignee: Open Text SA ULC
H04L9/50H04L9/3236H04L9/3247G06F21/64H04L63/0428
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,732,390
App. No.
18/337,937
Filed
Jun 20, 2023
Granted
Sep 8, 2026
Kind
B2
Art Unit
2457
USPC
713/193
Abstract

Embodiments provide systems and methods for referencing documents using block chains. A computer-implemented method, for example, includes receiving a hash of a document, storing the hash of the document in a block of a protected block chain, generating a unique identifier for the block of the protected block chain and storing the unique identifier in a public block chain.

Claims (63)

1 . A method for referencing documents using block chains, comprising:

receiving a hash of a document;

storing the hash of the document in a block of a protected block chain;

generating a unique identifier for the block of the protected block chain; and

storing the unique identifier in a public block chain, wherein the unique identifier is stored in the public block chain after a private contract is executed among users to obtain a consensus on a content action.

2 . The method of claim 1 , further comprising:

validating the document, comprising:

retrieving the unique identifier from the block of the protected block chain based on the hash of the document;

determining whether the unique identifier is stored in the public block chain; and

when the unique identifier is determined to be stored in the public block chain, determining that the document is valid.

3 . The method of claim 2 , further comprising:

when the unique identifier is determined not to be stored in the public block chain, determining that the document is invalid.

4 . The method of claim 2 , wherein the unique identifier is stored in a block of the public block chain, validating the document further comprising:

retrieving a block index for the block of the protected block chain;

retrieving a block index for the block of the public block chain; and

determining that the document is valid further based on a comparison of the block index for the block of the protected block chain and the block index for the block of the public block chain.

5 . The method of claim 2 , wherein validating the document further comprises:

retrieving a number of blocks in the protected block chain;

retrieving a number of blocks in the public block chain; and

determining that the document is valid further based on a comparison of the number of blocks in the protected block chain and the number of blocks in the public block chain.

6 . The method of claim 2 , wherein the block of the protected block chain comprises a plurality of protected blocks and the public block chain comprises a plurality of public blocks, validating the document further comprising:

traversing the protected block chain and the public block chain to determine whether the unique identifier of each protected block is stored in a corresponding public block.

7 . The method of claim 2 , wherein the hash of the document is received from a document management system, further comprising:

returning a result that the document is valid to the document management system.

8 . The method of claim 7 , wherein receiving the hash of the document is in response to a first user of the document management system accessing the document.

9 . The method of claim 8 , wherein validating of the document is in response to a second user of the document management system accessing the document, wherein the first and the second user do not have access to the protected block chain.

10 . The method of claim 1 , wherein metadata is associated with the document, and wherein the method further comprises:

storing the metadata associated with the document in the block of the protected block chain; and

retrieving the metadata associated with the document from the block in the protected block chain based on the hash of the document.

11 . A system for referencing documents using block chains, comprising: a processor; and

a non-transitory memory coupled to the processor and comprising instructions executable by the processor for:

receiving a hash of a document;

storing the hash of the document in a block of a protected block chain;

generating a unique identifier for the block of the protected block chain; and

storing the unique identifier in a public block chain, wherein the unique identifier is stored in the public block chain after a private contract is executed among users to obtain a consensus on a content action.

12 . The system of claim 11 , the instructions further executable by the processor for:

validating the document, comprising:

retrieving the unique identifier from the block of the protected block chain based on the hash of the document;

determining whether the unique identifier is stored in the public block chain; and

when the unique identifier is determined to be stored in the public block chain, determining that the document is valid.

13 . The system of claim 12 , the instructions further executable by the processor for:

when the unique identifier is determined not to be stored in the public block chain, determining that the document is invalid.

14 . The system of claim 12 , wherein the unique identifier is stored in a block of the public block chain, validating the document further comprising:

retrieving a block index for the block of the protected block chain;

retrieving a block index for the block of the public block chain; and

determining that the document is valid further based on a comparison of the block index for the block of the protected block chain and the block index for the block of the public block chain.

15 . The system of claim 12 , wherein validating the document further comprises:

retrieving a number of blocks in the protected block chain;

retrieving a number of blocks in the public block chain; and

determining that the document is valid further based on a comparison of the number of blocks in the protected block chain and the number of blocks in the public block chain.

16 . The system of claim 12 , wherein the block of the protected block chain comprises a plurality of protected blocks and the public block chain comprises a plurality of public blocks, validating the document further comprising:

traversing the protected block chain and the public block chain to determine whether the unique identifier of each protected block is stored in a corresponding public block.

17 . The system of claim 12 , wherein the hash of the document is received from a document management system, the instructions further executable by the processor for:

returning a result that the document is valid to the document management system.

18 . The system of claim 17 , wherein receiving the hash of the document is in response to a first user of the document management system accessing the document.

19 . The system of claim 18 , wherein validating of the document is in response to a second user of the document management system accessing the document, wherein the first and the second user do not have access to the protected block chain.

20 . The system of claim 11 , wherein metadata is associated with the document, the instructions further executable by the processor for:

storing the metadata associated with the document in the block of the protected block chain; and

retrieving the metadata associated with the document from the block in the protected block chain based on the hash of the document.

21 . The method of claim 1 , further comprising:

storing the unique identifier for the block of the protected block chain in the protected block chain.

22 . The system of claim 11 , wherein the instructions are further executable by the processor for:

storing the unique identifier for the block of the protected block chain in the protected block chain.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 1, 2023
From: ANISETTI, SURESH; CHIKKALA, KANAKA SRINIVAS
To: OPEN TEXT SA ULC
Reel/Frame 064771/0544 →
Continuity (1)
Related Publication 20240430112A1 · Dec 26, 2024
References Cited (29)
US 10419225B2 · Deery · 2019 [cited by examiner]
US 11190360B2 · Wang · 2021 [cited by examiner]
US 11582044B2 · Zabetian · 2023 [cited by examiner]
US 11689374B1 · Harrison · 2023 [cited by examiner]
US 12683815B2 · Anisetti · 2026 [cited by applicant]
US 20170048216A1 · Chow · 2017 [cited by examiner]
US 20180025181A1 · Barinov · 2018 [cited by applicant]
US 20180219685A1 · Deery · 2018 [cited by examiner]
US 20190356493A1 · Fisher · 2019 [cited by examiner]
US 20200250168A1 · Xu · 2020 [cited by applicant]
US 20200250661A1 · Padmanabhan · 2020 [cited by examiner]
US 20210248272A1 · Shrinivasan · 2021 [cited by examiner]
US 20210328770A1 · Gaur · 2021 [cited by applicant]
US 20220094698A1 · Qiu · 2022 [cited by applicant]
US 20220164794A1 · Tai · 2022 [cited by applicant]
US 20220231834A1 · Das · 2022 [cited by examiner]
US 20220271956A1 · Hung · 2022 [cited by applicant]
US 20220278853A1 · Ben-Reuven · 2022 [cited by applicant]
US 20220292463A1 · Brook · 2022 [cited by examiner]
US 20220405260A1 · Snow · 2022 [cited by applicant]
US 20230082841A1 · Marsh · 2023 [cited by applicant]
US 20230096457A1 · Wang · 2023 [cited by applicant]
US 20230401526A1 · Hu · 2023 [cited by applicant]
US 20240193593A1 · Zheng · 2024 [cited by applicant]
US 20240405999A1 · Racz · 2024 [cited by examiner]
US 20240430112A1 · Anisetti · 2024 [cited by applicant]
Office Action issued for U.S. Appl. No. 18/337,906, mailed Apr. 23, 2025, 24 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 18/337,906, mailed Oct. 16, 2025, 25 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 18/337,906, mailed Mar. 2, 2026, 12 pages. [cited by applicant]