# Offline verification

Open the transaction package or select the corresponding evidence and verification files.

## Open the prepared transaction package

From Offline verification or a saved comparison, use Install verifier and open this transaction. Run the downloaded installer according to the institution’s software policy. If the transaction is not preselected, open the .sigillum-check file obtained through Download this transaction’s offline package.

## Match files to verifier fields

| Download | Purpose in the verifier |
|---|---|
| Transaction evidence / evidence ZIP | Sealed transaction and related evidence input |
| Seal verification key | Verify the content seal signature |
| Witness verification key | Verify the witness signature |
| Report signature key | Verify the saved report signature |
| Private opening file | Original-content/opening material for the selected comparison |
| .sigillum-check package | Open the related files together |

Match the transaction and comparison run shown on screen with the downloaded files. An identical extension does not make another transaction’s key or opening file suitable.

## File naming conventions

The current product uses the following literal filenames; retain them when matching portal downloads to verifier inputs.

| File | Filename pattern |
|---|---|
| Transaction package | Sigillum-Islem-Paketi-*.sigillum-check |
| Evidence package | Sigillum-Kanit-Paketi-*.zip |
| Seal verification key | Sigillum-Muhur-Dogrulama-Anahtari-*.json |
| Witness verification key | Sigillum-Tanik-Dogrulama-Anahtari-*.json |
| Report verification key | Sigillum-Rapor-Imza-Dogrulama-Anahtari-*.json |
| Private opening file | Sigillum-Ozel-Acma-Dosyasi-*.json |
| Transaction evidence | Sigillum-Islem-Kaniti-*-Surum-*.json |

The comparison package identifies its run; transaction evidence identifies its transaction and sealed slice. Renaming a file does not change its signed identity.

## Protect private opening material

Public verification keys and files that open original content have different confidentiality requirements. Opening files and packages can contain institutional data. Share them only with authorised recipients through approved channels. Do not upload them to this public documentation website.

## Interpret the offline result

Select trusted keys and the corresponding evidence, then run verification. Read integrity and comparison results separately. Missing keys, wrong opening material, unsupported versions and signature mismatches are distinct failures. A successful result requires completion of all necessary checks.