EMBO Protocol — Emergency Memory Blackout

The XColdPro protocol that releases sensitive data left in memory and kills the process outright, instead of closing the application gracefully and hoping.

What EMBO does

When a session ends or an emergency shutdown is triggered, EMBO drops every reference to the wallet material held during that session and then terminates the process, rather than letting the application exit normally. The aim is to reduce what could be recovered afterwards from a machine that is seized, resold or inspected.

What EMBO actually does

EMBO releases the references, runs three successive garbage-collection passes, and then terminates the process without a normal exit path: no handlers run, no buffers flush, no state is written out. The process kill is what returns the memory to the operating system. It is not a byte-level overwrite of every address that held a secret, and XColdPro does not describe it as one — a userspace application cannot honestly guarantee that.

Instant by design

EMBO does not play an animation and does not wait: the interface reaches its SAFE state and hands off immediately. An emergency control that spends seconds on a progress display is not an emergency control, which is why the earlier animated version was removed.

Where it fits

EMBO covers the residue a session leaves behind on the machine you used. It is one layer among several — Omega handles evacuating funds under duress, Lazarus handles what happens if you are gone — and none of them replaces keeping the machine air-gapped in the first place.