Imprint - Verify Transaction

Every blockchain provenance scheme has the same moment of truth: the image was anchored months ago, and now someone wants to check it. Imprint - Verify Transaction is that check. Give it a 64-hex transaction id and it queries ImprintAI's public verification endpoint and tells you whether the chain record is valid, plus what metadata it carries. No API key, no account - the endpoint is public, which is the entire point. A third party with your txid can verify your image's record without asking you for anything or trusting you.

In a full Imprint workflow this is the quiet closer: you anchor with ImprintLog, export the labelled file, and later - possibly on someone else's machine - paste the txid in here and get the assertion back.

How it works

The node takes one required input, txid (plus an api_url that defaults to https://imprintai.link for self-hosted or dev setups), and GETs {api_url}/api/verify/{txid}. The service looks up the transaction and returns the stored assertion - the model, the hashes, the generation metadata that ImprintLog sent when it anchored. Two outputs come back:

• valid - a boolean. False if the txid is malformed, unknown, or the request fails; the console prints the reason.
• metadata_json - the assertion as pretty-printed JSON, or {} when verification fails. You can wire this into any text display node to eyeball it.

If you're checking the record of a file in front of you, this is where the difference between ImprintLabel's two stego methods shows up. An exact-file v1 label claims those exact pixels were anchored; a v3 label survives recompression but makes a "transformed copy" claim instead - the source is explicit that v3 doesn't prove transformed pixel equality. So a txid verified as valid doesn't automatically mean this particular download is the original bytes. Match the claim to the file you're checking.

When you'd reach for it

Honestly, this node is most useful as a sanity check while you're setting the pack up: anchor an image, run the verify node on the returned txid, and confirm the round trip works before you start mass-producing labelled exports. Beyond that it's a nicety - the same verification is a plain curl away, which is exactly why the endpoint is public. The one real gotcha is the format: the txid must be a full 64-character hex string (the Log node hands you exactly that, so wire it directly rather than typing).

Installing

This pack isn't on the ComfyUI Registry yet, so manual install is the reliable route:

cd ComfyUI/custom_nodes
git clone https://github.com/svcBSV/imprintai-comfyui.git
cd imprintai-comfyui
python -m pip install -r requirements.txt

Restart ComfyUI completely. Only requests and Pillow as dependencies, both already bundled with ComfyUI, and no API key needed for this node itself - the verification endpoint is open by design.