# Welcome to 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.

3vidence is 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.

{% hint style="info" %}
You can connect any application (written in any language or on any stack) to 3vidence (API REST).
{% endhint %}

### Getting started

**Prerequisites**\
pyhton3

```bash
pip-3 install click requests 
```

#### Install 3vidence CLI

```bash
mkdir -p .local/bin
cd .local
git clone https://github.com/liesware/3vidence_cli
ln -s ~/.local/3vidence_cli/0545.py ~/.local/bin/0545
export PATH=$PATH:~/.local/bin/
```

On file \~/.local/3vidence\_cli/vars.py modify the variable fileConf (absolute path), for example:\
\&#xNAN;*fileConf = '/home/$USER/.local/3vidence\_cli/.3vidence.json'* 

{% hint style="info" %}
 3vidence CLI connects to 3vidence cloud systems and it helps you administrate your account.
{% endhint %}

#### Creating your account

Go to [api.3vidence.com/signup](https://api.3vidence.com/signup)

![Sign up for 3vidence](https://3111983141-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MIR-gTe6S2iB3L_wcxQ%2F-MUELKuOtVgOCghtO9Zx%2F-MUEPBtJzB2D2l8bSb_y%2FCaptura%20de%20pantalla%20de%202021-02-23%2009-00-13.png?alt=media\&token=e66478aa-c388-44a4-884f-d612ae6fb2e7)

\
Save the json at $YOUR\_DIR/3vidence\_cli/.3vidence.json

```bash
echo '{ "email": "ok@ok.com", "password": "BECD2D13E7815A915CC3ED9ED364E8285FA1853E3AE5B777A624D779C426784F" }' > ~/.local/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](https://3111983141-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MIR-gTe6S2iB3L_wcxQ%2F-MUEQ9tNZzJJaSUBRt2-%2F-MUEQyoXngdmUKBZArSE%2FCaptura%20de%20pantalla%20de%202021-02-23%2009-07-50.png?alt=media\&token=77263eae-40bc-4a36-8395-33b1a28bd786)

```bash
$ ./0545.py auth signup
```

#### Login

Let's login on your account

```bash
./0545.py auth login
```

#### Init

![You need this code to verify your subject](https://3111983141-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MIR-gTe6S2iB3L_wcxQ%2F-MUER2fLSXZn3nRFMUvZ%2F-MUEReIFTBoQ_QxzpjdO%2FCaptura%20de%20pantalla%20de%202021-02-23%2009-10-08.png?alt=media\&token=a406be4f-69d6-4259-b9b1-6ae225c72079)

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.

```bash
$ ./0545.py htsp init
```

#### Sign a file

Now you have your account, let's sign some files.

```bash
$ ./0545.py htsp sign YOUR_BRANCH_NAME YOUR_FILE
```

{% hint style="info" %}
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.
{% endhint %}

#### Verify a file

Let's verify your file

```bash
$ ./0545.py htsp verify YOUR_FILE
```

{% hint style="info" %}
Be careful, when you verify a file (YOUR\_FILE), the cli read the signature file (YOUR\_FILE.hjws).
{% endhint %}

#### Account info

In this option de cli displays your account info.

```bash
$ ./0545.py htsp info
```

#### Api key info

in this option de cli displays your api key info.

```bash
$ ./0545.py htsp info-key YOUR_BRANCH_NAME
```