source avatarKaleel | Graph Engineer

Share

Your audit checked the contract once, before launch. The moment it holds real money on mainnet, conditions change by the block, and an exploit can play out in minutes. So here's the question for every team heading to mainnet: what are your alerts? The fastest way I know to pick them starts with your threat model, because a threat model is already a graph. Stellar's threat modeling guide has you draw a data flow diagram, with users, processes and storage as nodes, data flows as edges, and trust boundaries wherever one part starts trusting input from another. 1. Walk every edge that crosses a trust boundary. 2. Name at least one STRIDE threat in each category. 3. Turn each threat into a signal. Privilege risk means watching signer changes and admin calls. Price manipulation means watching oracle moves past a threshold. A drain means baselining balances and outflows. 4. Give each signal a severity and set up the highest impact ones first. SDF's security tools repo on GitHub lists 30 example monitors across 6 projects, from account signer changes to stale price feeds, if you want a starting list. Which alert would you set first on your contract? https://t.co/QO5XBWa7Nw

No.0 picture
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.