From 086c3225f58b0af9f3cd559015856d01a36d15e2 Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Sun, 14 Jan 2024 20:20:52 +0200 Subject: [PATCH] Update erc-7562.md: fixed typo --- erc/ERCS/erc-7562.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/erc/ERCS/erc-7562.md b/erc/ERCS/erc-7562.md index 8a17699a8..a44515165 100644 --- a/erc/ERCS/erc-7562.md +++ b/erc/ERCS/erc-7562.md @@ -369,7 +369,7 @@ The alt-mempool "topic" is a unique identifier. By convention, this is the IPFS * **[ALT-010]** The bundler listens to the alt-mempool "topic" over the P2P protocol * **[ALT-020]** The alt mempool rules MUST be checked only when a canonical rule is violated * That is, if validation follows the canonical rules above, it is not considered part of an alt-mempool. -* **[ALT-021]** Such a `UserOperation` (that violates the cannonical rules) is checked against all the "alternate mempools", and is considered part of all those alt-mempools +* **[ALT-021]** Such a `UserOperation` (that violates the canonical rules) is checked against all the "alternate mempools", and is considered part of all those alt-mempools * **[ALT-030]** Bundlers SHOULD forward `UserOperations` to other bundlers only once, regardless of how many (shared) alt-mempools they have. \ The receiving bundler validates the `UserOperations`, and based on the above rules (and subscribed alt-mempools) decides which alt-mempools to propagate it to. * **[ALT-040]** opsInclude and opsSeen of entities are kept per alt-mempool. That is, an entity can be considered throttled (or banned) in one mempool, while still active on another.