# The Zero-Storage Model #### The Problem with Keystores Most software wallets (MetaMask, Phantom, etc.) rely on a "Keystore" model. They generate a private key, encrypt it with your password, and save it to your device's hard drive or local storage. * **Vulnerability:** If malware infects your device, it can steal the encrypted file. The attacker then has infinite time to brute-force your password offline. * **Forensics:** If your device is seized or lost, the data remains on the disk. #### The EtheLock Solution: On-Demand Derivation EtheLock utilizes a zero-storage architecture. Your private key is never written to a permanent storage medium (Hard Drive, SSD, or Flash Memory). 1. **Generation:** When you tap your card and enter your PIN, the key is mathematically derived in the device's volatile memory (RAM). 2. **Action:** The key is used immediately to sign the specific transaction or derive the public address. 3. **Destruction:** The instant the operation is complete, the memory space containing the private key is overwritten and cleared. #### Anti-Forensics Because the key is ephemeral, there is no file to steal. An attacker examining your phone or computer will find no trace of your wallet credentials, even with advanced forensic tools. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ethelock.xyz/4-security-architecture/the-zero-storage-model.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.