certusone
/
xdapp-book
mirror of https://github.com/certusone/xdapp-book.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

fix typos/grammatical errors (#2)

This commit is contained in:
wonge97 2022-07-01 08:28:36 -05:00 committed by GitHub
parent d7f262228b
commit 8df85fd669
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/development/messages/registration/overview.md
View File

@ -2,6 +2,6 @@
This is not strictly required, but when writing xDapps, you want to listen for messages from *specific* apps on other chains, otherwise attacks could create fake applications that emit messages that *look* like what we expect, but have fake payloads.
To do this, we register the sending contract's addresses with the receiving contracts. Because each VAA has the contract address asked the core bridge to *emit* the VAA, we call the sending contracts *emitters*. Also, the emitters you're listening too, *do not* need to be your own contracts. You might want to listen to the emits of a different xDapp, in which case you'd register it's address in your code.
To do this, we register the sending contract's addresses with the receiving contracts. Because each VAA has the contract address that asked the core bridge to *emit* the VAA, we call the sending contracts *emitters*. Also, the emitters you're listening to *do not* need to be your own contracts. You might want to listen to the emits of a different xDapp, in which case you'd register it's address in your code.
Then, when receiving messages, we can check the VAA being submitted, and make sure that the VAA being submitted came from one of the contracts we were expecting and *from the chain* we were expecting.