Lmcq Get Machine Code

This node doesn't do anything on its own - it exists to feed every other encryption node in this pack. Drop it in, run it, and it outputs one string: a unique code identifying the machine it ran on. That code is the key ComfyUI-LMCQ uses to lock encrypted models, LoRAs, and workflows to specific hardware, so only the machines you've authorized can ever decrypt them.

The mechanism. ComfyUI-LMCQ's "runtime protection" system (the LmcqRuntime*Encryption/Decryption node families, plus the older LmcqAuth* variants) lets a creator encrypt a model or LoRA with a password and restrict which physical machines can ever open it. The machine identifier that restriction is built on is exactly what this node reports - derived from local hardware and system information, per the README. No network call, no account, nothing to configure: run the node once, copy the string it outputs.

How you'd actually use it - the real workflow. Say you're selling access to a fine-tuned LoRA and want to lock it to a specific buyer's machine rather than just password-protecting it (a password can be shared; a machine lock can't, at least not without also sharing the physical box). The buyer runs LmcqGetMachineCode on their own ComfyUI install, sends you the resulting string, and you paste it into the machine_codes field of LmcqRuntimeLoraEncryption (or the model/workflow equivalents) before encrypting. Only that machine - or any other whose code you've also added - will be able to decrypt what you produce. Miss a step, encrypt without the buyer's code, and they'll have the right password but still can't open the file; that mismatch is the single most common support question this feature generates.

Inputs and outputs. There are no inputs at all - nothing to configure, nothing to wire in. The single output is machine_code, a plain STRING. Connect it to a text display node to read it, or just check the node's output in the UI after running once.

Installing it. Same as the rest of the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/sebord/ComfyUI-LMCQ

or install "ComfyUI-LMCQ" through ComfyUI Manager. Restart ComfyUI afterward. This particular node needs nothing else - no models, no config files, no network access.

Worth knowing before you build around this. ComfyUI has no sandboxing for custom nodes - every node in every pack runs with full access to your system, and that's exactly the mechanism this pack's whole encryption system depends on to fingerprint your hardware. That's not unique to LMCQ (it's how the ecosystem works, and it's also how a malicious node called ComfyUI_LLMVISION harvested credentials off a Disney employee's machine in 2024, ending in a federal conviction), but it's worth knowing that a "machine code" reader is, by definition, a node reaching into system-level details about the box it runs on. Nothing in the reported history of this pack suggests abuse of that access - this is a standard licensing-lock pattern, the same idea behind hardware-locked software keys generally - but it's the kind of node where you'd want to trust the source before running it on a machine you care about.

The pack-wide gotcha applies here too, even though this node has nothing to do with it directly: ComfyUI-LMCQ's encryption code depends on a compiled runtime module that's occasionally missing after install, and when that import fails at startup it takes the entire pack down, this node included. If none of the Lmcq nodes appear in your list, check your console for a ModuleNotFoundError mentioning runtime.model_protection - it's a known, reported issue, and the README's January 2026 changelog has the fix.