Here we will cover how to get started using 3vidence.
Overview
Creating anti-tampering evidence, improving integrity. Using 3vidence, developers are able to proof their users that time sensitive static data has not been modified by anyone, not even by their self.
3videnceis a solution that closes the gap (integrity and existence) between data at rest and data in use by developing a hybrid digital signature from lessons learned (as well as inspiration) of JWS, Wireguard, PGP, TOR, safecurves, Telegram, Signal, RFC 3161 and Blockchain timestamping. 3vidence uses hybrid-mode with pre-quantum and post-quantum signature schemes (ed25519 and dilithium) to create the next generation trusted timestamps with long term support and privacy. We empower apps with hybrid trusted timestamping protocol technology on application layer.
You can connect any application (written in any language or on any stack) to 3vidence (API REST).
On file ~/.local/3vidence_cli/vars.py modify the variable fileConf (absolute path), for example:fileConf = '/home/$USER/.local/3vidence_cli/.3vidence.json'
3vidence CLI connects to 3vidence cloud systems and it helps you administrate your account.
Save the json at $YOUR_DIR/3vidence_cli/.3vidence.json
When you create your account, check your mail to verify your account (please check on spam). You will be asked for the verification code on cli.
You need this code to complete your sign up
Login
Let's login on your account
Init
You need this code to verify your subject
To init your account, check your email to verify your subject. You will be asked for the verification code and your branch (YOUR_BRANCH_NAME) name on cli.
Sign a file
Now you have your account, let's sign some files.
Be careful , when you sign a file (YOUR_FILE), the cli creates a file with the same name and extension .hjws (YOUR_FILE.hjws), this file is needed to verify the signature.
Verify a file
Let's verify your file
Be careful, when you verify a file (YOUR_FILE), the cli read the signature file (YOUR_FILE.hjws).