Granted Patent B2

US 12,380,182 · App. 17/710,866 · Granted Aug 5, 2025

Inventors: Stephane Savanah (London, GB); Craig Steven Wright (London, GB)

Assignee: NCHAIN LICENSING AG

G06F21/121G06F8/65G06F16/152G06F16/1834G06F21/105G06F21/12G06F21/51G06F21/57G06F21/602G06F21/6281G06F21/64H04L9/0637H04L9/0643H04L9/0841H04L9/3236H04L9/3247H04L9/3263H04L9/3265H04L63/0435H04L63/061H04L63/0823H04L67/104G06F21/107G06F2221/2107H04L9/50H04L67/1065H04L2209/56

Abstract

Claims (46)

1. A computer-implemented method comprising:

determining a data (D1) associated with a computer software, installed on a processing device associated with a second user (U2), the data (D1) comprising a license, the license comprising a second public key (P2), and the computer software comprising an indicator of a location of the computer software;

determining a first hash value (H1) of the computer software;

determining a second hash value (H2) based on the data (D1) and the computer software, the indicator comprising a link to a computer-based repository;

sending, over a communications network, the data (D1), the first hash value (H1) and the second hash value (H2) to an entry for storage in the computer-based repository wherein the second hash value (H2) is a key of a key-value pair, and the data (D1) and the first hash value (H1) are a value in the key-value pair;

determining a subsequent transaction on a peer-to-peer distributed ledger, wherein the subsequent transaction comprises a redeem script for spending an output of a transaction, and wherein the redeem script comprises the second hash value (H2) and a second user public key (PU2);

in response to the redeem script included in the subsequent transaction becoming visible on the peer-to-peer distributed ledger, retrieving the second hash value (H2) from the redeem script included in the subsequent transaction, as the key of the key-value pair;

determining the second user public key (PU2) associated with the second user (U2) from the redeem script included in the subsequent transaction stored on the peer-to-peer distributed ledger;

retrieving the value of the key-value pair associated with the entry stored in the computer-based repository based on the retrieved key;

determining the second public key (P2) associated with the second user (U2) based on the retrieved value;

comparing the second user public key (PU2) and the second public key (P2); and

verifying ownership of the computer software based on the comparing of the second user public key (PU2) and the second public key (P2).

2. The method of claim 1 , wherein comparing the second user public key (PU2) and the second public key (P2) comprises determining whether the second user public key (PU2) and the second public key (P2) match.

3. The method of claim 1 , wherein the computer software comprises a header and a body.

4. The method of claim 3 , wherein the header comprises a hash value of the body of the computer software.

5. The method of claim 3 , wherein the header further comprises the second hash value (H2) of a data associated with the computer software and the license.

6. The method of claim 3 , wherein the body of the computer software comprises an executable of the computer software.

7. The method of claim 5 , wherein before determining the second user public key (PU2), the method comprises installing an executable of the computer software on a processing device associated with the second user (U2).

8. The method of claim 1 , further comprising executing instructions of an executable of the computer software on a processing device associated with the second user (U2) after verifying the ownership of the computer software.

9. The method of claim 1 , wherein before executing instructions of a decrypted executable of the computer software, the method further comprises:

determining an activation key (AK) from the second user (U2); and

executing the instructions of the decrypted executable of the computer software based on the activation key (AK) on a processing device associated with the second user (U2).

10. A non-transitory computer-readable storage medium storing thereon executable instructions that, as a result of being executed by one or more processors, cause the one or more processors to:

determine a data (D1) associated with a computer software, installed on a processing device associated with a second user (U2), the data (D1) comprising a license, the license comprising a second public key (P2), and the computer software comprising an indicator of a location of the computer software, the indicator comprising a link to a computer-based repository;

determine a first hash value (H1) of the computer software;

determine a second hash value (H2) based on the data (D1) and the computer software;

send, over a communications network, the data (D1), the first hash value (H1) and the second hash value (H2) to an entry for storage in the computer-based repository, wherein the second hash value (H2) is a key of a key-value pair, and the data (D1) and the first hash value (H1) are a value in the key-value pair;

determine a subsequent transaction on a peer-to-peer distributed ledger, wherein the subsequent transaction comprises a redeem script for spending an output of a transaction, and wherein the redeem script comprises the second hash value (H2) and a second user public key (PU2);

in response to the redeem script included in the subsequent transaction becoming visible on the peer-to-peer distributed ledger, retrieving the second hash value (H2) from the redeem script included in the subsequent transaction, as the key of the key-value pair;

determine the second user public key (PU2) associated with the second user (U2) from the redeem script included in the subsequent transaction stored on the peer-to-peer distributed ledger;

retrieve the value of the key-value pair associated with the entry stored in the computer-based repository based on the retrieved key;

determine the second public key (P2) associated with the second user (U2) based on the retrieved value;

compare the second user public key (PU2) and the second public key (P2); and

verify ownership of the computer software based on the comparing of the second user public key (PU2) and the second public key (P2).

11. A system comprising at least one computing device associated with a node on a peer-to-peer network of nodes and configured with a processor and memory, the memory including instructions that, upon execution by the processor, cause the system to:

determine a data (D1) associated with a computer software, installed on a processing device associated with a second user (U2), the data (D1) comprising a license, the license comprising a second public key (P2), and the computer software comprising an indicator of a location of the computer software, the indicator comprising a link to a computer-based repository;

determine a first hash value (H1) of the computer software;

determine a second hash value (H2) based on the data (D1) and the computer software;

send, over a communications network, the data (D1), the first hash value (H1) and the second hash value (H2) to an entry for storage in the computer-based repository wherein the second hash value (H2) is a key of a key-value pair and the data (D1) and the first hash value (H1) are a value in the key-value pair;

determine a subsequent transaction on a peer-to-peer distributed ledger, wherein the subsequent transaction comprises a redeem script for spending an output of a transaction, and wherein the redeem script comprises the second hash value (H2) and a second user public key (PU2);

in response to the redeem script included in the subsequent transaction becoming visible on the peer-to-peer distributed ledger, retrieve the second hash value (H2) from the redeem script included in the subsequent transaction, as the key of the key-value pair;

determine the second user public key (PU2) associated with the second user (U2) from the redeem script included in the subsequent transaction stored on the peer-to-peer distributed ledger;

retrieving the value of the key-value pair associated with the entry stored in the computer-based repository based on the retrieved key;

determine the second public key (P2) associated with the second user (U2) based on the retrieved value;

compare the second user public key (PU2) and the second public key (P2); and

verify ownership of the computer software based on the compare of the second user public key (PU2) and the second public key (P2).

Assignments (5)

Priority Claims (3)

Continuity (2)

References Cited (105)