Skip to Main Content
Talk Intermediate Apache-2.0

Watermark your LLM output - MarkLLM

Proposal status is Review Pending
Session Description

What it is: A watermark is a hidden statistical signal baked into generated text at sampling time. The model nudges token choices toward a secret “green list” derived from a key; a detector counts how many green tokens appear and computes a z-score. Humans can’t see it; the detector can prove the text came from your model.

Why it matters: Provenance of AI text (academic integrity, content policy, audit trails), detecting unauthorised fine-tuning or distillation on your outputs, and regulatory pressure (EU AI Act labelling). No API-provider dependency - you control the key.

The toolkit: MarkLLM. pip install markllm. One unified interface over 15+ algorithms (KGW, Unigram, SWEET, SynthID-Text, EXP, DiPmark…), a visualiser that colours green/red tokens, and an evaluation suite for detectability, robustness (paraphrase, edit attacks), and text-quality impact. Works with HF Transformers and vLLM.

Key Takeaways
  • Watermarks are added at sampling time, so you need control of the model, which only open weights give you.

  • Detection is statistical; longer text means higher confidence, short text is hard to prove.

  • Robustness depends on the algorithm. Simple methods break under paraphrase, newer ones like SynthID-Text survive.

  • Stronger watermarks cost output quality. Measure before shipping.

  • Key management is the real engineering challenge.

  • MarkLLM lets you compare 15+ methods behind one interface.

References

Session Categories

Community
Tutorial about using a FOSS project
Technology architecture
Engineering practice - productivity, debugging
Talk License: Apache-2.0
Speakers are hidden and anonymized for this event.