暫無描述

Francisco Giordano 7713757609 Add function documentation for SignatureChecker. 3 年之前
.github 2abda12af1 Add workflow to generate and update docs branches 3 年之前
audit 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 年之前
contracts 7713757609 Add function documentation for SignatureChecker. 3 年之前
docs 0413d58860 add bug bounty info 3 年之前
hardhat a0323d446c Transition from buidler to hardhat 4 年之前
migrations 0e5799c93b Clean up npm package (#904) 7 年之前
scripts f64890d595 Lint 3 年之前
test eff4ad7c1d Fix encoding of signature+calldata in GovernorCompatibilityBravo (#3100) 3 年之前
.codecov.yml 73c7af102b Configure Codecov parameters 4 年之前
.editorconfig 6bc2ae3731 Add documentation for proxies (#2344) 5 年之前
.eslintrc f06738828b Migrate to Hardhat (#2397) 5 年之前
.gitattributes ad5edd329f feat: add solidity syntax highlighting directive, fixes #671 7 年之前
.gitignore 232c355b3a Fix mentions of buidler (#2548) 4 年之前
.mocharc.js 8bcf0ad7ab Use Hardhat recommended Mocha configuration (#2805) 4 年之前
.prettierrc b0cf6fbb7a Add Prettier for linting and fix Solhint config (#2697) 4 年之前
.solcover.js 85f50d3e06 Update lockfile (#2412) 4 年之前
.solhint.json 2d1e82c901 remove duplicated 'private-vars-leading-underscore' solhint rule (#2800) 4 年之前
CHANGELOG.md eff4ad7c1d Fix encoding of signature+calldata in GovernorCompatibilityBravo (#3100) 3 年之前
CODE_OF_CONDUCT.md 4575a240f7 Create CODE_OF_CONDUCT.md (#1061) 7 年之前
CONTRIBUTING.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 年之前
DOCUMENTATION.md aaa5ef81cf Fix typos (#2343) 5 年之前
GUIDELINES.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 年之前
LICENSE 2a0f2a8ba8 Update LICENSE (#2247) 5 年之前
README.md 0413d58860 add bug bounty info 3 年之前
RELEASING.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 年之前
SECURITY.md bbd68b721d Update security policy regarding past major releases 4 年之前
hardhat.config.js fb36326a58 Support london with coverage using initialBaseFee = 0 (#2838) 4 年之前
logo.svg d1f336d8fd use svg logo for better scaling 5 年之前
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 年之前
package-lock.json b53c43242f 4.4.2 3 年之前
package.json b53c43242f 4.4.2 3 年之前
renovate.json 0c27ecc536 configure renovate using openzeppelin shareable config 5 年之前

README.md

OpenZeppelin

Docs NPM Package Coverage Status

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.

Overview

Installation

$ npm install @openzeppelin/contracts

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

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 docs 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.
  • Gas Station Network: let your users interact with your contracts without having to pay for gas themselves.
  • 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, some of the referenced tools have changed as the tooling in the ecosystem continues to rapidly evolve.

Security

This project is maintained by OpenZeppelin, and developed following our high standards for code quality and security. OpenZeppelin Contracts is meant to provide tested and community-audited code, but please use common sense when doing anything that deals with real money! We take no responsibility for your implementation decisions and any security problems you might experience.

The core development principles and strategies that OpenZeppelin Contracts is based on include: security in depth, simple and modular code, clarity-driven naming conventions, comprehensive unit testing, pre-and-post-condition sanity checks, code consistency, and regular audits.

The latest audit was done on October 2018 on version 2.0.0.

Please report any security issues you find via our bug bounty program on Immunefi or directly to security@openzeppelin.org.

Critical bug fixes will be backported to past major releases.

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.