System and method for utilizing connected devices to enable secure and anonymous electronic interaction in a decentralized manner
A system and method for utilizing connected devices to enable secure and anonymous electronic interaction in a decentralized manner without the need for usernames and passwords. The method comprises Blockchain, Merkle Trees and Public Key infrastructures and methods that utilize peer-to-peer network protocols. The methods include interactions of two self-sovereign identity groups; persons and devices, with each having their own authorization layer. The devices employ two domains of identity and authorization with each said device having its own self-assigned machine identity. There are three domains of Identity, Authentication and Authorization employed for persons. The final linking of the two groups requires access to be granted by the device in a distributed autonomous manner.
1. A method for managing access permissions for a connected device by a user device, the method comprising:
generating, by a connected device, a public key and a private key for the connected device, the connected device storing in its memory a genesis block for a private blockchain, the genesis block being addressable using a hash of a unique qualifier of the connected device;
hashing, by the connected device, the public key to provide a self-identity of the connected device;
adding, by the connected device, a life block to the private blockchain, the life block being added to the private blockchain as a block following the genesis block, the life block being addressable by the hash of the public key, the life block being stored in the memory;
designating a user device as an owner of the connected device, the user device controlling access permissions to the connected device, and adding a first permissions block to the private blockchain, the first permissions block storing a self-identity of the user device as the owner of the connected device;
adding a further permissions block to the private blockchain, the further permissions block storing access permissions for one or more users of the connected device;
initiating distribution of the private blockchain comprising the genesis block, the life block, and the permissions blocks, to a plurality of peers; and
controlling access to the connected device based on the access permissions stored in the private blockchain.
2. The method according to claim 1 , wherein an address to a public blockchain is included in the genesis block, the method further comprising the connected device adding to the public blockchain a new block comprising the self-identity of the connected device.
3. The method according to claim 1 , wherein the self-identity of the user device is a hash of a public key associated with the user device.
4. The method according to claim 1 , wherein the connected device generates the public key and private key and hashes the public key to provide the self-identity when the connected device is powered up for the first time after manufacture.
5. The method according to claim 1 , further comprising:
the connected device powering up for the first time after manufacture;
the connected device contacting a central server to obtain an authorization;
wherein the connected device generating the public key and private key and hashing the public key occurs after receiving the authorization.
6. The method according to claim 1 , wherein the access permissions to the connected device are controlled by the user device.
7. The method according to claim 1 , wherein designating the user device as the owner of the connected device comprises the user device connecting to the connected device.
8. A device, comprising:
at least one hardware processor;
a memory module; and
a wireless communication module,
the at least one hardware processor being configured to implement management of access permissions for the device by a user device, comprising:
generating a public key and a private key for the device;
storing, in the memory module, a genesis block for a private blockchain, the genesis block being addressable using a hash of a unique qualifier of the device;
hashing the public key to provide a self-identity of the device;
adding a life block to the private blockchain, the life block being added to the private blockchain as a block following the genesis block, the life block being addressable by the hash of the public key, the life block being stored in the memory module;
designating a user device as an owner of the device, the user device controlling access permissions to the device, and adding a first permissions block to the private blockchain, the first permissions block storing a self-identity of the user device as the owner of the device;
adding a further permissions block to the private blockchain, the further permissions block storing access permissions for one or more users of the device;
initiating distribution of the private blockchain comprising the genesis block, the life block, and the permissions blocks, to a plurality of peers; and
controlling access to the device based on the access permissions stored in the private blockchain.
9. The device according to claim 8 , wherein an address to a public blockchain is included in the genesis block, and the at least one processor is further configured to add to the public blockchain a new block comprising the self-identity of the device.
10. The device according to claim 8 , wherein the self-identity of the user device is a hash of a public key associated with the user device.
11. The device according to claim 8 , wherein the at least one processor is configured to generate the public key and private key and hash the public key to provide the self-identity when the device is powered up for the first time after manufacture.
12. The device according to claim 8 , wherein the at least one processor is configured to cause the device to contact a central server to obtain an authorization when the device is powered up for the first time after manufacture, and is further configured to generate the public key and private key and hash the public key after receiving the authorization.
13. The device according to claim 8 , wherein the at least one processor is configured to designate the user device as the owner of the device after the user device is connected to the device.
14. A non-transitory computer-readable medium storing code which, when executed by at least one hardware processor of a device, causes the device to implement:
generating a public key and a private key for the device;
storing, in memory of the device, a genesis block for a private blockchain, the genesis block being addressable using a hash of a unique qualifier of the device;
hashing the public key to provide a self-identity of the device;
adding a life block to the private blockchain, the life block being added to the private blockchain as a block following the genesis block, the life block being addressable by the hash of the public key, the life block being stored in the memory of the device;
designating a user device as an owner of the device, the user device controlling access permissions to the device, and adding a first permissions block to the private blockchain, the first permissions block storing a self-identity of the user device as the owner of the device;
adding a further permissions block to the private blockchain, the further permissions block storing access permissions for one or more users of the device;
initiating distribution of the private blockchain comprising the genesis block, the life block, and the permissions blocks, to a plurality of peers; and
controlling access to the device based on the access permissions stored in the private blockchain.
15. The non-transitory computer-readable medium according to claim 14 , wherein an address to a public blockchain is included in the genesis block, and the device is further caused to add to the public blockchain a new block comprising the self-identity of the device.
16. The non-transitory computer-readable medium according to claim 14 , wherein the self-identity of the user device is a hash of a public key associated with the user device.
17. The non-transitory computer-readable medium according to claim 14 , wherein the device is caused to generate the public key and private key and hash the public key to provide the self-identity when the device is powered up for the first time after manufacture.
18. The non-transitory computer-readable medium according to claim 14 , wherein the device is further caused to contact a central server to obtain an authorization when the device is powered up for the first time after manufacture, and is further configured to generate the public key and private key and hash the public key after receiving the authorization.
19. The non-transitory computer-readable medium according to claim 14 , wherein the device is caused to designate the user device as the owner of the device after the user device is connected to the device.