Sin descripción

Francisco Giordano 40a15c0406 Merge branch 'solc-0.7' into release-v3.3-solc-0.7 hace 4 años
.github cb19930b83 Run tests on release branches hace 4 años
audit 7f54542172 Add latest audit to repository (#1664) hace 6 años
buidler 1e78adc28c Refactor buidler config hace 4 años
contracts 40a15c0406 Merge branch 'solc-0.7' into release-v3.3-solc-0.7 hace 4 años
docs 40a15c0406 Merge branch 'solc-0.7' into release-v3.3-solc-0.7 hace 4 años
migrations 0e5799c93b Clean up npm package (#904) hace 7 años
scripts ba843f0ad9 Fix release script hace 4 años
test 7f8fc584de Remove Address.functionDelegateCall hace 4 años
.codecov.yml 2a29f697bf Disable Travis in favor of Circle (#1866) hace 6 años
.editorconfig 6bc2ae3731 Add documentation for proxies (#2344) hace 5 años
.eslintrc f06738828b Migrate to Hardhat (#2397) hace 5 años
.gitattributes ad5edd329f feat: add solidity syntax highlighting directive, fixes #671 hace 7 años
.gitignore f06738828b Migrate to Hardhat (#2397) hace 5 años
.mocharc.js 722879b32d increase mocha timeout hace 5 años
.solcover.js f06738828b Migrate to Hardhat (#2397) hace 5 años
.solhint.json 90ed1af972 Support compiling with solc 0.7 (#2408) hace 4 años
CHANGELOG.md 40a15c0406 Merge branch 'solc-0.7' into release-v3.3-solc-0.7 hace 4 años
CODE_OF_CONDUCT.md 4575a240f7 Create CODE_OF_CONDUCT.md (#1061) hace 7 años
CONTRIBUTING.md da9161fc91 Migrate to GitHub Actions hace 4 años
DOCUMENTATION.md aaa5ef81cf Fix typos (#2343) hace 5 años
GUIDELINES.md e5da0986bb Fix code style parameters in Event (#2324) hace 5 años
LICENSE 2a0f2a8ba8 Update LICENSE (#2247) hace 5 años
README.md 4972bf4f23 Merge branch 'master' into solc-0.7 hace 4 años
RELEASING.md 528c23d679 Remove ethpm.json and update releasing docs (#2205) hace 5 años
buidler.config.js 3f2a2b5f62 Configure compilation with solc 0.7.4 hace 4 años
logo.svg d1f336d8fd use svg logo for better scaling hace 5 años
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) hace 5 años
package-lock.json 40a15c0406 Merge branch 'solc-0.7' into release-v3.3-solc-0.7 hace 4 años
package.json 40a15c0406 Merge branch 'solc-0.7' into release-v3.3-solc-0.7 hace 4 años
renovate.json 0c27ecc536 configure renovate using openzeppelin shareable config hace 5 años

README.md

OpenZeppelin

Docs NPM Package 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.7.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 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.