From c945eba63e54bb699e5d3dcfd5e7a6aa0e7e2280 Mon Sep 17 00:00:00 2001 From: ABDul Rehman Date: Thu, 14 Mar 2024 14:08:51 +0500 Subject: [PATCH] Update README.md Typo Fixed! --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 038cb92c9..ee3764723 100644 --- a/README.md +++ b/README.md @@ -38,4 +38,4 @@ NTT supports rate-limiting both on the sending and destination chains. If a tran ## Cancel-Flows -If users bridge frequently between a given source chain and destination chain, the capacity could be exhausted quickly. This can leave other users rate-limited, potentially delaying their transfers. To mitigate this issue, the outbound transfer cancels the inbound rate-limit on the source chain (refills the inbound rate-limit by an amount equal to that of the outbound transfer amount) and vice-versa, the inbound transfer cancels the outbound rate-limit on the destination chain (refills the outbound raste-limit by an amount equal to the inbound transfer amount). +If users bridge frequently between a given source chain and destination chain, the capacity could be exhausted quickly. This can leave other users rate-limited, potentially delaying their transfers. To mitigate this issue, the outbound transfer cancels the inbound rate-limit on the source chain (refills the inbound rate-limit by an amount equal to that of the outbound transfer amount) and vice-versa, the inbound transfer cancels the outbound rate-limit on the destination chain (refills the outbound rate-limit by an amount equal to the inbound transfer amount).