mirror of openzeppelin-contracts
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Francisco Giordano 694f169832
Remove changelog entry for test changes
4 years ago
.github Update codecov/codecov-action action to v2 (#2779) 4 years ago
audit Use "OpenZeppelin Contracts" where appropriate (#2778) 4 years ago
contracts Improve Governor (#2794) 4 years ago
docs Add Governor guide (#2811) 4 years ago
hardhat
migrations
scripts Add Governor contracts (#2672) 4 years ago
test Fix inconsistencies in contract/test hierachy (#2814) 4 years ago
.codecov.yml
.editorconfig
.eslintrc
.gitattributes
.gitignore
.mocharc.js Use Hardhat recommended Mocha configuration (#2805) 4 years ago
.prettierrc Add Prettier for linting and fix Solhint config (#2697) 4 years ago
.solcover.js
.solhint.json remove duplicated 'private-vars-leading-underscore' solhint rule (#2800) 4 years ago
CHANGELOG.md Remove changelog entry for test changes 4 years ago
CODE_OF_CONDUCT.md
CONTRIBUTING.md Use "OpenZeppelin Contracts" where appropriate (#2778) 4 years ago
DOCUMENTATION.md
GUIDELINES.md Use "OpenZeppelin Contracts" where appropriate (#2778) 4 years ago
LICENSE
README.md Update security policy regarding past major releases 4 years ago
RELEASING.md Use "OpenZeppelin Contracts" where appropriate (#2778) 4 years ago
SECURITY.md Update security policy regarding past major releases 4 years ago
hardhat.config.js Read optional compiler version from args/envvars (#2810) 4 years ago
logo.svg
netlify.toml
package-lock.json Update lockfile (#2774) 4 years ago
package.json Add Governor contracts (#2672) 4 years ago
renovate.json

README.md

OpenZeppelin

Docs NPM Package Coverage Status

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

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