Brak opisu

Nicolás Venturo 97894a140d Adhere to naming convention (#2150) 5 lat temu
.circleci 5f92adc2e7 Migrate from truffle to test-environment (#2007) 5 lat temu
.dependabot 111cde942f Update dependencies + configure Dependabot (#1931) 6 lat temu
.github 7554ea84a3 Update support request (#2148) 5 lat temu
audit 7f54542172 Add latest audit to repository (#1664) 6 lat temu
contracts 97894a140d Adhere to naming convention (#2150) 5 lat temu
docs 3ae631c81d Fix display of array arguments in documentation (#2141) 5 lat temu
migrations 0e5799c93b Clean up npm package (#904) 7 lat temu
scripts e4d2830f1d Update release script for major releases 5 lat temu
test 4476a2d531 Unsigned conversion #2111 (#2123) 5 lat temu
.codecov.yml 2a29f697bf Disable Travis in favor of Circle (#1866) 6 lat temu
.editorconfig cab26fd046 Update .editorconfig 6 lat temu
.eslintrc 5f92adc2e7 Migrate from truffle to test-environment (#2007) 5 lat temu
.gitattributes ad5edd329f feat: add solidity syntax highlighting directive, fixes #671 7 lat temu
.gitignore b56e00eb61 Fix documentation previews in pull requests (#2015) 5 lat temu
.solcover.js 8c40a5b275 Create2 feature pending tasks (#2013) 5 lat temu
.solhint.json 97894a140d Adhere to naming convention (#2150) 5 lat temu
CHANGELOG.md 97894a140d Adhere to naming convention (#2150) 5 lat temu
CODE_OF_CONDUCT.md 4575a240f7 Create CODE_OF_CONDUCT.md (#1061) 7 lat temu
CODE_STYLE.md e869b37d0b Update CODE_STYLE.md (#1842) 6 lat temu
CONTRIBUTING.md f095b62856 Fixing instructions by correcting instruction to (#1877) 6 lat temu
DOCUMENTATION.md 18d7e24a2c rename docsite script to docs and update docs setup description 6 lat temu
GUIDELINES.md 984468b583 Create GUIDELINES.md from wiki content. (#1776) 6 lat temu
LICENSE d45f0c89db Update copyright notice 6 lat temu
README.md 4a531fe588 Add note about gas costs (#2079) 5 lat temu
RELEASING.md b8c8308d77 Add @openzeppelin/contracts as alternative package name (#1840) 6 lat temu
ethpm.json 58a3368215 2.5.0 5 lat temu
logo.png eae306f259 Rebrand readme (#1832) 6 lat temu
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 lat temu
package-lock.json 97894a140d Adhere to naming convention (#2150) 5 lat temu
package.json 97894a140d Adhere to naming convention (#2150) 5 lat temu
test-environment.config.js 5f92adc2e7 Migrate from truffle to test-environment (#2007) 5 lat temu

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.