From 9a7a95cbea3ded600cfaa559bd970ea155d169eb Mon Sep 17 00:00:00 2001
From: lightclient <14004106+lightclient@users.noreply.github.com>
Date: Thu, 7 Oct 2021 10:28:15 +0300
Subject: [PATCH] Update EIPS/eip-4337.md

---
 EIPS/eip-4337.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/EIPS/eip-4337.md b/EIPS/eip-4337.md
index 4db15b430f27c..8adc0ff6b7ee6 100644
--- a/EIPS/eip-4337.md
+++ b/EIPS/eip-4337.md
@@ -102,7 +102,7 @@ During the verification loop, in addition to calling `validateUserOp`, the `hand
 
 During the execution loop, the `handleOps` execution must call `postOp` on the paymaster after making the main execution call. It must guarantee the execution of `postOp`, by making the main execution inside an inner call context, and if the inner call context reverts attempting to call `postOp` again in an outer call context.
 
-Maliciously crafted paymasters _can_ DoS the system. To prevent this, we use a paymaster reputation system; see the [reputation, throttling and banning section](#Reputation-scoring-and-throttling%2Fbanning-for-paymasters) for details.
+Maliciously crafted paymasters _can_ DoS the system. To prevent this, we use a paymaster reputation system; see the [reputation, throttling and banning section](#reputation-scoring-and-throttlingbanning-for-paymasters) for details.
 
 The paymaster interface is as follows: