Add documentation about the security of overrides (#3725)

pull/3728/head
Francisco 2 years ago committed by GitHub
parent c08c6e1b84
commit e2362ce74f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 5
      docs/modules/ROOT/pages/extending-contracts.adoc

@ -129,3 +129,8 @@ contract MyToken is ERC20 {
```
That's it! Enjoy simpler code using hooks!
== Security
The maintainers of OpenZeppelin Contracts are mainly concerned with the correctness and security of the code as published in the library, and the combinations of base contracts with the official extensions from the library.
Custom overrides, and those of hooks in particular, may break some important assumptions and introduce vulnerabilities in otherwise secure code. While we try to ensure the contracts remain secure in the face of a wide range of potential customizations, this is done in a best-effort manner. Similarly, while we try to document all important assumptions, this should not be relied upon. Custom overrides should be carefully reviewed and checked against the source code of the contract they are customizing so as to fully understand their impact and guarantee their security.

Loading…
Cancel
Save