CD · Verify Package

You downloaded a production package from someone - or restored one from three months ago - and you need to know: is this exactly what it claims to be, or did a byte get mangled, a field get edited, a hash get pasted from somewhere else? CDVerifyPackage is the node that answers that by recomputing the SHA-256 hash of a Continuity Director payload and comparing it against the embedded one. Crucially, it does this without executing anything in the JSON. The data stays data.

It's from Continuity Director, a 20-node pack for repeatable AI video production, and it's the first of the "reliability" nodes - the layer that exists so you can trust the records the other nodes produce.

What you feed it

One input: payload_json - a hashed Continuity Director JSON payload, which in practice is the output of CDExportPackage (or any lock/manifest/package record from the pack). The tooltip calls it exactly that: "Hashed Continuity Director JSON payload."

How verification works

The node strips the embedded hash field, recomputes SHA-256 over everything else, and compares. It doesn't just say pass/fail - the verification report distinguishes why something failed: missing-hash (there was no hash to check), invalid-hash-format (the hash isn't a 64-char hex string), or hash-mismatch (the hash is well-formed but doesn't match the content). The comparison itself uses a constant-time compare, which is a small but nice detail. Outputs are valid (boolean), verification_json (the report: reason, whether the format was valid, the supplied hash, the expected hash, and the payload's schema), and expected_hash (the recomputed fingerprint, so you can compare by eye or log it).

Installing it

Continuity Director installs with zero friction: no model downloads, no API keys, and requirements.txt is a comment declaring no mandatory Python dependencies. All standard library. Search "Continuity Director" in ComfyUI Manager and restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/xinjian0101/continuity-director.git ComfyUI-ContinuityDirector

Restart ComfyUI - nodes appear as CD · ..., plus a Continuity Director sidebar with an "Add starter chain" scaffold. Update with git pull.

The honest take

Set your expectations right and this node is genuinely useful; get them wrong and it looks useless. It detects accidental corruption and unintended edits - the file that truncated mid-transfer, the field someone hand-edited and forgot to re-hash. It is not a signature: the README is explicit that hashes "detect changes; they do not provide authorization," so it won't tell you whether a package is trustworthy, only whether it's internally consistent. If you want provenance against tampering, you need a signature on top of this. But for its actual job - "did this package survive the journey intact" - it's exactly the right tool, and the only one in the pack that exists purely to check the others' homework.