Starting this week, we'll be reaching out to top security researchers to ask a few important questions and share their perspectives here. This week, I reached out to @gowtham_ponnana , a Senior Security Researcher, someone who lead Security teams and also worked as Head of Security Services for an CEX, to ask: What's one thing protocols should do after an audit that most teams still overlook? Here's what he had to say: "The most common and recurring issue that the teams did is that: they immediately push it to production. But this is what I tell my team or my clients - After an audit, sit back and check with Researchers on any specific implementatios or ideas. Most of the security researchers would love to do it. Importantly let them see the deployment scripts (or even better, ask them to write them) and follow up with them till the protocol hits production carefully. Many protocols miss this. They simply avoid talking to researchers post audits, which barely covers deployment stuff. For Researchers -- Do check whether the production code is 100% matching with code you audited in the end. Of course there are many more OPSEC things, but the main thing is, I ask them to set up a bug bounty program (at least self-hosted). It brings you a good reputation and improves security throughout." Thanks, Gowtham , for sharing your insights. My few cents: In my opinion, Gowtham has covered everything. Apart from that, I also advise our clients to use separate wallets and devices exclusively for signing and nothing else. I also recommend working in containerized environments and never mixing work with your personal environment.