Nenhuma descrição

Francisco d89e51ac42 Use actionlint on GitHub Actions workflows (#3953) 2 anos atrás
.github d89e51ac42 Use actionlint on GitHub Actions workflows (#3953) 2 anos atrás
audit faf5820f03 Fix many spelling errors (#3274) 3 anos atrás
certora 24fc709533 Set up codespell (#3643) 3 anos atrás
contracts 6b17b33430 Use a staticcall to fetch ERC20.decimals in ERC4626 (#3943) 2 anos atrás
docs 717fbc45cb Add docs on non-stability of internal function use (#3952) 2 anos atrás
hardhat a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
lib 96ff934ad0 Update `forge-std` submodule to `v1.2.0` (#3885) 2 anos atrás
scripts a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
test a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
.codecov.yml 93bc3b657b Remove Codecov Patch status outside PRs 3 anos atrás
.editorconfig d3ff81b37f Remove line length configuration for markdown files 3 anos atrás
.eslintrc 2336bd3e8e Simplify ESLint config (#3903) 2 anos atrás
.gitattributes ad5edd329f feat: add solidity syntax highlighting directive, fixes #671 7 anos atrás
.gitignore c1d9da4052 Use hardhat-exposed to reduce the need for mocks (#3666) 2 anos atrás
.gitmodules c7315e8779 Add ERC4626 standard property tests (#3792) 2 anos atrás
.mocharc.js 8bcf0ad7ab Use Hardhat recommended Mocha configuration (#2805) 4 anos atrás
.prettierrc a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
.solcover.js a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
.solhint.json 2d1e82c901 remove duplicated 'private-vars-leading-underscore' solhint rule (#2800) 4 anos atrás
CHANGELOG.md 6b17b33430 Use a staticcall to fetch ERC20.decimals in ERC4626 (#3943) 2 anos atrás
CODE_OF_CONDUCT.md 4575a240f7 Create CODE_OF_CONDUCT.md (#1061) 7 anos atrás
CONTRIBUTING.md 15d5174139 Fix minor typo in CONTRIBUTING.md. (#3284) 3 anos atrás
DOCUMENTATION.md aaa5ef81cf Fix typos (#2343) 5 anos atrás
GUIDELINES.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 anos atrás
LICENSE 21c5d623d6 Update Copyright notice and include contributors 3 anos atrás
README.md 48dd186870 Improve readme style (#3577) 3 anos atrás
RELEASING.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 anos atrás
SECURITY.md c739d1976b Update security email domain and Immunefi text 3 anos atrás
foundry.toml c7315e8779 Add ERC4626 standard property tests (#3792) 2 anos atrás
hardhat.config.js a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
logo.svg d1f336d8fd use svg logo for better scaling 5 anos atrás
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 anos atrás
package-lock.json a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
package.json a28aafdc85 Use Prettier for JS files (#3913) 2 anos atrás
renovate.json 4fc19ddb8d Add label to Renovate PRs 2 anos atrás
slither.config.json f85eb5b725 Use slither action (#3278) 3 anos atrás

README.md

OpenZeppelin

Docs NPM Package Coverage Status gitpoap badge

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.

:building_construction: Want to scale your decentralized application? Check out OpenZeppelin Defender — a secure platform for automating and monitoring your operations.

Overview

Installation

$ npm install @openzeppelin/contracts

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

An alternative to npm is to use the GitHub repository (openzeppelin/openzeppelin-contracts) to retrieve the contracts. When doing this, make sure to specify the tag for a release such as v4.5.0, instead of using the master branch.

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 documentation 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 that 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.

We have a bug bounty program on Immunefi. Please report any security issues you find through the Immunefi dashboard, or reach out to security@openzeppelin.com.

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.