Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message service: automatic claiming fix #686

Merged
merged 1 commit into from
Aug 15, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ The message service is responsible for cross-chain messages between Ethereum and
- Args:
- `_to`: the destination address on the destination chain
- `_fee`: the message service fee on the origin chain
- An optional field used to incentivize a Postman to perform `claimMessage(...)` automatically on the destination chain (this is not yet available)
- An optional field used to incentivize a Postman to perform `claimMessage(...)` automatically on the destination chain (not available when bridging from L2 to L1)
- `_calldata`: a flexible field that is generally created using `abi.encode(...)`
1. dApp uses the Postman SDK (details to come) to pay for the execution of messages on the destination layer by:
- Triggering the delivery
Expand Down