Paper: Block-wise Codeword Embedding for Reliable Multi-bit Text Watermarking Authors: Joeun Kim, HoEun Kim, Dongsup Jin, Young-Sik Kim arXiv: 2605.00348 (2026-04-29)
The Problem: Watermarks That Embed But Aren't Reliable
Watermarking AI-generated text matters for identifying AI content, preventing abuse, copyright protection, and content provenance. But existing approaches face a dilemma:
- Capacity-focused methods embed many bits but are unreliable, and they conflate decoding with detection.
- ECC-based extractors suffer catastrophic false-positive rates. Threshold tuning is a losing game: raising the threshold cuts false positives but drops detection rates to random-guess levels.
- Blind decoding tries to extract a watermark from everything, "decoding" information that doesn't exist. Threshold tuning hurts both false positives and detection.
- Specified verification separates the two questions: detect with high reliability, then decode only what's confirmed. The result: very low false positives, high detection sensitivity, and reliable multi-bit capacity — suitable for real deployment.
The core issue: multi-bit watermarks store more information but lose reliability — and at detection time, you can't tell whether a text is "watermarked but decoded wrong" or "not watermarked at all."
BREW: Block-wise Reliable Embedding
BREW shifts the paradigm from "detect first, then decode" to specified verification via a two-stage mechanism:
1. Block-level embedding — the text is split into blocks; each block independently carries watermark bits, enabling local verification and global aggregation. 2. Stage 1: Block-level detection — reliably confirm whether the text is watermarked. 3. Stage 2: Specified verification — decode payload bits only from confirmed blocks, avoiding false positives.
An analogy: traditional methods receive a letter and immediately try to read hidden content — even if no hidden message exists, you "read out" something that isn't there (false positives). BREW first checks "is there invisible ink?" Only if yes does it read the message.
Why Specified Verification Beats Blind Decoding
Takeaways for Practitioners
If you're building watermarking or provenance systems, ask:
1. Does my system conflate detection with decoding? 2. Is the false-positive rate acceptable? 3. Does multi-bit capacity sacrifice reliability? 4. Would a two-stage design improve reliability?
BREW reminds us: a reliable watermark isn't about how much information you can embed, but how certain you are at detection time. When a watermark system learns to "confirm first, decode second," it evolves from an information hider into a trustworthy content passport — in AI content governance, the best watermark isn't the most invisible one, but the most reliable one.