From 94b01a5e60f9bb595054f8b4e63c33a307a26195 Mon Sep 17 00:00:00 2001 From: Ilaria <43253244+ilariae@users.noreply.github.com> Date: Wed, 31 Jul 2024 10:54:09 +0200 Subject: [PATCH] Update learn/architecture.md Co-authored-by: Erin Shaben --- learn/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/learn/architecture.md b/learn/architecture.md index c0d13578..e82cb3ce 100644 --- a/learn/architecture.md +++ b/learn/architecture.md @@ -16,7 +16,7 @@ Wormhole has several noteworthy components. Before we discuss each component in ## On-Chain Components -- **Emitter** - a contract that calls the publish message method on the Core Contract. The core contract will write an event to the Transaction Logs with details about the emitter and sequence number to identify the message. This may be your [xDapp](#){target=\_blank} or an existing ecosystem protocol +- **Emitter** - a contract that calls the publish message method on the Core Contract. The Core Contract will write an event to the transaction logs with details about the emitter and sequence number to identify the message. This may be your [xDapp](#){target=\_blank} or an existing ecosystem protocol - **[Wormhole core contract](#){target=\_blank}** - primary contract, this is the contract which the Guardians observe and which fundamentally allows for cross-chain communication - **Transaction Log** - blockchain-specific logs that allow the Guardians to observe messages emitted by the core contract