Module starknet_devnet_core::messaging
source · Expand description
Messaging module.
This module contains code related to messaging feature. The messaging is composed of two major actors:
- The Starknet sequencer, which is in charge of gathering messages from L1 and executing them.
- The Starknet Core Contract, an Ethereum contract, that is generating the logs to send message to L2 and computing/ref-counting messages hashes for messages sent to L1.
Being a devnet, this project is embedding an Ethereum contract (MockStarknetMessaging) that mocks the behavior of the Starknet Core Contract by adding a method to manually increment the ref-counting of message hashes. This ensures that messages can be consumed on L1 without actually waiting for the proof to be generated (at it is done on Starknet in production).
§Receive message from L1
The Starknet sequencer (the devnet being the sequencer in this project)
is in charge of fetching the logs from Starknet Core Contract from Ethereum network.
In this project, the logs are emitted by the MockStarknetMessaging contract method
sendMessageToL2.
Once a log is gathered, a L1HandlerTransaction is executed internally, without
being signed by any account.
§Send message to L1
To send messages to L1, any Starknet contract can use the send_message_to_l1 syscall.
This will have the effect of adding, in the transaction output, the content
of the message.
By collecting those messages from transactions output, the devnet
uses the mocked functionality of manually incrementing the ref-count of a message
to make it available for consumption on L1.
This is done my sending a transaction to the Ethereum node, to the MockStarknetMessaging
contract (mockSendMessageFromL2 entrypoint).
Re-exports§
pub use ethereum::EthereumMessaging;