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 ad290e7181 Use msg.sender in docs 5 years ago
.circleci Migrate from truffle to test-environment (#2007) 5 years ago
.dependabot
.github Update support request (#2148) 5 years ago
audit
contracts Use msg.sender in docs 5 years ago
docs Remove outdated notes to v2.x docs 5 years ago
migrations
scripts Remove ethpm.json and update releasing docs (#2205) 5 years ago
test ERC721 deploy ready fixes (#2192) 5 years ago
.codecov.yml
.editorconfig Configure line length in .editorconfig 5 years ago
.eslintrc Migrate from truffle to test-environment (#2007) 5 years ago
.gitattributes
.gitignore Fix documentation previews in pull requests (#2015) 5 years ago
.solcover.js Create2 feature pending tasks (#2013) 5 years ago
.solhint.json Adhere to naming convention (#2150) 5 years ago
CHANGELOG.md 3.0.0 5 years ago
CODE_OF_CONDUCT.md
CODE_STYLE.md
CONTRIBUTING.md
DOCUMENTATION.md
GUIDELINES.md
LICENSE
README.md Add note about gas costs (#2079) 5 years ago
RELEASING.md Remove ethpm.json and update releasing docs (#2205) 5 years ago
ethpm.json Remove ethpm.json and update releasing docs (#2205) 5 years ago
logo.png
netlify.toml Fix documentation previews in pull requests (#2015) 5 years ago
package-lock.json 3.0.0 5 years ago
package.json 3.0.0 5 years ago
test-environment.config.js Migrate from truffle to test-environment (#2007) 5 years ago

README.md

OpenZeppelin

NPM Package Build Status Coverage Status

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

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.5.0;

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

contract MyNFT is ERC721Full, ERC721Mintable {
    constructor() ERC721Full("MyNFT", "MNFT") public {
    }
}

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

Contribute

OpenZeppelin 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 is released under the MIT License.