Skip to content

Commit

Permalink
Update 03-warp-message-format.mdx
Browse files Browse the repository at this point in the history
update sentence

Signed-off-by:  ochuko awhe <7204868+amochuko@users.noreply.github.com>
  • Loading branch information
amochuko authored Sep 7, 2024
1 parent ab750cc commit 3229aaa
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ authors: [martineckardt]
icon: BookOpen
---

Warp Messages have a minimal message format only contains the absolute necessary data for the transportation:
Warp Messages have a minimal message format that only contains the absolute necessary data for the transportation:

- **NetworkID:** The ID of the Network (Mainnet, Fuji Test Network, Local Test Network). This is included as a security mechanisms, so messages from the Fuji Test Network cannot be replayed on the Mainnet.
- **SourceChainID:** The chainID where the message originates from. This is not the EVM chain ID you may know from adding a network to a wallet, but the blockchain ID on the P-Chain. The P-Chain uses the transaction ID of the transaction that created those blockchain on the P-Chain for the chain ID, e.g.: 0xd7cdc6f08b167595d1577e24838113a88b1005b471a6c430d79c48b4c89cfc53
Expand All @@ -15,4 +15,4 @@ Warp Messages have a minimal message format only contains the absolute necessary

Every Warp message can be uniquely identified by its ID: the SHA256 hash of the serialized message (NetworkID, SourceChainID, SourceAddress & Payload).

The fields above are actually an UnsignedMessage. Hence, it has not been attached an aggregated signature yet. We will examine this in the following sections.
The fields above are actually an UnsignedMessage. Hence, it has not been attached an aggregated signature yet. We will examine this in the following sections.

0 comments on commit 3229aaa

Please sign in to comment.