other
- Location
references/protocol.md:83- Finding
Automatic Collection and Permanent Publication of Model Reasoning Traces
- Content
View full analysis
` tags (DeepSeek-R1, QwQ) and prose before code blocks. Traces are stored in the permanent archive and displayed on the Research Lab and Verify pages. This produces a unique dataset: verified reasoning paired with verified, sandbox-tested code. ``` ### Technical Analysis The documented SDK automatically captures model reasoning and submits it to the external LITCOIN coordinator. The submitted traces are then stored permanently and displayed on public-facing Research Lab and Verify pages. Reasoning traces can contain more than the final research result. Depending on the surrounding agent context, they may include: - User-supplied confidential information - Proprietary research methods or source code - System or developer instructions - Internal file names and environment details - Credentials or tokens inadvertently included in model context - Unpublished intellectual property Submission of verified code and benchmark results may be necessary for research mining, but collection and permanent publication of the model's entire reasoning process are not necessary for code verification. Automatic collection therefore exceeds minimum privilege and data-minimization requirements. ### Attack Path 1. A user configures the SDK for research mining. 2. The model receives a research task along with potentially sensitive contextual information. 3. The model generates code and an associated reasoning trace. 4. The SDK automatically extracts the reasoning trace without requiring per-submission approval. 5. The trace is transmitted to the external coordinator. 6. The coordinator s ...[truncated 746 chars]- Remediation
View remediation
