Private Requests using Encryption
Last updated
Last updated
The Request Network protocol persists request contents on IPFS. When privacy is required, the SDK supports the creation and subsequent reading of encrypted requests.
This is achieved by combining public key (asymmetric) & AES (symmetric) encryption.
The "request contents" are encrypted with a random AES key. This key is then encrypted with the public key of each stakeholder of the request. The stakeholders are the users and platforms who require access to the request contents. The encrypted request contents and the encrypted AES keys are then persisted to IPFS.
The user retrieves the encrypted request content and the encrypted AES keys. They decrypt the AES key using their private key. Then they decrypt the request content using the AES key.
The privacy and encryption mechanism used by Request Network has many similarities to HTTPS. If you're not familiar with HTTPS, we recommend reading HTTPS explained with carrier pigeons
.svg?alt=media&token=27ae4ef1-67ce-40f9-9173-c1ca1be7b69c)
.svg?alt=media&token=bb496c7f-3f0e-4ab4-9198-d211bfb370c5)