Channel, you must upload an
Encryptionobject to the server. At any time, the decryptor can retrieve the
Encryptionobject using the hash of the token value, which acts as an identifier of the channel. The decryptor may choose to retrieve the
Encryptionobject immediately in order to independently store the encrypted values, or may only do so when a decryption is requested. In any case, no decryption can occur unless the decryptor has posted a data request and sufficient trustees and validators have responded. Read the code samples section for details and information about how to construct
Encryptionobject securely in some use cases (Find-me, for example), you can send a channel key along with this request. This ensures only you who has the private key counterpart of the channel key can change the
Encryptionobject in this channel.
encryption, namely whether or not the data has been requested by the decryptor. If a request has been made, then this status also gives which trustees and validators have responded to the data request. This information is retrieved and provided by the PAD server. To eliminate the need to trust the PAD service, this data should be checked for consistency with trustee attestations of the ledger state.
Encryptionafter establishing an encryption channel.
Encryptionobject with the channel private key.
Encryptionis successfully updated.
Encryptionis identified by
tokenHashand the instance in which it lives. It contains the ciphertext encrypted by both the decryptor's key and a fresh symmetric key
k. It also contains the encrypted shares of
kfor the trustees and validators. For more details, read the code samples page.
Trustee) and its public keys.
Validator) and its public keys.
encryption. The decryptor posts it on the ledger at data request stage.
.) or dashes (
-). It must start with a lowercase letter.