Update overview.md

Adjusted content for grammar, style and readability.
This commit is contained in:
Ian Traas 2022-08-09 10:29:34 -05:00 committed by GitHub
parent cbadcab772
commit ee861fc8eb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -1,9 +1,9 @@
# Overview of Receving Messages
The basic flow of receving messages requires you (or a relayer!) to submit the VAA to your application contract. This contract then calls the Core Bridge on the receving chain to check the message signatures against the stored guardian set signatures.
Receving messages requires you (or a relayer) to submit the VAA to your application contract. This contract then calls the Core Bridge on the receving chain to check the message signatures against the stored Guardian set signatures.
If those checks pass, then the application can check to see if it's a message that's already been processed before by checking it's sequence number against a store list of processed message sequence numbers.
If those checks pass, then the application can see if it's a message that's already been processed by checking its sequence number against a store list of processed message sequence numbers.
The final optional check is to make sure that the message came from an application from the source chain that we were expecting. Usually this is our own application, and should be registered during initialization steps (see [registration](../registration/overview.md)).
After we have ensured all those things are correct, we can go ahead and process the message according to the business logic in our application.
After we have ensured all those things are correct, we can process the message according to the business logic in our application.