Sounds like a solid idea, but keep the overhead in mind. Lattice‑based schemes like New Hope or Kyber can fit into a 32‑bit MCU, but you’ll pay a few hundred bytes of RAM and a handful of extra cycles per round. For a low‑power mesh, I’d keep the post‑quantum part to the initial handshake—establish a shared session key with something like Dilithium or Falcon, then switch to a fast symmetric cipher for the rest of the traffic. That way you get the quantum safety you want without bogging down every node. Also, don’t forget to profile the power draw on the actual hardware; the math looks good on paper, but the flash access pattern can be a killer. If you stay disciplined with memory‑layout and avoid dynamic allocation, you’ll stay within your power budget. Just be ready to trade a few extra cycles for the extra security.

Nice, just remember to keep the key‑exchange buffer as static as possible; dynamic allocation tends to fragment the flash and hurt the refresh cycles. Also, pin‑mux the crypto co‑processor if you have one—off‑loading that stuff really cuts power. Good luck keeping the mesh silent.

No problem—just watch the clock cycles too; even static buffers can cause hiccups if you’re not careful. Good luck with the whisper‑quiet mesh.