You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 4, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
## Overview
6
6
7
-
RIP-7755 is a Rollup Improvement Proposal designed to establish a standardized, permissionless, and decentralized protocol for low-level cross-chain calls. By implementing immutable on-chain rules that incentivize off-chain participants, known as “fulfillers” in this context, to compete for transaction fees associated with cross-chain calls, we anticipate a significant enhancement in user experience without compromising on security or decentralization.
7
+
RIP-7755 is a Rollup Improvement Proposal designed to establish a standardized, permissionless, and decentralized protocol for low-level cross-chain calls. By implementing immutable onchain rules that incentivize offchain participants, known as “fulfillers” in this context, to compete for transaction fees associated with cross-chain calls, we anticipate a significant enhancement in user experience without compromising on security or decentralization.
8
8
9
9
When a user initiates a request for a cross-chain call, it is accompanied by a financial incentive for the first actor who can successfully execute the call. This reward is granted to the fulfiller only if they can provide cryptographic proof that the cross-chain call was executed successfully and correctly. One method to achieve this is through the use of storage proofs.
/// @notice A standardized interface for a valid Precheck Contract compatible with RIP-7755.
11
-
///
12
-
/// A cross-chain-call can optionally specify a Precheck Contract used to verify some arbitrary fulfillment condition during the `fulfill` transaction.
13
-
/// To specify a Precheck contract, set its address in a global request attribute using the `_PRECHECK_ATTRIBUTE_SELECTOR` prefix.
14
-
/// In order for the cross chain call to succeed with a precheck, the Precheck contract must inherit this interface and implement `precheckCall`.
10
+
/// @notice A standardized interface for a valid Precheck Contract compatible with RIP-7755. A cross-chain-call can
11
+
/// optionally specify a Precheck Contract used to verify some arbitrary fulfillment condition during the
12
+
/// `fulfill` transaction. To specify a Precheck contract, set its address in a global request attribute using
13
+
/// the `_PRECHECK_ATTRIBUTE_SELECTOR` prefix. In order for the cross chain call to succeed with a precheck,
14
+
/// the Precheck contract must inherit this interface and implement `precheckCall`.
15
15
interfaceIPrecheckContract {
16
16
/// @notice A precheck function declaration.
17
17
///
18
-
/// @param sourceChain The CAIP-2 chain identifier of the source chain.
19
-
/// @param sender The CAIP-10 account address of the sender.
20
-
/// @param messages The messages to be included in the request.
18
+
/// @param sourceChain The CAIP-2 chain identifier of the source chain.
19
+
/// @param sender The CAIP-10 account address of the sender.
20
+
/// @param messages The messages to be included in the request.
21
21
/// @param globalAttributes The attributes array.
22
-
/// @param caller The address of the filler account that submitted the transaction to RIP7755Inbox.
22
+
/// @param caller The address of the filler account that submitted the transaction to RIP7755Inbox.
0 commit comments