<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Best Practices on Mr.Yam</title><link>https://mr.nickyam.com/tags/best-practices/</link><description>Recent content in Best Practices on Mr.Yam</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 17 Oct 2026 10:02:00 +0800</lastBuildDate><atom:link href="https://mr.nickyam.com/tags/best-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Secure Exchange API Keys for Crypto Trading Bots</title><link>https://mr.nickyam.com/Crypto/How-to-Secure-Exchange-API-Keys-for-Crypto-Trading-Bots/</link><pubDate>Sat, 17 Oct 2026 10:02:00 +0800</pubDate><guid>https://mr.nickyam.com/Crypto/How-to-Secure-Exchange-API-Keys-for-Crypto-Trading-Bots/</guid><description>&lt;p&gt;If you run any kind of automated trading — a simple rebalancing script, a grid bot, or a full strategy engine — you cannot avoid the exchange &lt;strong&gt;API key&lt;/strong&gt;. It is the credential that lets your code move money. Functionally, it belongs to the same family as a database password or a cloud account key, and it deserves the same discipline: &lt;strong&gt;grant the minimum permission necessary, and nothing more.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This guide translates the common-sense engineering practices around API keys into the specific context of crypto exchanges, and expands on the basics with the details that actually get skipped — rotation, multi-key segmentation, and what real-world breaches look like when these controls are missing. It contains no real keys and no platform-specific click-through instructions; for the latter, defer to your exchange&amp;rsquo;s own documentation.&lt;/p&gt;</description></item></channel></rss>