---
title: "Comment by For sell Mx on \"Preventing Denial of Service Attacks in Smart Contracts: Implementing the Withdrawal Pattern\" | Hashnode"
description: "Great analogy with the bank withdrawal. As a dev, I've seen loops that iterate over unbounded arrays become the most common DoS trap in practice—it's easy to mi"
url: "https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9/comment/69e08cb087cf8cd2a4415742"
---

[Discussion](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9)

Comment [Preventing Denial of Service Attacks in Smart Contracts: Implementing the Withdrawal Pattern](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9)

[For sell Mx](https://hashnode.com/@mxsell)

[Apr 16](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9/comment/69e08cb087cf8cd2a4415742)

Great analogy with the bank withdrawal. As a dev, I've seen loops that iterate over unbounded arrays become the most common DoS trap in practice—it's easy to miss during testing until the list grows. This post rightly highlights that the vulnerability is often in the _logic_, not just the gas.