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
Copy file name to clipboardExpand all lines: content/community-contracts/account-modules.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,12 @@ ERC-7579 defines a standardized interface for modular smart accounts. This stand
10
10
11
11
### Accounts
12
12
13
-
OpenZeppelin offers an implementation of an [`AccountERC7579`](/community-contracts/api/account#AccountERC7579) contract that allows installing modules compliant with this standard. There’s also an [`AccountERC7579Hooked`](/community-contracts/api/account#AccountERC7579Hooked) variant that supports installation of hooks. Like [most accounts](/contracts/5.x/accounts#handling-initialization), an instance should define an initializer function where the first module that controls the account will be set:
13
+
OpenZeppelin offers an implementation of an [`AccountERC7579`](/contracts/5.x/api/account#AccountERC7579) contract that allows installing modules compliant with this standard. There’s also an [`AccountERC7579Hooked`](/contracts/5.x/api/account#AccountERC7579Hooked) variant that supports installation of hooks. Like [most accounts](/contracts/5.x/accounts#handling-initialization), an instance should define an initializer function where the first module that controls the account will be set:
For simplicity, the [`AccountERC7579Hooked`](/community-contracts/api/account#AccountERC7579Hooked) only supports a single hook. A common workaround is to install a [single hook with a multiplexer pattern](https://github.com/rhinestonewtf/core-modules/blob/7afffccb44d73dbaca2481e7b92bce0621ea6449/src/HookMultiPlexer/HookMultiPlexer.sol) to extend the functionality to multiple hooks.
18
+
For simplicity, the [`AccountERC7579Hooked`](/contracts/5.x/api/account#AccountERC7579Hooked) only supports a single hook. A common workaround is to install a [single hook with a multiplexer pattern](https://github.com/rhinestonewtf/core-modules/blob/7afffccb44d73dbaca2481e7b92bce0621ea6449/src/HookMultiPlexer/HookMultiPlexer.sol) to extend the functionality to multiple hooks.
Copy file name to clipboardExpand all lines: content/community-contracts/api/crosschain.mdx
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -210,14 +210,14 @@ This function revert if:
210
210
chain.
211
211
* someone tries re-execute a message that was already successfully delivered. This includes gateways that call
212
212
this function a second time with a message that was already executed.
213
-
* the execution of the message (on the [`IERC7786Receiver`](interfaces#IERC7786Receiver) receiver) is successful but fails to return the
213
+
* the execution of the message (on the [`IERC7786Receiver`](./interfaces#IERC7786Receiver) receiver) is successful but fails to return the
214
214
executed value.
215
215
216
216
This function does not revert if:
217
217
218
218
* A known gateway delivers a message for the first time, and that message was already executed. In that case
219
219
the message is NOT re-executed, and the correct "magic value" is returned.
220
-
* The execution of the message (on the [`IERC7786Receiver`](interfaces#IERC7786Receiver) receiver) reverts. In that case a [`ERC7786OpenBridge.ExecutionFailed`](#ERC7786OpenBridge-ExecutionFailed-bytes32-)
220
+
* The execution of the message (on the [`IERC7786Receiver`](./interfaces#IERC7786Receiver) receiver) reverts. In that case a [`ERC7786OpenBridge.ExecutionFailed`](#ERC7786OpenBridge-ExecutionFailed-bytes32-)
Implementation of an ERC-7786 gateway destination adapter for the Axelar Network in dual mode.
738
738
739
-
The contract implements AxelarExecutable's [`ERC7579DelayedExecutor._execute`](account#ERC7579DelayedExecutor-_execute-address-bytes32-bytes32-bytes-) function to execute the message, converting Axelar's native
739
+
The contract implements AxelarExecutable's [`ERC7579DelayedExecutor._execute`](./account#ERC7579DelayedExecutor-_execute-address-bytes32-bytes32-bytes-) function to execute the message, converting Axelar's native
740
740
workflow into the standard ERC-7786.
741
741
742
742
<Callout>
@@ -965,9 +965,9 @@ Endpoint for creating a new message. If the message requires further (gateway sp
965
965
it can be sent to the destination chain, then a non-zero `outboxId` must be returned. Otherwise, the
966
966
message MUST be sent and this function must return 0.
967
967
968
-
* MUST emit a [`IERC7786GatewaySource.MessageSent`](interfaces#IERC7786GatewaySource-MessageSent-bytes32-bytes-bytes-bytes-uint256-bytes---) event.
968
+
* MUST emit a [`IERC7786GatewaySource.MessageSent`](./interfaces#IERC7786GatewaySource-MessageSent-bytes32-bytes-bytes-bytes-uint256-bytes---) event.
969
969
970
-
If any of the `attributes` is not supported, this function SHOULD revert with an [`IERC7786GatewaySource.UnsupportedAttribute`](interfaces#IERC7786GatewaySource-UnsupportedAttribute-bytes4-) error.
970
+
If any of the `attributes` is not supported, this function SHOULD revert with an [`IERC7786GatewaySource.UnsupportedAttribute`](./interfaces#IERC7786GatewaySource-UnsupportedAttribute-bytes4-) error.
971
971
Other errors SHOULD revert with errors not specified in ERC-7786.
972
972
973
973
</div>
@@ -1723,9 +1723,9 @@ Endpoint for creating a new message. If the message requires further (gateway sp
1723
1723
it can be sent to the destination chain, then a non-zero `outboxId` must be returned. Otherwise, the
1724
1724
message MUST be sent and this function must return 0.
1725
1725
1726
-
* MUST emit a [`IERC7786GatewaySource.MessageSent`](interfaces#IERC7786GatewaySource-MessageSent-bytes32-bytes-bytes-bytes-uint256-bytes---) event.
1726
+
* MUST emit a [`IERC7786GatewaySource.MessageSent`](./interfaces#IERC7786GatewaySource-MessageSent-bytes32-bytes-bytes-bytes-uint256-bytes---) event.
1727
1727
1728
-
If any of the `attributes` is not supported, this function SHOULD revert with an [`IERC7786GatewaySource.UnsupportedAttribute`](interfaces#IERC7786GatewaySource-UnsupportedAttribute-bytes4-) error.
1728
+
If any of the `attributes` is not supported, this function SHOULD revert with an [`IERC7786GatewaySource.UnsupportedAttribute`](./interfaces#IERC7786GatewaySource-UnsupportedAttribute-bytes4-) error.
1729
1729
Other errors SHOULD revert with errors not specified in ERC-7786.
0 commit comments