Feature Proposal: Post-Generation SiliconSignature Watermark — Hardware-Bound Image Provenance

[Agnuxo1]

Hi @invoke-ai,

InvokeAI is one of the most polished open-source image generation platforms. I have a project that could add hardware-bound provenance to every image generated.

SiliconSignature — ASIC-Based Image Authentication

We use ASIC miners (Antminer S9 BM1387) to generate proof-of-work nonces, then embed them via Reed-Solomon LSB watermarking.

Proposed Integration: Post-Generation Watermark

New node in InvokeAI pipeline:

[txt2img / img2img] → [VAE Decode] → [SiliconSignature Watermark] → [Gallery]
                                              │
                                              ├── ASIC nonce generation
                                              ├── Reed-Solomon encoding
                                              ├── LSB embedding
                                              └── Metadata JSON

New UI panel:

┌─ SiliconSignature ──────────────────┐
│ ☑️ Sign with ASIC                   │
│ Device: /dev/ttyUSB0               │
│ Redundancy: 5×                     │
│ ☑️ Include metadata (prompt, seed) │
└─────────────────────────────────────┘

Verification Flow

# Any user can verify offline
python -m siliconsignature verify output.png
# → ✅ Signed by InvokeAI-ASIC-0x7a3f...
# → 🎨 Metadata: prompt="cyberpunk city", seed=12345, model=SDXL
# → 🔒 Integrity: FULL

Why This Matters

Threat	Current	+ SiliconSignature
Fake provenance	Possible	ASIC physically required
Tampering	Undetected	Exact pixel detection
Server spoofing	Possible	$10,000+ forge cost
Offline verify	Needs API	Pure math, zero deps

Technical Details

• ASIC: SHA-256 on Antminer S9 BM1387
• Watermark: Reed-Solomon GF(2^8), configurable redundancy
• Embed: LSB in PNG (preserves InvokeAI's output format)
• Verify: Offline Python, MIT license
• Forge barrier: Physical ASIC required ($10,000+)
• Repo: https://github.com/Agnuxo1/Secure_image_generation_with_ASIC_signature

Author

Francisco Angulo de Lafuente (@Agnuxo1) — independent researcher, 35 years

Would you consider a post-generation watermarking node for hardware-bound image authentication?

— Francisco