加密结束桥接

SaveCryptoBridgeNode does nothing at execution time. It takes whatever you feed its value input, returns it unchanged on its * output, and that's the entire runtime story. The node's real job is structural: it's the tail marker that tells CryptoCat where the encrypted part of your workflow ends. In the pack's Chinese UI it's literally named "加密结束桥接" - the encryption-end bridge - and that name is more honest than the English one.

How the encryption scheme uses it

This is the current generation of CryptoCat (RiceRound/ComfyUI_CryptoCat), a workflow-encryption scheme built around three roles:

• SaveCryptoNode at the head - you wire the inputs the hidden section needs into its input_anything slots.
• SaveCryptoBridgeNode at the tail - you feed it the output of the hidden section, and its output connects onward to your visible output.
• Everything between the two is "the secret" - stripped out, uploaded to the author's server, and re-served only to people with a valid serial number.

When you queue the workflow, SaveCryptoNode's analysis walks the graph: everything upstream of its inputs is public, everything downstream of the bridge is public, and everything in between is what gets replaced by a license-gated DecodeCryptoNode. The bridge's output is the seam - that's the value the decode node re-attaches to the visible output side when a licensed user runs the packaged workflow. Get the seam wrong and the whole scheme falls apart, which is why the README hammers two rules: start node and bridge at opposite ends ("一头一尾"), and never leave the output connection dangling.

The inputs and output

It's about as minimal as a node gets:

• value (*) - any single value from the hidden section, commonly the final image (IMAGE) but literally anything.
• * output - the same value, passed through untouched to your visible output node (PreviewImage, SaveImage, whatever the recipient will see).

No widgets, no knobs. Wire it, forget it.

Installing it

It ships with the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/RiceRound/ComfyUI_CryptoCat

then restart ComfyUI. Or search "CryptoCat" in ComfyUI Manager (pack title ComfyUI Compression and Encryption Node). Dependencies are modest - aiohttp, pyzipper, websockets - no models to download. You'll find it under Advanced → CryptoCat.

Common issues

The two errors you'll actually hit come from the validation in trim_workflow.py: "No 'SaveCryptoBridgeNode' instances found" when you forget it, and "Multiple 'SaveCryptoBridgeNode' instances found" when you drop in two. It's exactly one bridge per encrypted workflow, no more, no less. The other classic mistake is leaving the bridge's output unwired - the README's warning about missing output connections is aimed squarely at this. If the bridge output doesn't reach a visible output node, the packaged workflow has no way to deliver results to whoever runs it.

Also set expectations before you invest an afternoon: this pack is a tiny niche. It launched in late 2024 as "the world's first commercial-grade workflow encryption" and the community's reaction was essentially one lukewarm thread - the tool is aimed at people selling or renting workflows, not at the average tinkerer. And remember the current-gen encryption path requires logging into the author's server and deals in hardware-bound serial numbers, so the bridge is a small piece of a bigger, very specific machine. If you're not selling workflows, you're unlikely to ever place one of these.