Skip to content

Commit

Permalink
Changes in auto generated contracts folders
Browse files Browse the repository at this point in the history
  • Loading branch information
@Hugoo
Hugoo committed Nov 6, 2023
1 parent fd39ed5 commit 1b3b05e
Show file tree
Hide file tree
Showing 19 changed files with 111 additions and 111 deletions.
10 changes: 5 additions & 5 deletions docs/contracts/contracts/LSP0ERC725Account/LSP0ERC725Account.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1196,7 +1196,7 @@ This function does not forward to the extension contract the `msg.value` receive
If you would like to forward the `msg.value` to the extension contract, you can override the code of this internal function as follow:

```solidity
(bool success, bytes memory result) = extension.call{value: msg.value}(
(bool success, bytes memory result) = extension.call\{value: msg.value\}(
abi.encodePacked(callData, msg.sender, msg.value)
);
```
Expand Down Expand Up @@ -1464,11 +1464,11 @@ Emitted when the [`universalReceiver`](#universalreceiver) function was called w

| Name | Type | Description |
| ---------------------- | :-------: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `from` **`indexed`** | `address` | The address of the EOA or smart contract that called the {universalReceiver(...)} function. |
| `value` **`indexed`** | `uint256` | The amount sent to the {universalReceiver(...)} function. |
| `from` **`indexed`** | `address` | The address of the EOA or smart contract that called the \{universalReceiver(...)\\} function. |
| `value` **`indexed`** | `uint256` | The amount sent to the \{universalReceiver(...)\\} function. |
| `typeId` **`indexed`** | `bytes32` | A `bytes32` unique identifier (= _"hook"_)that describe the type of notification, information or transaction received by the contract. Can be related to a specific standard or a hook. |
| `receivedData` | `bytes` | Any arbitrary data that was sent to the {universalReceiver(...)} function. |
| `returnedValue` | `bytes` | The value returned by the {universalReceiver(...)} function. |
| `receivedData` | `bytes` | Any arbitrary data that was sent to the \{universalReceiver(...)\\} function. |
| `returnedValue` | `bytes` | The value returned by the \{universalReceiver(...)\\} function. |

<br/>

Expand Down
2 changes: 1 addition & 1 deletion docs/contracts/contracts/LSP17Extensions/Extension4337.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ Must validate caller is the entryPoint. Must validate the signature and nonce

| Name | Type | Description |
| ---- | :-------: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `0` | `uint256` | packaged ValidationData structure. use `_packValidationData` and `_unpackValidationData` to encode and decode <20-byte> sigAuthorizer - 0 for valid signature, 1 to mark signature failure, otherwise, an address of an "authorizer" contract. <6-byte> validUntil - last timestamp this operation is valid. 0 for "indefinite" <6-byte> validAfter - first timestamp this operation is valid If an account doesn't use time-range, it is enough to return SIG_VALIDATION_FAILED value (1) for signature failure. Note that the validation code cannot use block.timestamp (or block.number) directly. |
| `0` | `uint256` | packaged ValidationData structure. use `_packValidationData` and `_unpackValidationData` to encode and decode \<20-byte\> sigAuthorizer - 0 for valid signature, 1 to mark signature failure, otherwise, an address of an "authorizer" contract. \<6-byte\> validUntil - last timestamp this operation is valid. 0 for "indefinite" \<6-byte\> validAfter - first timestamp this operation is valid If an account doesn't use time-range, it is enough to return SIG_VALIDATION_FAILED value (1) for signature failure. Note that the validation code cannot use block.timestamp (or block.number) directly. |

<br/>

Expand Down
2 changes: 1 addition & 1 deletion docs/contracts/contracts/LSP25ExecuteRelayCall/LSP25MultiChannelNonce.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ The address of the signer will be recovered using the LSP25 signature format.
| -------------------- | :-------: | ----------------------------------------------------------------------------------------------------------------------- |
| `signature` | `bytes` | A 65 bytes long signature generated according to the signature format specified in the LSP25 standard. |
| `nonce` | `uint256` | The nonce that the signer used to generate the `signature`. |
| `validityTimestamps` | `uint256` | The validity timestamp that the signer used to generate the signature (See {\_verifyValidityTimestamps} to learn more). |
| `validityTimestamps` | `uint256` | The validity timestamp that the signer used to generate the signature (See \{\_verifyValidityTimestamps\} to learn more). |
| `msgValue` | `uint256` | The amount of native tokens intended to be sent for the relay transaction. |
| `callData` | `bytes` | The calldata to execute as a relay transaction that the signer signed for. |

Expand Down
Loading

0 comments on commit 1b3b05e

Please sign in to comment.