WITNESSCTL(1)

🎀 WITNESSCTL(1) 🎀

okay so. this is witnessctl, bestie — the command that operates on the litewitness(1) database. that's the whole vibe. it's a manual-page situation, it's giving "I have exactly one job and I do it flawlessly" energy 💅

---

🌸 NAME 🌸

witnessctl — operate on the litewitness(1) database 🦋

---

✨ SYNOPSIS ✨

witnessctl <command> [options]

like, you pick a command and then you hand it whatever options it wants. that's the shape of it, periodt.

---

💖 DESCRIPTION 💖

so this page is basically a menu, and the menu is the commands. no cap, that's the whole thing. each command wants a -db <path> because hello, it needs to know where the database is at, and the rest of the flags are per-command situations. pick your fighter:

🫶 Commands 🫶

• add-log — the one called add-log. flags it takes:
  • -db <path> — the database <path>, obviously, she needs directions 🗺️
  • -origin <origin> — the <origin> in question ✨
• add-key — the one called add-key. flags it takes:
  • -db <path> — database <path> 💾
  • -origin <origin> — the <origin> ✨
  • -key <verifier key> — a <verifier key>, exactly that kind 🔑
• del-key — the one called del-key. flags it takes:
  • -db <path> — database <path> 💾
  • -origin <origin> — the <origin> ✨
  • -key <verifier key> — a <verifier key> 🔑
• add-sigsum-log — the one called add-sigsum-log. flags it takes:
  • -db <path> — database <path> 💾
  • -key <hex-encoded key> — a <hex-encoded key> this time, not a verifier key, don't mix them up bestie 🚨
• list-logs — the one called list-logs. flags it takes:
  • -db <path> — database <path>, and that is literally the only one 💾

also note: add-sigsum-log is out here with -key <hex-encoded key> while add-key and del-key roll with -key <verifier key>. they are not the same flag, they do not do the same thing, do not YOLO them 🔥

---

and that's the page, babe 🎀 this is witnessctl version 0.4.3-3build1, dated February 2026, dropped as a User Command in the WITNESSCTL(1) section of the manual. go be iconic with it 💅✨🦋