Verae Timestamping for Windows

Artifacts

All three EXEs are frozen one-file binaries (GUI/CLI via PyInstaller; hasher is a small native Rust build). Place them in the same folder so the GUI can find verae-sha256.exe.

Install & first run

1. Download the three EXEs (or at least the GUI) into a folder such as %USERPROFILE%\Verae\.
2. Verify checksums, e.g. in PowerShell:

   Get-FileHash .\verae-timestamp-gui.exe -Algorithm SHA256
   Get-Content .\SHA256SUMS

3. If SmartScreen blocks: More info → Run anyway, or unblock via Properties.
4. Double-click verae-timestamp-gui.exe (first launch can be slow while the onefile bundle extracts to %TEMP%\_MEI…).
5. Confirm MCP URL is https://mcp.verae.ai/mcp, scope global, then Save defaults (writes %USERPROFILE%\.verae\client.json).
6. Optional auth for global stamps that need a VeraeTime account — use the CLI login / set-auth helpers; tokens live in %USERPROFILE%\.verae\auth.properties (mode 600 on Unix; ACL-protected on Windows where possible).

GUI: Register · Verify · Hash · Export

Status colors: green = PASS (registered / valid), red = FAIL, blue = hashed. Results table columns: Status, File, SHA-256, Timestamp, Receipt, Scope. Export JSON / CSV / Text, or Copy output.

Screenshots are the real PySide6 Qt GUI shipped inside verae-timestamp-gui.exe (same gui_qt.py), captured in a dry run against https://mcp.verae.ai/mcp on 2026-09-28. Window chrome may differ slightly on a native Windows desktop; layout and results are identical.

CLI usage

verae-timestamp.exe
verae-timestamp.exe set-defaults --url https://mcp.verae.ai/mcp --scope global --output text
verae-timestamp.exe hash .\sample-contract.txt
verae-timestamp.exe register .\sample-contract.txt
verae-timestamp.exe verify .\sample-contract.txt
verae-timestamp.exe verify --output json --output-dir .\out .\sample-contract.txt
verae-timestamp.exe verify --output csv --output-dir .\out .\sample-contract.txt

Receipts also land under %USERPROFILE%\.verae\receipts\<sha256>.json unless --no-persist is set.

Example outputs (real dry run)

Captured 2026-09-28 against the live MCP with a local sample file. Paths below reflect the capture host; on Windows you would see a C:\… path instead. Digests, receipt ids, and timestamps are authentic.

c4c2489ebe491a110c26fb66cdfb3545785d4746453a46d21cb6eb2f2972d60c  sample-contract.txt

File: sample-contract.txt
SHA-256: c4c2489ebe491a110c26fb66cdfb3545785d4746453a46d21cb6eb2f2972d60c
Scope: global
Receipt: QmTV7gB2vb3ALTCKe1DZ1qxBvawF6h6a4ajYax2chNp6Nc
Original timestamp: 2026-09-28T17:15:39.073480469Z
Merkle: (none)
Status: ok

File: sample-contract.txt
SHA-256: c4c2489ebe491a110c26fb66cdfb3545785d4746453a46d21cb6eb2f2972d60c
Scope: global
Receipt: QmTV7gB2vb3ALTCKe1DZ1qxBvawF6h6a4ajYax2chNp6Nc
Original timestamp: 2026-09-28T17:15:38.657720898Z
Merkle: 113072
Status: valid

[
  {
    "sha256": "c4c2489ebe491a110c26fb66cdfb3545785d4746453a46d21cb6eb2f2972d60c",
    "scope": "global",
    "path": "sample-contract.txt",
    "valid": true,
    "error": null,
    "receipt": {
      "receipt_id": "QmTV7gB2vb3ALTCKe1DZ1qxBvawF6h6a4ajYax2chNp6Nc",
      "scope": "global",
      "created_at": "2026-09-28T17:15:38.657720898Z",
      "merkle": "113072"
    },
    "receipt_id": "QmTV7gB2vb3ALTCKe1DZ1qxBvawF6h6a4ajYax2chNp6Nc",
    "status": "valid"
  }
]

path,sha256,scope,receipt_id,created_at,merkle,status
sample-contract.txt,c4c2489ebe491a110c26fb66cdfb3545785d4746453a46d21cb6eb2f2972d60c,global,QmTV7gB2vb3ALTCKe1DZ1qxBvawF6h6a4ajYax2chNp6Nc,2026-09-28T17:15:38.657720898Z,113072,valid

Raw capture files (full paths as written by the client): verae-verify.json · verae-verify.csv · verae-register.txt · hash-only.txt

Runtime notes

• Architecture: PE32+ x86-64 (amd64). GUI subsystem for the GUI EXE.
• PyInstaller embeds MSVC runtime DLLs; a separate VC++ Redistributable is usually not required.
• Config / auth / receipts: %USERPROFILE%\.verae\ (same layout as macOS ~/.verae).
• Also try the browser app if you prefer not to install binaries.