added relaying
This commit is contained in:
parent
12bce8dea0
commit
f6eae49cdd
|
@ -70,6 +70,7 @@
|
|||
- [Solana CLI]()
|
||||
- [Anchor]()
|
||||
- [Algorand]()
|
||||
- [CosmWasm]()
|
||||
- [Sending Messages](./development/messages/sending/overview.md)
|
||||
- [EVM](./development/messages/sending/evm.md)
|
||||
- [Solana]()
|
||||
|
@ -82,11 +83,10 @@
|
|||
- [CosmWasm]()
|
||||
- [Relaying Messages](./development/messages/relaying/overview.md)
|
||||
- [Manual Relays]()
|
||||
- [Rest Relayers]()
|
||||
- [Spy Relayer]()
|
||||
- [REST & Spy Relayer]()
|
||||
- [Generic Relayers]()
|
||||
- [Receving Messages]()
|
||||
- [EVM]()
|
||||
- [Receving Messages](./development/messages/receiving/overview.md)
|
||||
- [EVM](./development/messages/receiving/evm.md)
|
||||
- [Solana]()
|
||||
- [Algorand]()
|
||||
- [CosmWasm]()
|
||||
|
@ -95,13 +95,6 @@
|
|||
- [Prerequistes]()
|
||||
- [EVM]()
|
||||
- [Lever Puzzle]()
|
||||
- [Tools]()
|
||||
- [Testnet]()
|
||||
- [Wormhole Explorer]()
|
||||
- [Bridge UI]()
|
||||
- [Tilt]()
|
||||
- [Wormhole SDK]()
|
||||
|
||||
---
|
||||
|
||||
# Portal Token Bridge
|
||||
|
@ -122,6 +115,7 @@
|
|||
|
||||
- [Glossary]()
|
||||
- [Reference]()
|
||||
- [Tools] (./reference/tools.md)
|
||||
- [Github & Useful Links](./reference/github.md)
|
||||
- [Deployed Contracts](./reference/contracts.md)
|
||||
- [RPC Nodes](./reference/rpcnodes.md)
|
||||
|
|
|
@ -1 +1,15 @@
|
|||
# Relaying Messages
|
||||
# Relaying Messages
|
||||
|
||||
Relaying Messages can be done one of three ways:
|
||||
|
||||
1. Manual Relaying
|
||||
|
||||
Manual Relaying is usally done on the front end, and has the front end fetch the VAA it just created and then submit on the target chain. This means the user ends up paying for the gas fee to submit the tx on the target chain and has to go through the additional step.
|
||||
|
||||
2. Protocol Specific Relayers
|
||||
|
||||
Protocols and Apps can run their own relayers, listening to messages as they are created by the Core Bridge and submitting them to their application on the target chain. This is the ideal user experience but means more work for the developer.
|
||||
|
||||
3. Generic Relayers
|
||||
|
||||
Generic Relayers can pick up any app or protocol's messages and submit them to the target chain for a fee. This is the ideal developer and user experience, but still being developed.
|
Loading…
Reference in New Issue