Storing private keys in config files is basically like leaving your keys in the door—what’s the difference? I’m honestly numb from all the recent news about on-chain thefts. Just a few days ago, I saw someone lose $3 million to hackers and even message them begging to get half of it back. Most of the time, it’s not that the contracts are super complicated—it’s just that people are way too careless about where they store their private keys. That’s why I think @bluwhaleai’s latest node security upgrade is pretty solid. Previously, private keys were stored in the `config.yaml` file, but now they’re no longer kept in files. Instead, they’re stored in protected memory, and after the node starts up, you feed the private key through a local Unix Socket using the command line. To put it simply, private keys are no longer sitting in the node’s config file. Even if someone gets their hands on the file, they won’t find the private key there. What’s cool is that this change came from feedback by node operators in the community. The team listened and directly upgraded the code. If you’re running a node, make sure to update your image files! When it comes to security, there’s no such thing as a one-and-done solution. Fixing things bit by bit based on feedback is way better than apologizing after something goes wrong, right? solana:6ZnCkq5t8XG4q42b5JiVvU6hV5cZFaNdSBoFq5E7Vf9q