Consensus-based voting for network member identification employing blockchain-based identity signature mechanisms

1. A method for operating a communication network, comprising:

validating a first member of the communication network by inserting a first validated member identity hash block (MIHB) based on a network identifier for the first member into a master blockchain ledger;

obtaining a revised network identifier for the first member;

generating a revision score for the revised network identifier, comprising counting a number of attributes of the first member that changed between the network identifier and the revised network identifier; and

in response to determining that the revision score satisfies a major revision threshold:

obtaining a first vote value regarding the revised network identifier;

generating a first trust score based on the first vote value; and

revalidating the first member, in response to the first trust score satisfying a trust score threshold, by inserting a second validated MIHB based on the revised network identifier into the master blockchain ledger.

2. The method of claim 1 , further comprising:

storing, in a relational ledger, a first un-validated MIHB comprising the network identifier;

generating the first validated MIHB based on the first un-validated MIHB;

storing, in the relational ledger, a second un-validated MIHB comprising the revised network identifier; and

generating the second validated MIHB based on the second un-validated MIHB.

3. The method of claim 1 , wherein:

the first vote value is associated with a communication session between a first user of the first member and a second user of a second member of the communication network,

the first vote value is obtained from the second user, and

generating the first trust score comprises assigning a weight to the first vote value based on the second user.

4. The method of claim 3 , wherein the weight is based on one or more of a distance between the first user and the second user, a voting frequency of the second user, a duration of the communication session, and how long the second user has been associated with the second member and how long the second member has been validated.

5. The method of claim 1 , further comprising:

generating a second trust score for a second member;

validating the second member, in response to the second trust score satisfying the trust score threshold, by inserting a third validated MIHB for the second member into the master blockchain ledger;

obtaining a second vote value for the second member after validating the second member;

updating the second trust score based on the second vote value; and

un-validating the second member, in response to the second trust score no longer satisfying the trust score threshold, by inserting a block into the master blockchain ledger indicating the second member is un-validated.

6. The method of claim 5 , further comprising:

transmitting a copy of the master blockchain ledger to a member node of the communication network after un-validating the second member, wherein the master blockchain ledger is located in a master node of the communication network; and

classifying, by the member node and based on the copy, a suspect user associated with the second member as a threat after un-validating the second member.

7. The method of claim 1 , further comprising:

extracting, an internet protocol (IP) address or MAC address of a computing device from a member block of a member blockchain ledger of the first member, and an identity attribute of the first member from a network packet sent by the computing device;

classifying the computing device as trusted in response to:

determining that the first member is validated based on the first validated MIHB in the master blockchain ledger comprising the identity attribute extracted from the network packet; and

determining that the member blockchain ledger comprises the IP address or MAC address of the computing device extracted from the network packet by traversing the member blockchain ledger; and

participating in a communication session with the computing device in response to the computing device being classified as trusted.

8. A system, comprising:

a memory; and

a computer processor, coupled to the memory, and configured to:

validate a first member of a communication network by inserting a first validated member identity hash block (MIHB) based on a network identifier for the first member into a master blockchain ledger;

obtain a revised network identifier for the first member;

generate a revision score for the revised network identifier, comprising counting a number of attributes of the first member that changed between the network identifier and the revised network identifier; and

in response to determining that the revision score satisfies a major revision threshold:

obtain a first vote value regarding the revised network identifier;

generate a first trust score based on the first vote value; and

revalidate the first member, in response to the first trust score satisfying a trust score threshold, by inserting a second validated MIHB based on the revised network identifier into the master blockchain ledger.

9. The system of claim 8 , wherein:

the first vote value is associated with a communication session between a first user of the first member and a second user of a second member of the communication network,

the first vote value is obtained from the second user, and to generate the first trust score, the computer processor is configured to assign a weight to the first vote value based on the second user.

10. The system of claim 9 , wherein the weight is based on: a distance between the first user and the second user, a voting frequency of the second user, or a duration of the communication session.

11. The system of claim 8 , wherein the computer processor is further configured to:

generate a second trust score for a second member;

validate the second member, in response to the second trust score satisfying the trust score threshold, by inserting a third validated MIHB for the second member into the master blockchain ledger;

obtain a second vote value for the second member after validating the second member;

update the second trust score based on the second vote value; and

un-validate the second member, in response to the second trust score no longer satisfying the trust score threshold, by inserting a block into the master blockchain ledger indicating the second member is un-validated.

12. The system of claim 8 , wherein the computer processor is further configured to:

extract an internet protocol (IP) address or MAC address of a computing device from a member block of a member blockchain ledger of the first member, and an identity attribute of the first member from a network packet sent by the computing device;

determine that the first member is validated based on the first validated MIHB in the master blockchain ledger comprising the identity attribute extracted from the network packet;

determine that the member blockchain ledger comprises the IP address or MAC address of the computing device extracted from the network packet;

based on the determinations, classify the computing device as trusted; and

participate in a communication session with the computing device in response to the computing device being classified as trusted.

13. The system of claim 8 , wherein the computer processor is further configured to:

store in a relational ledger, a first un-validated MIHB comprising the network identifier;

generate the first validated MIHB based on the first un-validated MIHB;

store in the relational ledger, a second un-validated MIHB comprising the revised network identifier; and

generate the second validated MIHB based on the second un-validated MIHB.

14. The system of claim 11 , wherein the computer processor is further configured to:

transmit a copy of the master blockchain ledger to a member node of the communication network after un-validating the second member, wherein the master blockchain ledger is located in a master node of the communication network; and

classify, based on the copy, a suspect user associated with the second member as a threat after un-validating the second member.

15. A system, comprising:

a master blockchain ledger associated with a communication network;

a trust tabulation engine configured to:

generate a trust score for a first member of the communication network;

obtain a plurality of vote values for the first member; and

update the trust score for the first member based on the plurality of vote values;

a master blockchain controller configured to:

compare, before the trust score is updated, the trust score with a trust score threshold;

validate the first member, in response to the trust score satisfying the trust score threshold, by inserting a validated member identity hash block (MIHB) for the first member into the master blockchain ledger;

compare, after the trust score is updated, the trust score with the trust score threshold; and

un-validate the first member, in response to the trust score no longer satisfying the trust score threshold, by inserting a block into the master blockchain ledger indicating the first member is un-validated.

16. The system of claim 15 , further comprising:

a relational ledger configured to store an un-validated MIHB comprising a network identifier for the first member,

wherein the validated MIHB for the first member is generated based on the un-validated MIHB for the first member, and

wherein the master blockchain ledger, the master blockchain controller, the trust tabulation engine, and the relational ledger are located in a master node of the communication network.

17. The system of claim 15 , further comprising:

a member node associated with a second member of the communication network and comprising:

a member blockchain ledger; and

a member blockchain controller configured to:

insert a first member block comprising identity information of a first user into the member blockchain ledger; and

insert a second member block indicating a second user has departed the second member into the member blockchain ledger.

18. The system of claim 17 , wherein the second member is validated, wherein the first user is classified as trusted based on the first member block, and wherein the second user is classified as a threat in response to the second member block.

19. The system of claim 15 , further comprising:

a member node associated with the first member of the communication network and comprising:

a member blockchain ledger; and

a member blockchain controller configured to insert a member block based on a first user of the first member into the member blockchain ledger, wherein the member block comprises an internet protocol (IP) address of the first user;

a member node associated with a second member of the communication network and configured to:

extract the IP address of the first user and an identity attribute of the first member from a network packet sent by the first user;

classify the first user as trusted in response to:

determining that the first member is validated based on a first validated MIHB in the master blockchain ledger comprising the identity attribute extracted from the network packet; and

determining that the member blockchain ledger comprises the IP address of the first user extracted from the network packet by traversing the member blockchain ledger,

wherein the second member is associated with a second user, and wherein the second user participates in a communication session with

the first user in response to the first user being classified as trusted.

20. The system of claim 19 , wherein the first user is a human.