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/crosschain.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ function sendMessage(
95
95
// Post on all gateways
96
96
Outbox[] memory outbox = new Outbox[](_gateways.length());
97
97
bool needsId = false;
98
-
for (uint256 i = 0; i < outbox.length; `i) {
98
+
for (uint256 i = 0; i < outbox.length; ++i) {
99
99
address gateway = _gateways.at(i);
100
100
// send message
101
101
bytes32 id = IERC7786GatewaySource(gateway).sendMessage(
@@ -132,7 +132,7 @@ function receiveMessage(
132
132
if (_gateways.contains(msg.sender) && !tracker.receivedBy[msg.sender]) {
133
133
// Count number of time received
134
134
tracker.receivedBy[msg.sender] = true;
135
-
`tracker.countReceived;
135
+
++tracker.countReceived;
136
136
emit Received(id, msg.sender);
137
137
138
138
// if already executed, leave gracefully
@@ -162,4 +162,4 @@ function receiveMessage(
162
162
}
163
163
```
164
164
165
-
The bridge is designed to be configurable. As an `Ownable` contract, it allows the owner to manage the list of trusted gateways and adjust the confirmation threshold. The `_gateways` list and threshold are initially set during contract deployment using the [`+_addGateway+`](/community-contracts/api/crosschain#ERC7786OpenBridge-_addGateway-address-) and [`+_setThreshold+`](/community-contracts/api/crosschain#ERC7786OpenBridge-_setThreshold-uint8-) functions. The owner can update these settings as needed to adapt to changing requirements or add new gateways.
165
+
The bridge is designed to be configurable. As an `Ownable` contract, it allows the owner to manage the list of trusted gateways and adjust the confirmation threshold. The `_gateways` list and threshold are initially set during contract deployment using the [`_addGateway`](/community-contracts/api/crosschain#ERC7786OpenBridge-_addGateway-address-) and [`_setThreshold`](/community-contracts/api/crosschain#ERC7786OpenBridge-_setThreshold-uint8-) functions. The owner can update these settings as needed to adapt to changing requirements or add new gateways.
Copy file name to clipboardExpand all lines: content/community-contracts/index.mdx
+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
@@ -42,4 +42,4 @@ Contracts in the community library are provided as is, with no particular guaran
42
42
43
43
Similarly, the code has no backward compatibility guarantees.
44
44
45
-
We kindly ask to report any issue directly to our security mailto:security@openzeppelin.org[contact]. The team will do its best to assist and mitigate any potential misuses of the library. However, keep in mind the flexibility assumed for this repository may relax our assessment.
45
+
We kindly ask to report any issue directly to our security [contact](mailto:security@openzeppelin.org). The team will do its best to assist and mitigate any potential misuses of the library. However, keep in mind the flexibility assumed for this repository may relax our assessment.
Copy file name to clipboardExpand all lines: content/confidential-contracts/index.mdx
+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
@@ -14,4 +14,4 @@ Contracts in the confidential contracts library are provided as is, with no part
14
14
15
15
Similarly, the code has no backward compatibility guarantees.
16
16
17
-
We kindly ask to report any issue directly to our security mailto:security@openzeppelin.org[contact]. The team will do its best to assist and mitigate any potential misuses of the library. However, keep in mind the flexibility assumed for this repository may relax our assessment.
17
+
We kindly ask to report any issue directly to our security [contact](mailto:security@openzeppelin.org). The team will do its best to assist and mitigate any potential misuses of the library. However, keep in mind the flexibility assumed for this repository may relax our assessment.
Copy file name to clipboardExpand all lines: content/confidential-contracts/token.mdx
+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
@@ -41,7 +41,7 @@ Setting an operator for any amount of time allows the operator to _***take all o
41
41
42
42
The token standard exposes transfer functions with and without callbacks. It is up to the caller to decide if a callback is necessary for the transfer. For smart contracts that support it, callbacks allow the operator approval step to be skipped and directly invoke the receiver contract via a callback.
43
43
44
-
Smart contracts that are the target of a callback must implement [`+IERC7984Receiver+`](/confidential-contracts/api/interfaces#IERC7984Receiver). After balances are updated for a transfer, the callback is triggered by calling the [`+onConfidentialTransferReceived+`](/confidential-contracts/api/interfaces#IERC7984Receiver-onConfidentialTransferReceived-address-address-euint64-bytes-) function. The function must either revert or return an `ebool` indicating success. If the callback returns false, the token transfer is reversed.
44
+
Smart contracts that are the target of a callback must implement [`IERC7984Receiver`](/confidential-contracts/api/interfaces#IERC7984Receiver). After balances are updated for a transfer, the callback is triggered by calling the [`onConfidentialTransferReceived`](/confidential-contracts/api/interfaces#IERC7984Receiver-onConfidentialTransferReceived-address-address-euint64-bytes-) function. The function must either revert or return an `ebool` indicating success. If the callback returns false, the token transfer is reversed.
Copy file name to clipboardExpand all lines: content/contracts/5.x/erc1155.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
@@ -71,9 +71,9 @@ The metadata uri can be obtained:
71
71
"https://game.example/api/item/{id}.json"
72
72
```
73
73
74
-
The `uri` can include the string `+id+` which clients must replace with the actual token ID, in lowercase hexadecimal (with no 0x prefix) and leading zero padded to 64 hex characters.
74
+
The `uri` can include the string `id` which clients must replace with the actual token ID, in lowercase hexadecimal (with no 0x prefix) and leading zero padded to 64 hex characters.
75
75
76
-
For token ID `2` and uri `+https://game.example/api/item/id.json+` clients would replace `+id+` with `0000000000000000000000000000000000000000000000000000000000000002` to retrieve JSON at `https://game.example/api/item/0000000000000000000000000000000000000000000000000000000000000002.json`.
76
+
For token ID `2` and uri `https://game.example/api/item/id.json` clients would replace `id` with `0000000000000000000000000000000000000000000000000000000000000002` to retrieve JSON at `https://game.example/api/item/0000000000000000000000000000000000000000000000000000000000000002.json`.
77
77
78
78
The JSON document for token ID 2 might look something like:
0 commit comments