---
title: "Comment by Mm Cc on \"Preventing Denial of Service Attacks in Smart Contracts: Implementing the Withdrawal Pattern\" | Hashnode"
description: "Great point about the withdrawal pattern vulnerability. A complementary practice is to use a \"pull over push\" design for payments, where users withdraw funds th"
url: "https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9/comment/69e067a01e34081e127cdff1"
---

[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)

[Mm Cc](https://hashnode.com/@mmcc)

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

Great point about the withdrawal pattern vulnerability. A complementary practice is to use a "pull over push" design for payments, where users withdraw funds themselves from a separate contract, preventing a single failed transaction from blocking others.