No Description

Hadrien Croubois 91e8d0ba3c Add `string` and `bytes` support to the `StorageSlots` library (#4008) 2 years ago
.changeset 91e8d0ba3c Add `string` and `bytes` support to the `StorageSlots` library (#4008) 2 years ago
.github a70ee4e3bb Check storage layout consistency in PRs (#3967) 2 years ago
audits 88a64a802e Update guidelines and project documentation (#3966) 2 years ago
certora 0c89a8b771 Automate release process via Changesets (#3915) 2 years ago
contracts 91e8d0ba3c Add `string` and `bytes` support to the `StorageSlots` library (#4008) 2 years ago
docs 591c12d22d Remove outdated note about virtual view functions (#4014) 2 years ago
hardhat a28aafdc85 Use Prettier for JS files (#3913) 2 years ago
lib 96ff934ad0 Update `forge-std` submodule to `v1.2.0` (#3885) 2 years ago
scripts 91e8d0ba3c Add `string` and `bytes` support to the `StorageSlots` library (#4008) 2 years ago
test 91e8d0ba3c Add `string` and `bytes` support to the `StorageSlots` library (#4008) 2 years ago
.codecov.yml 93bc3b657b Remove Codecov Patch status outside PRs 3 years ago
.editorconfig d3ff81b37f Remove line length configuration for markdown files 3 years ago
.eslintrc 2336bd3e8e Simplify ESLint config (#3903) 2 years ago
.gitattributes ad5edd329f feat: add solidity syntax highlighting directive, fixes #671 7 years ago
.gitignore c1d9da4052 Use hardhat-exposed to reduce the need for mocks (#3666) 2 years ago
.gitmodules c7315e8779 Add ERC4626 standard property tests (#3792) 2 years ago
.mocharc.js 8bcf0ad7ab Use Hardhat recommended Mocha configuration (#2805) 4 years ago
.prettierrc a28aafdc85 Use Prettier for JS files (#3913) 2 years ago
.solcover.js a28aafdc85 Use Prettier for JS files (#3913) 2 years ago
.solhint.json 2d1e82c901 remove duplicated 'private-vars-leading-underscore' solhint rule (#2800) 4 years ago
CHANGELOG.md 0c89a8b771 Automate release process via Changesets (#3915) 2 years ago
CODE_OF_CONDUCT.md 88a64a802e Update guidelines and project documentation (#3966) 2 years ago
CONTRIBUTING.md 88a64a802e Update guidelines and project documentation (#3966) 2 years ago
GUIDELINES.md d6fb3d645f Add guidelines for pull requests (#4002) 2 years ago
LICENSE 88a64a802e Update guidelines and project documentation (#3966) 2 years ago
README.md 88a64a802e Update guidelines and project documentation (#3966) 2 years ago
RELEASING.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 years ago
SECURITY.md 88a64a802e Update guidelines and project documentation (#3966) 2 years ago
foundry.toml c7315e8779 Add ERC4626 standard property tests (#3792) 2 years ago
hardhat.config.js a28aafdc85 Use Prettier for JS files (#3913) 2 years ago
logo.svg d1f336d8fd use svg logo for better scaling 5 years ago
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 years ago
package-lock.json a70ee4e3bb Check storage layout consistency in PRs (#3967) 2 years ago
package.json a70ee4e3bb Check storage layout consistency in PRs (#3967) 2 years ago
renovate.json 4fc19ddb8d Add label to Renovate PRs 2 years ago
slither.config.json a5af0adce4 Ignore reentrancy in`executeBatch` and update Slither config (#3955) 2 years ago

README.md

OpenZeppelin

NPM Package Coverage Status GitPOAPs Docs Forum

A library for secure smart contract development. Build on a solid foundation of community-vetted code.

:mage: Not sure how to get started? Check out Contracts Wizard — an interactive smart contract generator.

:building_construction: Want to scale your decentralized application? Check out OpenZeppelin Defender — a secure platform for automating and monitoring your operations.

Overview

Installation

$ npm install @openzeppelin/contracts

OpenZeppelin Contracts features a stable API, which means that your contracts won't break unexpectedly when upgrading to a newer minor version.

An alternative to npm is to use the GitHub repository (openzeppelin/openzeppelin-contracts) to retrieve the contracts. When doing this, make sure to specify the tag for a release such as v4.5.0, instead of using the master branch.

Usage

Once installed, you can use the contracts in the library by importing them:

pragma solidity ^0.8.0;

import "@openzeppelin/contracts/token/ERC721/ERC721.sol";

contract MyCollectible is ERC721 {
    constructor() ERC721("MyCollectible", "MCO") {
    }
}

If you're new to smart contract development, head to Developing Smart Contracts to learn about creating a new project and compiling your contracts.

To keep your system secure, you should always use the installed code as-is, and neither copy-paste it from online sources nor modify it yourself. The library is designed so that only the contracts and functions you use are deployed, so you don't need to worry about it needlessly increasing gas costs.

Learn More

The guides in the documentation site will teach about different concepts, and how to use the related contracts that OpenZeppelin Contracts provides:

  • Access Control: decide who can perform each of the actions on your system.
  • Tokens: create tradeable assets or collectives, and distribute them via Crowdsales.
  • Utilities: generic useful tools including non-overflowing math, signature verification, and trustless paying systems.

The full API is also thoroughly documented, and serves as a great reference when developing your smart contract application. You can also ask for help or follow Contracts's development in the community forum.

Finally, you may want to take a look at the guides on our blog, which cover several common use cases and good practices. The following articles provide great background reading, though please note that some of the referenced tools have changed, as the tooling in the ecosystem continues to rapidly evolve.

Security

This project is maintained by OpenZeppelin with the goal of providing a secure and reliable library of smart contract components for the ecosystem. We address security through risk management in various areas such as engineering and open source best practices, scoping and API design, multi-layered review processes, and incident response preparedness.

The security policy is detailed in SECURITY.md, and specifies how you can report security vulnerabilities, which versions will receive security patches, and how to stay informed about them. We run a bug bounty program on Immunefi to reward the responsible disclosure of vulnerabilities.

The engineering guidelines we follow to promote project quality can be found in GUIDELINES.md.

Past audits can be found in audits/.

Smart contracts are a nascent techology and carry a high level of technical risk and uncertainty. Although OpenZeppelin is well known for its security audits, using OpenZeppelin Contracts is not a substitute for a security audit.

OpenZeppelin Contracts is made available under the MIT License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including OpenZeppelin. As set out further in the Terms, you acknowledge that you are solely responsible for any use of OpenZeppelin Contracts and you assume all risks associated with any such use.

Contribute

OpenZeppelin Contracts exists thanks to its contributors. There are many ways you can participate and help build high quality software. Check out the contribution guide!

License

OpenZeppelin Contracts is released under the MIT License.

Legal

Your use of this Project is governed by the terms found at www.openzeppelin.com/tos (the "Terms").