Message encryption using public keychains
AssigneeCapital One Services, LLC
InventorAustin Walters
Life of this patent
Estimating the term…
Abstract
To encrypt and distribute a message, a processor of a sender device may determine a public key associated with a recipient identifier. The processor may request confirmation of a the recipient identifier from a central authority server. The processor may receive the confirmation of the recipient identifier from the central authority server. The processor may encrypt the message using the public key to form an encrypted message. The processor may distribute the encrypted message. The encrypted message may be decipherable using a private key associated with the recipient identifier and used by a recipient device to securely interact with the distributed blockchain.
Claims14
A method of encrypting and delivering a message, the method comprising:
- requesting, by a processor of a sender device, a recipient identifier from a central authority server;
- receiving, at the processor, a confirmation of the recipient identifier from the central authority server, the confirmation including a signed recipient identifier determined by the central authority server in response to the requesting;
- identifying, by the processor, a public key associated with the signed recipient identifier within a distributed blockchain;
- encrypting, by the processor, the message using a public key associated with the recipient identifier to form an encrypted message, wherein the encrypted message is decipherable using a private key associated with the recipient identifier and used by a recipient device to securely interact with the distributed blockchain;
- sending, by the processor, the encrypted message as an email or text message sent to an address of an account accessible by a user associated with an external device by at least one network;
- receiving, at the processor, an encrypted inbound message from the external device, the encrypted inbound message being encrypted using a second public key associated with a user of the sender device;
- decrypting, by the processor, the encrypted inbound message using a second private key associated with the user of the sender device;
- and
- decrypting, by the processor, at least one block of the distributed blockchain using the second private key.
A device configured to securely communicate with other devices, the device comprising:
- a processor;
- a transceiver in communication with the processor;
- and
- a non-transitory memory in communication with the processor and configured to store a private key for securely interacting with the distributed blockchain and instructions that, when executed by the processor, cause the processor to perform processing comprising:
- requesting, by the transceiver, a recipient identifier from a central authority server;
- receiving, by the transceiver, a confirmation of the recipient identifier from the central authority server, the confirmation including a signed recipient identifier determined by the central authority server in response to the requesting;
- identifying a public key associated with the signed recipient identifier within a distributed blockchain;
- encrypting the message using a public key associated with the recipient identifier to form an encrypted message, wherein the encrypted message is decipherable using a recipient private key associated with the recipient identifier and used by a recipient device to securely interact with the distributed blockchain;
- sending, by the transceiver, the encrypted message as an email or text message sent to an address of an account accessible by a user associated with an external device by at least one network;
- receiving, by the transceiver, an encrypted inbound message from a user of the external device, the encrypted inbound message being encrypted using a second public key associated with the user of the sender device;
- decrypting the encrypted inbound message using the private key in the memory;
- and
- decrypting at least one block of the distributed blockchain using the second private key.
Dependencies are inferred from the claim text.