Generalized entity network translation (GENT)
Generalized Entity Network Translation provides new state of the art methodology for extending RKI techniques into a truly generalized framework capable of operating at exceptional levels of authenticity without the need for roots, certificate authorities, or other static points in an infrastructure. More astounding is its ability to create trusted authentic entity relationships that require no externally stored state outside of the shared context between discrete peers. The present invention provides, among other things, novel improvements to blockchain-derived systems and provides strong proof of ownership, renewal, roll-backs, and localized state and many blockchain systems more palatable choices for system integration.
1. A method for creating trusted authentic digital relationships in a computer network using a unique electronic entity identifier for an entity including, but not limited to a person, abstract entity, datum, good, or electronic device, the method comprising the steps of:
acquiring, at a device, public key data for an asymmetric key pair comprising a public key and a private key;
acquiring, at a device, a unique key identifier for the public key data;
acquiring, at a device, a set of one or more policies, wherein each policy from the set of one or more policies comprises a set of machine-evaluable rules comprising one or more unique electronic entity identifiers and/or the unique key identifier, and at least one logical operator or mathematical function, wherein a total number of identifiers from the one or more unique electronic entity identifiers and/or the unique key identifier in the policy is greater than one;
determining a unique electronic entity identifier for the entity, at a device, comprising a hash value of the set of one or more policies, wherein the determined unique electronic identifier represents a trusted digital identity of the entity for use in a computer network;
replacing one or more unique electronic entity identifiers within the set of one or more policies with numeric or logical values;
receiving, at a device, a message; and
authenticating the received message, wherein the step of authenticating comprises:
evaluating the set of one or more policies with the replaced one or more unique electronic entity identifiers to produce an affirmative or non-affirmative result.
2. The method of claim 1 , wherein the determined unique key identifier comprises a hash value of the public key data.
3. The method of claim 1 , further comprising the step of:
transmitting, at a device, the set of one or more policies to an other device.
4. The method of claim 3 , further comprising the steps of:
receiving, at the other device, the set of one or more policies;
calculating, at the other device, a hash value of the received set of one or more policies;
validating, at the other device, that the calculated hash value of the received set of one or more policies matches the unique electronic entity identifier; and
authenticating, at the other device, a received message signed using one or more private keys.
5. The method of claim 1 , further comprising the steps of:
authenticating the received message against one or more public keys represented by the unique key identifiers; and
when the received message is authenticated, replacing that unique key identifier with a numeral or logical value.
6. The method of claim 1 , further comprising the step of replacing one or the one or more unique electronic entity identifiers within a policy with at least one policy used to create the replaced unique electronic entity identifier.
7. The method of claim 1 , further comprising the steps of recursively replacing the one or more unique electronic entity identifiers within a policy with policies used to create the replaced one or more unique electronic entity identifiers.
8. The method of claim 1 , further comprising the step of replacing the unique electronic entity identifier with a new unique electronic entity identifier reflecting one or more updated or more accurate policies for the entity.
9. The method of claim 8 , wherein the replacement of the unique electronic entity identifier with a new unique electronic entity identifier is authorized by the set of one or more policies.
10. The method of claim 8 , wherein the replacement of the unique electronic entity identifier with a new unique electronic entity identifier is authorized through evaluation of the set of one or more policies.
11. A method for authenticating a unique entity identifier for an entity including, but not limited to a person, abstract entity, datum, good, or electronic device, method comprising the steps of:
receiving, at a device, a set of one or more policies, wherein each policy from the set of one or more policies comprises a set of machine-evaluable rules comprising one or more unique entity identifiers and/or unique key identifiers, and at least one logical operator or mathematical function, wherein a total number of identifiers from the one or more unique entity identifiers and/or unique key identifiers in the policy is greater than one, wherein each unique key identifier comprises a hash value of public key data associated with a asymmetric key pair comprising a public key and a private key;
receiving, at a device, a message signed using one or more private keys;
receiving, at a device, a unique entity identifier;
determining, at a device, a hash value of the received set of one or more policies;
validating, at any device, that the calculated hash value of the received set of one or more policies matches the unique entity identifier; and
authenticating, at a device, the received message, wherein the step of authenticating comprises:
replacing one or more unique electronic entity identifiers within the set of one or more policies with numeric or logical values; and
evaluating the set of one or more policies with the replaced one or more unique electronic entity identifiers to produce an affirmative or non-affirmative result.