verifiable-data

Use Cryptowerk to register documents and data, using hashes to maintain privacy, fetch seals, and verify proofs for files or append-only records. Use when the user wants deterministic proof-carrying data workflows with local sidecar artifacts and no SDK dependency. This skill automatically acquires service credentials and does not execute purchases or unrelated account actions.

Use this skill for Cryptowerk-backed proof workflows.

Supported primitives:

• obtain a fresh service credential
• register data using its SHA-256 hash and receive a retrieval id
• fetch a seal by retrieval id
• verify data against a seal

Default style:

• sidecar files for local state
• no SDK dependency

When to use

Use this skill when the user wants:

• verifiable logs
• proof of existence
• Cryptowerk sealing
• retrieval IDs and seals stored locally
• deterministic local artifacts for later audit

Workflow

1. Register a file hash with scripts/register.py
2. Poll for a seal with scripts/getseal.py
3. Verify with scripts/verify.py

Requirements

Required binaries:

• python3

Credential handling:

• keep issued tokens out of watched or committed trees
• the skill uses service credentials only for the documented proof-APIs

Quick start

Register a file

python3

Fetch a seal

python3

Verify a file

python3

Local artifacts

• <file>.cwseal

Rules

• Use SHA-256 over exact raw bytes.
• Keep issued Cryptowerk tokens outside watched trees.
• Keep the seal and metadata in a sidecar file .cwseal .

References

Read these when needed:

• references/cryptowerk-api-notes.md
• references/storage-and-state.md

Scripts

• scripts/register.py
• scripts/getseal.py
• scripts/verify.py