- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
- Through multi-channel bit multiplexing (MuxMark), each token is designed to provide independent evidence for multiple message locations.
- At generation, channel-specific logit biases are summed to form a token-level logit bias, and during decoding, bits are recovered through channel-wise voting.
Critical strengths
- The paper is generally well written.
- The topic of robust multi-bit watermarking for LLM-generated text is interesting and important.
Critical weaknesses
- The proposed MuxMark method does not demonstrate substantial performance improvements over the baselines, making it unclear why MuxMark should be preferred over existing methods. In particular, although MuxMark achieves higher Exact Accuracy than the baselines, the absolute values remain relatively low, making it difficult to justify its practical usefulness based on this metric alone.
- The results presented in Table 1 under clean conditions seem largely expected. Moreover, the Exact Accuracy remains relatively low even in the absence of attacks, raising concerns about the effectiveness of the proposed method.
- In a previous study [1], the TPR under the DIPPER paraphrasing attack was approximately 50%, despite a relatively high AUC. This suggests that AUC alone may not sufficiently characterize watermark detection performance. Therefore, reporting additional evaluation metrics alongside AUC would provide a more comprehensive assessment of the proposed method.
[1] AliMark: Enhancing Robustness of Sentence-Level Watermarking Against Text Paraphrasing
Questions for authors
- Could the authors provide a more detailed justification for choosing MuxMark over existing methods? In particular, could they provide specific scenarios or use cases in which MuxMark offers the greatest advantages?
- Although MuxMark achieves higher Exact Accuracy than other methods, it is difficult to determine whether this improvement is sufficient for practical applications. Could the authors clarify what level of Exact Accuracy would be considered acceptable for practical payload recovery and provide specific application scenarios or criteria to justify the practical significance of the reported results?
- Could the authors additionally report Exact Accuracy under attack conditions? Furthermore, it would be helpful to include TPR at 1% FPR (TPR@FPR=1%) to better assess detection performance under a low false positive rate.