What's New in Digital Evidence Big update to Digital Evidence today. We shipped file uploads, a TypeScript SDK, and an MCP server that puts the full API in the hands of coding agents. Here's what's new and where it's all heading. File Uploads You can now upload files alongside fingerprints: images, screenshots, audio, documents. These get displayed publicly alongside their cryptographic proof on the Digital Evidence explorer. Anyone verifying a record sees the evidence and its provenance in one place. Screenshots of system events, timestamped images, audio logs. Anything that needs verifiable context around the proof itself. TypeScript SDK Integrating with Digital Evidence previously meant working directly with the API and pulling in third-party libraries to handle cryptographic signing. The new SDK handles all of that. Signing fingerprints, submitting them, uploading files, verifying public proofs. Getting started is now a few lines of code. MCP Server Coding agents like Claude Code, Cursor, and Codex can now discover and interact with the full Digital Evidence API directly. An agent can sign and submit fingerprints, upload files, and verify proofs without leaving its own workflow. Where this is heading These three features point in the same direction. As AI agents take on more autonomous work, there's a growing need for cryptographic accountability. When an agent acts, produces output, or makes a decision, a verifiable record of that action becomes essential. File uploads give that proof visual context. The SDK lowers the barrier to integration for both human developers and automated pipelines. The MCP server puts Digital Evidence directly in the hands of coding agents. Together, they shape Digital Evidence into an accountability layer for autonomous systems. We're early, and there's a lot more coming. @Conste11ation $DAG