From 0220eec21bb7987c0d17bcf61eb3ad66febb5f73 Mon Sep 17 00:00:00 2001 From: Akshay Date: Mon, 26 Aug 2024 15:53:59 +0200 Subject: [PATCH] Fix comment --- modules/4337/contracts/Safe4337Module.sol | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/4337/contracts/Safe4337Module.sol b/modules/4337/contracts/Safe4337Module.sol index 579c6ac0..2a860db1 100644 --- a/modules/4337/contracts/Safe4337Module.sol +++ b/modules/4337/contracts/Safe4337Module.sol @@ -228,7 +228,7 @@ contract Safe4337Module is IAccount, HandlerContext, CompatibilityFallbackHandle * A malicious bundler can manipulate the field(s) storing the signature length and pad additional bytes to the * dynamic part of the signatures which will make `_checkSignaturesLength` to return true. In such cases, it is * the responsibility of the Safe signature validator implementation, as an account owner, to check for additional - * bytes to it smart contract signature data. + * bytes. * @param signatures Signatures data. * @param threshold Signer threshold for the Safe account. * @return isValid True if length check passes, false otherwise.