|
61 | 61 | }} |
62 | 62 | /> |
63 | 63 | Signature Validation |
64 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/accounts#signature_validation"> |
| 64 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/accounts#signature_validation"> |
65 | 65 | Enables smart contracts to validate signatures through a standard <code>isValidSignature</code> method. Unlike EOAs |
66 | 66 | (regular accounts) that use private keys, this allows contracts to implement custom signature validation logic, making |
67 | 67 | them capable of acting as signing entities for operations like approvals, swaps, or any signed messages. |
|
77 | 77 | }} |
78 | 78 | /> |
79 | 79 | Account Bound |
80 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/accounts#erc_7739_signatures"> |
| 80 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/accounts#erc_7739_signatures"> |
81 | 81 | Enhances signature security by using a defensive rehashing scheme that prevents signature replay attacks across |
82 | 82 | multiple smart accounts owned by the same private key. This preserves the readability of signed contents while |
83 | 83 | ensuring each signature is uniquely bound to a specific account and chain. |
|
92 | 92 | }} |
93 | 93 | /> |
94 | 94 | ERC721 Holder |
95 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/api/token/erc721#ERC721Holder"> |
| 95 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/api/token/erc721#ERC721Holder"> |
96 | 96 | Implement native support for receiving ERC-721 tokens. |
97 | 97 | </HelpTooltip> |
98 | 98 | </label> |
|
105 | 105 | }} |
106 | 106 | /> |
107 | 107 | ERC1155 Holder |
108 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/api/token/erc1155#ERC1155Holder"> |
| 108 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/api/token/erc1155#ERC1155Holder"> |
109 | 109 | Implement native support for receiving ERC-1155 tokens. |
110 | 110 | </HelpTooltip> |
111 | 111 | </label> |
|
119 | 119 | }} |
120 | 120 | /> |
121 | 121 | Batched Execution |
122 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/accounts#batched_execution"> |
| 122 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/accounts#batched_execution"> |
123 | 123 | Enables atomic execution of multiple transactions in a single operation, reducing total transaction costs and |
124 | 124 | latency. |
125 | 125 | </HelpTooltip> |
|
164 | 164 | bind:value={opts.signer} |
165 | 165 | defaultValue="ECDSA" |
166 | 166 | helpContent="Defines the base signature validation mechanism for the account. This implementation will be used to validate user operations following ERC-4337 or by ERC-1271's <code>isValidSignature</code> to verify signatures on behalf of the account." |
167 | | - helpLink="https://docs.openzeppelin.com/contracts/accounts#selecting_a_signer" |
| 167 | + helpLink="https://docs.openzeppelin.com/contracts/5.x/accounts#selecting_a_signer" |
168 | 168 | > |
169 | 169 | <div class="checkbox-group"> |
170 | 170 | <label class:checked={opts.signer === 'ECDSA'}> |
171 | 171 | <input type="radio" bind:group={opts.signer} value="ECDSA" /> |
172 | 172 | ECDSA |
173 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/api/utils/cryptography#ECDSA"> |
| 173 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/api/utils/cryptography#ECDSA"> |
174 | 174 | Standard Ethereum signature validation using secp256k1. Validates signatures against a specified owner address, |
175 | 175 | making it suitable for accounts controlled by EOAs. |
176 | 176 | </HelpTooltip> |
177 | 177 | </label> |
178 | 178 | <label class:checked={opts.signer === 'ERC7702'}> |
179 | 179 | <input type="radio" bind:group={opts.signer} value="ERC7702" use:error={errors?.erc7702} /> |
180 | 180 | EOA Delegation |
181 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/eoa-delegation"> |
| 181 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/eoa-delegation"> |
182 | 182 | Special ECDSA validation that uses the account's own address as the signer. Enables EOAs to delegate execution |
183 | 183 | rights to the account while maintaining their native signature verification. |
184 | 184 | </HelpTooltip> |
185 | 185 | </label> |
186 | 186 | <label class:checked={opts.signer === 'Multisig'}> |
187 | 187 | <input type="radio" bind:group={opts.signer} value="Multisig" /> |
188 | 188 | Multisig |
189 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/multisig"> |
| 189 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/multisig"> |
190 | 190 | ERC-7913 multisignature validation requiring a minimum number of signatures to approve operations. The contract |
191 | 191 | maintains a set of authorized signers and validates that the number of valid signatures meets the threshold |
192 | 192 | requirement. |
|
195 | 195 | <label class:checked={opts.signer === 'MultisigWeighted'}> |
196 | 196 | <input type="radio" bind:group={opts.signer} value="MultisigWeighted" /> |
197 | 197 | Multisig Weighted |
198 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/multisig#multisignererc7913weighted"> |
| 198 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/multisig#multisignererc7913weighted"> |
199 | 199 | Weighted version of ERC-7913 multisignature validation. Signers have different voting weights, allowing for |
200 | 200 | flexible governance. The total weight of valid signatures must meet the threshold requirement. |
201 | 201 | </HelpTooltip> |
202 | 202 | </label> |
203 | 203 | <label class:checked={opts.signer === 'P256'}> |
204 | 204 | <input type="radio" bind:group={opts.signer} value="P256" /> |
205 | 205 | P256 |
206 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/api/utils/cryptography#P256"> |
| 206 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/api/utils/cryptography#P256"> |
207 | 207 | Signature validation using the NIST P-256 curve (secp256r1). Useful for integrating with external systems and |
208 | 208 | hardware that use this standardized curve, such as Apple's Passkeys or certain HSMs. |
209 | 209 | </HelpTooltip> |
210 | 210 | </label> |
211 | 211 | <label class:checked={opts.signer === 'RSA'}> |
212 | 212 | <input type="radio" bind:group={opts.signer} value="RSA" /> |
213 | 213 | RSA |
214 | | - <HelpTooltip link="https://docs.openzeppelin.com/contracts/api/utils/cryptography#RSA"> |
| 214 | + <HelpTooltip link="https://docs.openzeppelin.com/contracts/5.x/api/utils/cryptography#RSA"> |
215 | 215 | RSA PKCS#1 v1.5 signature validation following RFC8017. Enables integration with traditional PKI systems and |
216 | 216 | hardware security modules that use RSA keys. |
217 | 217 | </HelpTooltip> |
|
0 commit comments