-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs[message-relayer]: add a README and improve the interface for gen…
…erating proofs (#1002) * docs[message-relayer]: add basic docs and clean up an interface * chore: add changeset
- Loading branch information
1 parent
750a502
commit 9d39121
Showing
3 changed files
with
83 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
'@eth-optimism/message-relayer': patch | ||
--- | ||
|
||
Adds a README and cleans up the interface for generating messages and proofs |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
# @eth-optimism/message-relayer | ||
|
||
This package contains: | ||
|
||
1. A service for relaying messages from L2 to L1. | ||
2. Utilities for finding these messages and relaying them. | ||
|
||
## Installation | ||
|
||
``` | ||
yarn add @eth-optimism/message-relayer | ||
``` | ||
|
||
## Relay Utilities | ||
|
||
### getMessagesAndProofsForL2Transaction | ||
|
||
Finds all L2 => L1 messages sent in a given L2 transaction and generates proof for each. | ||
|
||
#### Usage | ||
|
||
```typescript | ||
import { getMessagesAndProofsForL2Transaction } from '@eth-optimism/message-relayer' | ||
|
||
const main = async () => { | ||
const l1RpcProviderUrl = 'https://layer1.endpoint' | ||
const l2RpcProviderUrl = 'https://layer2.endpoint' | ||
const l1StateCommitmentChainAddress = 'address of OVM_StateCommitmentChain from deployments page' | ||
const l2CrossDomainMessengerAddress = 'address of OVM_L2CrossDomainMessenger from deployments page' | ||
const l2TransactionHash = 'hash of the transaction with messages to relay' | ||
|
||
const messagePairs = await getMessagesAndProofsForL2Transaction( | ||
l1RpcProviderUrl, | ||
l2RpcProviderUrl, | ||
l1StateCommitmentChainAddress, | ||
l2CrossDomainMessengerAddress, | ||
l2TransactionHash | ||
) | ||
|
||
console.log(messagePairs) | ||
// Will log something along the lines of: | ||
// [ | ||
// { | ||
// message: { | ||
// target: '0x...', | ||
// sender: '0x...', | ||
// message: '0x...', | ||
// messageNonce: 1234... | ||
// }, | ||
// proof: { | ||
// // complicated | ||
// } | ||
// } | ||
// ] | ||
|
||
// You can then do something along the lines of: | ||
// for (const { message, proof } of messagePairs) { | ||
// await l1CrossDomainMessenger.relayMessage( | ||
// message.target, | ||
// message.sender, | ||
// message.message, | ||
// message.messageNonce, | ||
// proof | ||
// ) | ||
// } | ||
} | ||
|
||
main() | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters