From 1a14b8dcaa75724ff53d2af975aaa8b61f16ce89 Mon Sep 17 00:00:00 2001 From: Kariy Date: Tue, 3 Oct 2023 00:37:59 +0700 Subject: [PATCH] udpate doc --- crates/katana/core/src/service/messaging/mod.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/crates/katana/core/src/service/messaging/mod.rs b/crates/katana/core/src/service/messaging/mod.rs index 24acc3b156..b6d0e3d9e2 100644 --- a/crates/katana/core/src/service/messaging/mod.rs +++ b/crates/katana/core/src/service/messaging/mod.rs @@ -12,10 +12,10 @@ //! The sending of the messages is realized by collecting all the `messages_sent` from local //! execution of smart contracts using the `send_message_to_l1_syscall`. Once messages are //! collected, the hash of each message is computed and then registered on the settlement layer to -//! be consumed on the latter (by manually by sending a transaction on the settlement chain). -//! The hashes are registered using a custom contract that mimics the verification of Starknet block -//! on Ethereum, since this process of proving and verifying a block is not present with local dev -//! nodes. +//! be consumed on the latter (by manually sending a transaction on the settlement chain). The +//! hashes are registered using a custom contract that mimics the verification of Starknet state +//! updates on Ethereum, since the process of proving and verifying of state updates, and then +//! posting in on the settlement layer are not yet present in Katana. //! //! Katana also has a `starknet-messaging` feature, where an opiniated implementation of L2 <-> L3 //! messaging is implemented using Starknet as settlement chain.