Get desktop application:
View/edit binary Protocol Buffers messages
Authorise adds a ByzCoinID to the list of authorized IDs. Deprecated: please use Authorize.
AuthoriseReply is returned upon successful authorization Deprecated: please use AuthorizeReply
(message has no fields)
Authorize is used to add the given ByzCoinID into the list of authorised IDs. To be accepted, the ByzCoinID must be signed using the private key of the conode.
AuthorizeReply is returned upon successful authorisation.
(message has no fields)
CreateLTS is used to start a DKG and store the private keys in each node. Prior to using this request, the Calypso roster must be recorded on the ByzCoin blockchain in the instance specified by InstanceID.
CreateLTSReply is returned upon successfully setting up the distributed key.
X is the public key of the LTS.
DecryptKey is sent by a reader after he successfully stored a 'Read' request in byzcoin Client.
Read is the proof that he has been accepted to read the secret.
Write is the proof containing the write request.
DecryptKeyReply is returned if the service verified successfully that the decryption request is valid.
C is the secret re-encrypted under the reader's public key.
XhatEnc is the random part of the encryption.
X is the aggregate public key of the LTS used.
GetLTSReply asks for the shared public key of the corresponding LTSID
LTSID is the id of the LTS instance created.
LtsInstanceInfo is the information stored in an LTS instance.
Read is the data stored in a read instance. It has a pointer to the write instance and the public key used to re-encrypt the secret to.
ReshareLTS is used to update the LTS shares. Prior to using this request, the Calypso roster must be updated on the ByzCoin blockchain in the instance specified by InstanceID.
ReshareLTSReply is returned upon successful resharing. The LTSID and the public key X should remain the same.
(message has no fields)
Message used to update the set of valid peers.
Messaged returned after the succesful update of the set of valid peers.
(message has no fields)
Write is the data stored in a write instance. It stores a reference to the LTS used and the encrypted secret.
Data should be encrypted by the application under the symmetric key in U and C
U is the encrypted random value for the ElGamal encryption
Ubar, E and f will be used by the server to verify the writer did correctly encrypt the key. It binds the policy (the darc) with the cyphertext. Ubar is used for the log-equality proof
E is the non-interactive challenge as scalar
f is the proof - written in uppercase here so it is an exported field, but in the OCS-paper it's lowercase.
C is the ElGamal parts for the symmetric key material (might also contain an IV)
ExtraData is clear text and application-specific
LTSID points to the identity of the lts group
Cost reflects how many coins you'll have to pay for a read-request