{"slug": "why-we-need-to-schedule-post-quantum-cryptography-around-the-weather", "title": "Why We Need to Schedule Post-Quantum Cryptography Around the Weather", "summary": "An engineer has released Quant Harvest, an open-source Go control plane that schedules post-quantum cryptography workloads to run only when the electrical grid is cleanest. The tool buffers CPU-intensive PQC operations and defers them when carbon intensity is high, resuming when renewable energy is available, aiming to reduce the carbon footprint of the PQC migration.", "body_md": "The security industry is undergoing one of the largest migrations in history: moving from classical cryptography (RSA/ECC) to **Post-Quantum Cryptography (PQC)**.\n\nWhile algorithms like **ML-KEM** (FIPS 203) are quantum-resistant, they have a hidden cost: they are **CPU-intensive**. Compared to classical algorithms, key generation, signing, and verification consume significantly more compute.\n\nMore compute = more electricity. For bulk operations (signing millions of docs, encrypting petabytes of backups), this spikes carbon footprint — bad for net-zero goals.\n\nWhat if we schedule these workloads to run **only when the grid is cleanest**?\n\nEnter **Quant Harvest**.\n\n**Quant Harvest** is an open-source Go control plane — a carbon-aware deferred-execution queue for PQC workloads.\n\nInstead of executing heavy crypto immediately, it buffers workloads and monitors grid carbon intensity (gCO2e/kWh). Dirty grid (fossil) → pause queue. Clean grid (solar/wind) → resume and harvest.\n\n```\n                  ┌──────────────────────┐\n                  │   Workload Enqueued  │\n                  └──────────┬───────────┘\n                             ▼\n                  ┌──────────────────────┐\n                  │    Task Buffered     │\n                  └──────────┬───────────┘\n                             ▼\n               No  /───────────────────\\\n             ┌────/  Grid Clean enough? \\\n             │    \\   (Under threshold) /\n             │     \\───────────────────/\n             ▼               │ Yes\n     ┌──────────────┐        ▼\n     │ Queue Paused │ ┌──────────────┐\n     └──────────────┘ │ Execute Task │\n                      └──────────────┘\n```\n\n**Try it live:** [https://quant-harvest.onrender.com](https://quant-harvest.onrender.com)\n\n```\ncurl -X POST https://quant-harvest.onrender.com/api/tasks \\\n  -H \"Content-Type: application/json\" \\\n  -H \"Idempotency-Key: demo-123\" \\\n  -d '{\"name\":\"pqc-batch-signing\",\"payload\":\"ml-kem-768\"}'\n\n# Watch /api/status — when carbon >200 it defers, when <200 it runs\ncurl https://quant-harvest.onrender.com/api/status | jq\n```\n\n`modernc.org/sqlite`\n\npure-Go driver) — busy timeouts, atomic claims, idempotency via `Idempotency-Key`\n\n`/metrics`\n\n(`qharvest_task_queue_size`\n\n, `qharvest_carbon_intensity`\n\n) + `/healthz`\n\n`/readyz`\n\n`/`\n\n— real-time grid chart + queue + WAL logs (see live demo)`deploy/`\n\n```\n// pqc.go — integration boundary ready for ML-KEM\nfunc EnvelopeIdentifier(data []byte) [32]byte {\n    return sha256.Sum256(data) // placeholder for vetted ML-KEM/FIPS203\n}\n2026/08/15 12:01:45 Q-HARVEST listening on :8080\n2026/08/15 12:02:00 scheduler: deferring queue at 270gCO2e/kWh\n2026/08/15 12:02:15 scheduler: carbon intensity dropped to 145gCO2e/kWh\n2026/08/15 12:02:15 scheduler: executing pqc-bulk-signing\n```\n\nGreen computing is usually \"use less.\" Quant Harvest is \"use **when** clean.\" Same jobs, shifted to renewable windows — simplest decarbonization win for PQC migration.\n\nApache-2.0. If you're Go/DevOps/crypto, try the live demo and roast the scheduler logic!", "url": "https://wpnews.pro/news/why-we-need-to-schedule-post-quantum-cryptography-around-the-weather", "canonical_source": "https://dev.to/skeletorpirate/why-we-need-to-schedule-post-quantum-cryptography-around-the-weather-2lhk", "published_at": "2026-08-27 11:21:01+00:00", "updated_at": "2026-08-27 11:48:25.853098+00:00", "lang": "en", "topics": ["developer-tools", "ai-infrastructure"], "entities": ["Quant Harvest", "ML-KEM", "FIPS 203"], "alternates": {"html": "https://wpnews.pro/news/why-we-need-to-schedule-post-quantum-cryptography-around-the-weather", "markdown": "https://wpnews.pro/news/why-we-need-to-schedule-post-quantum-cryptography-around-the-weather.md", "text": "https://wpnews.pro/news/why-we-need-to-schedule-post-quantum-cryptography-around-the-weather.txt", "jsonld": "https://wpnews.pro/news/why-we-need-to-schedule-post-quantum-cryptography-around-the-weather.jsonld"}}