Operation
Digitally Signing Information
The procedure for a signatory to digitally sign information is:
The signatory must own a hardware or software blockchain wallet which contains a private key, an associated public key and associated public key addresses
Generate the specific information to be signed
Send the information into the signatory’s wallet function that signs information – this will create a digital signature of the information from the signatory’s private key
Copy the output of the wallet (the digital signature of the supplied information)
Provide that signature as required
Bitcoind Wallet
If the bitcoind wallet is used, it can be used to sign the information with the public key address:
Producing a signature like:
164b0b3fe7d09ef0728dc3822115e38c4d6460bf890e7e9a347545d38f34
ElectrumSV Wallet
It is also possible to sign the information in the ElectrumSV wallet application, see the Tools/Sign/Verify message menu option. Provide the wallet address and the information, producing a signature similar to this:
Backup Procedures
The tools are distributed as docker images (see reference 6). Because docker images use local hard drives for persisting data, only the location where the volume is stored needs to be backed up.
This can be done manually by copying the volume data to separate storage, or by setting up automatic backup process of the docker volume location.
To stop the containers before backup, use this command for each tool (potentially across multiple machines):
Copy the data files for each machine according to your company backup procedure (potentially across multiple machines):
Restart the containers for each tool (potentially across multiple machines):
Note: A consistent data set for backup is across all machines that are providing the system. All data files in the set must be stored (and if necessary, restored) together.
Last updated