Timestamp

Create cryptographic proofs anchoring your files' exact content and timestamp to the Bitcoin blockchain for immutable, verifiable history.

This skill appears to do what it says: it creates and verifies OpenTimestamps proofs for files. Before installing/using it, consider: (1) install the official opentimestamps-client (pip3 install opentimestamps-client) from a trusted environment (verify PyPI/package integrity), because the scripts call the 'ots' CLI; (2) the scripts operate on your local workspace and will create .ots proof files and an .ots-archive directory — add .ots-archive/ to .gitignore if you don't want archives committed; (3) stamping only sends hashes (not file contents) to calendar servers, but those commitments are visible on-chain and multiple files stamped together are linkable as noted in the SKILL.md; (4) network access is required for stamping and verification (calendar servers/Bitcoin), so run these tools where network usage is acceptable. Overall, the package is coherent and proportionate to its purpose.

Type: OpenClaw Skill Name: timestamp Version: 1.0.0 The OpenClaw Timestamp skill is designed to create and verify cryptographic proofs of file existence using OpenTimestamps and the Bitcoin blockchain. The `SKILL.md` documentation clearly outlines its purpose, emphasizing privacy by stating 'No secrets uploaded. Only hashes leave your machine.' The accompanying shell scripts (`ots-auto-memory.sh`, `ots-stamp.sh`, `ots-verify.sh`) orchestrate the use of the `opentimestamps-client` (installed via `pip3`). These scripts perform file system operations (creating `.ots` proof files, archiving old proofs in `.ots-archive/` directories) and execute external commands (`ots`, `git`, `date`, `find`) strictly within the scope of timestamping and verification. There is no evidence of malicious intent, data exfiltration, persistence mechanisms, or prompt injection attempts against the agent. All actions are transparently aligned with the stated goal of building a verifiable history of files.