From 5d6535973856f54f5e940fc030083aababa76893 Mon Sep 17 00:00:00 2001 From: paulgs9988 <69936006+paulgs9988@users.noreply.github.com> Date: Wed, 22 Jan 2025 15:25:19 -0500 Subject: [PATCH] Update 07-message-delivery.mdx Just noticed an unnecessary repetition of "required" and wanted to test out the "Edit on Github" button in the UI. I may go back and commit some changes to previous sections that I noticed might be helpful. Signed-off-by: paulgs9988 <69936006+paulgs9988@users.noreply.github.com> --- .../09-avalanche-warp-messaging/07-message-delivery.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/academy/interchain-messaging/09-avalanche-warp-messaging/07-message-delivery.mdx b/content/academy/interchain-messaging/09-avalanche-warp-messaging/07-message-delivery.mdx index d59dad42f31..1863186fcd4 100644 --- a/content/academy/interchain-messaging/09-avalanche-warp-messaging/07-message-delivery.mdx +++ b/content/academy/interchain-messaging/09-avalanche-warp-messaging/07-message-delivery.mdx @@ -8,7 +8,7 @@ icon: BookOpen import { Step, Steps } from 'fumadocs-ui/components/steps'; -Next, the AWM Relayer delivers the message with the aggregated signature by simply submitting a transaction to the destination Avalanche L1. The transaction is propagated through the validator set of the destination blockchain just as any other regular transaction would. +Next, the AWM Relayer delivers the message with the aggregated signature by simply submitting a transaction to the destination Avalanche L1. The transaction is propagated through the validator set of the destination blockchain just as any other regular transaction would be. In order to submit the transaction, the AWM Relayer needs access to the private key of a wallet holding the gas token of the destination blockchain to sign the transaction. @@ -27,7 +27,7 @@ The verifying validators of the destination L1 each query the validator set of t ### Verify Sufficient Stake Weight: -First, the verifying validators are checking if the combined stake weight of the validators that have signed the Warp message is large enough to accept the message (e.g. validators representing 50% of the total stake have signed the message). The required stake weight required to accept a message from a source chain can be set arbitrarily by the destination chain. An Avalanche L1 may require 50% for chain A and 90% for chain B. If the stake weight of the validators of the aggregate signature is insufficient the message is rejected. +First, the verifying validators are checking if the combined stake weight of the validators that have signed the Warp message is large enough to accept the message (e.g. validators representing 50% of the total stake have signed the message). The required stake weight to accept a message from a source chain can be set arbitrarily by the destination chain. An Avalanche L1 may require 50% for chain A and 90% for chain B. If the stake weight of the validators of the aggregate signature is insufficient the message is rejected. @@ -63,4 +63,4 @@ Even though this would make the verification much faster, there is a security is The only way to verify that is to aggregate the public keys of the signing validators and compare it to the one sent by the AWM Relayer. Therefore, it is pointless to attach it to the message. - \ No newline at end of file +