Storing the private key in a configuration file is no different from leaving the key stuck in the door. I’ve seen so many news reports about on-chain thefts lately—just a few days ago, someone got hacked for $3 million and even messaged the hacker asking to get half back. Often, it’s not the smart contract that’s complex—it’s just that the private key was stored too carelessly. That’s why I think @bluwhaleai’s recent node security upgrade is genuinely practical. Previously, the private key was stored in the config.yaml file; now, it’s no longer kept in any file at all. Instead, it’s held in protected memory, and after the node starts, the key is injected via a local Unix socket using command-line input. In simple terms: the private key is no longer sitting in the node’s configuration file—even if someone accesses the file, they won’t find the key ready to use. This improvement came directly from feedback by community node operators, and the team listened, updating the code accordingly. If you run a node, don’t forget to update your image! Security isn’t a one-time fix—it’s better to steadily improve based on feedback than to apologize after something goes wrong. solana:6ZnCkq5t8XG4q42b5JiVvU6hV5cZFaNdSBoFq5E7Vf9q