From 4b46856e0f6304f93fe1c3dda44d42ec31bbf995 Mon Sep 17 00:00:00 2001 From: Pete Date: Thu, 6 Feb 2025 13:50:43 -0600 Subject: [PATCH] Update arbitrum-docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- arbitrum-docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arbitrum-docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx b/arbitrum-docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx index 760ae67c4..5b432121f 100644 --- a/arbitrum-docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx +++ b/arbitrum-docs/how-arbitrum-works/10-l1-to-l2-messaging.mdx @@ -153,7 +153,7 @@ function sendL2MessageFromOrigin( Unsigned messages allow a Parent chain sender to specify transaction parameters without an EOA signature. Because there is no signature, **the sender's address must be aliased on the child chain** (see the [Address aliasing](#address-aliasing) section for the rationale.). The delayed inbox provides four main methods for unsigned messages, divided based on whether the sender is an EOA or a contract and whether it includes parent chain funds: -1. **Unsigned from EOAs**: These methods incorporate a none for replay protection, similar to standard EOA-based transaction on Ethereum. +1. **Unsigned from EOAs**: These methods incorporate a none-for replay protection, similar to standard EOA-based Ethereum transactions. - `sendL1FundedUnsignedTransaction` - Tranfers value from the parent to child chain along with the transaction