暫無描述

Francisco 6bf68a41d1 Remove "available since" comments (#4424) 2 年之前
.changeset 63bfab1a0c Enable ERC-1271 signature checks in Governor `castVoteBySig` (#4418) 2 年之前
.github 023894deef Add `ERC2771Forwarder` as an enhanced successor to `MinimalForwarder` (#4346) 2 年之前
audits e5dbc7435e Add final PDF report for v4.9 audit (#4235) 2 年之前
certora 7bb5592ad5 Bump minimum pragma version to `0.8.19` (#4288) 2 年之前
contracts 6bf68a41d1 Remove "available since" comments (#4424) 2 年之前
docs 874c2d3c02 Use explicit imports (#4399) 2 年之前
hardhat dfef6a68ee Fix error when running hardhat test with parameters (#4265) 2 年之前
lib 96ff934ad0 Update `forge-std` submodule to `v1.2.0` (#3885) 2 年之前
scripts 6bf68a41d1 Remove "available since" comments (#4424) 2 年之前
test 63bfab1a0c Enable ERC-1271 signature checks in Governor `castVoteBySig` (#4418) 2 年之前
.codecov.yml 93bc3b657b Remove Codecov Patch status outside PRs 3 年之前
.editorconfig d3ff81b37f Remove line length configuration for markdown files 3 年之前
.eslintrc 2336bd3e8e Simplify ESLint config (#3903) 2 年之前
.gitignore 1a60b061d5 Add Pausable FV (#4117) 2 年之前
.gitmodules 58a62916de Bump and pin Forge Std submodule (#4102) 2 年之前
.mocharc.js 8bcf0ad7ab Use Hardhat recommended Mocha configuration (#2805) 4 年之前
.prettierrc a28aafdc85 Use Prettier for JS files (#3913) 2 年之前
.solcover.js a28aafdc85 Use Prettier for JS files (#3913) 2 年之前
.solhint.json 874c2d3c02 Use explicit imports (#4399) 2 年之前
CHANGELOG.md cb4bf950df Add unreleased disclaimer in readme 2 年之前
CODE_OF_CONDUCT.md 88a64a802e Update guidelines and project documentation (#3966) 2 年之前
CONTRIBUTING.md 6d18435098 Add `RELEASING.md` docs (#3981) 2 年之前
GUIDELINES.md 5cc1ea0a39 Add `GUIDELINES.md` for marking `abstract` contracts (#4010) 2 年之前
LICENSE 88a64a802e Update guidelines and project documentation (#3966) 2 年之前
README.md 874c2d3c02 Use explicit imports (#4399) 2 年之前
RELEASING.md 6d18435098 Add `RELEASING.md` docs (#3981) 2 年之前
SECURITY.md 88a64a802e Update guidelines and project documentation (#3966) 2 年之前
foundry.toml ead3bcaccb Fix spurious CI check failures (#4160) 2 年之前
hardhat.config.js 6e21422737 Add Governor signature nonces (#4378) 2 年之前
logo.svg d1f336d8fd use svg logo for better scaling 5 年之前
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 年之前
package-lock.json 3fe28e19af Update lockfile (#4409) 2 年之前
package.json 874c2d3c02 Use explicit imports (#4399) 2 年之前
remappings.txt dd1265cb1d Improve `ERC4626` test coverage (#4134) 2 年之前
renovate.json 740ce2d440 Update renovate.json 2 年之前
requirements.txt e739144cb0 Update dependency certora-cli to v3.6.4 (#4110) 2 年之前
slither.config.json 908f78d07b Enable more Slither detectors (#4219) 2 年之前

README.md

Warning Version 5.0 is under active development. The code in this branch is not recommended for use.

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

Hardhat, Truffle (npm)

$ 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.

Foundry (git)

Warning When installing via git, it is a common error to use the master branch. This is a development branch that should be avoided in favor of tagged releases. The release process involves security measures that the master branch does not guarantee.

Warning Foundry installs the latest version initially, but subsequent forge update commands will use the master branch.

$ forge install OpenZeppelin/openzeppelin-contracts

Usage

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

pragma solidity ^0.8.19;

import {ERC721} from "@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 OpenZeppelin Contracts Security Center contains more details about the secure development process.

The security policy is detailed in SECURITY.md as well, 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 technology 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").