> Source: https://vitna.ai/docs/routing/verifying
> Raw Markdown: https://vitna.ai/docs/routing/verifying.md
> Corpus index: https://vitna.ai/llms.txt

# Verifying a routing config

Checking a file you were handed, without needing the database or the key that
made it.

```bash
npm run aperture:config -- --verify /etc/convexity/models.env
```

## What it checks without anything

The digest is recomputed from the file's own canonical body, and the signature
checked over the statement the file carries. Neither needs a database nor a
signing key, so a consumer can verify a config on a machine that has neither.

## The part a signature does not settle

A valid signature proves that whoever holds that key signed this file. It does
not prove the key is Vitna's.

So the command says so out loud. Without a database it reports the key as **not
checked**, and points at the key published on `/witness` and
`/api/v1/attestations` to compare against.

With `DATABASE_URL` set it compares the key against the one the record
publishes, and only then reports that this is Vitna's signature and not a
well-formed forgery.

If the record has signed nothing yet, it says that too, rather than reporting a
check it did not make.

## The same distinction the attestations make

This mirrors what [`attestation`](../concepts/attestation.md) says about the
daily roots. A signature is a statement about custody of a key, and the step
that ties a key to Vitna is published separately and has to be done.

The signing key here is the same one the daily attestation uses.
`npm run witness:attest -- --new-key` prints a pair.
