Ingen beskrivning

Hadrien Croubois 30c3c6c16e Clean up after merging master into next-v5.0 (#3956) 2 år sedan
.github 147dc89054 Merge branch 'master' into next-v5.0 2 år sedan
audit faf5820f03 Fix many spelling errors (#3274) 3 år sedan
certora 24fc709533 Set up codespell (#3643) 3 år sedan
contracts 30c3c6c16e Clean up after merging master into next-v5.0 (#3956) 2 år sedan
docs 147dc89054 Merge branch 'master' into next-v5.0 2 år sedan
hardhat a28aafdc85 Use Prettier for JS files (#3913) 2 år sedan
lib 96ff934ad0 Update `forge-std` submodule to `v1.2.0` (#3885) 2 år sedan
scripts 147dc89054 Merge branch 'master' into next-v5.0 2 år sedan
test 30c3c6c16e Clean up after merging master into next-v5.0 (#3956) 2 år sedan
.codecov.yml 93bc3b657b Remove Codecov Patch status outside PRs 3 år sedan
.editorconfig d3ff81b37f Remove line length configuration for markdown files 3 år sedan
.eslintrc 2336bd3e8e Simplify ESLint config (#3903) 2 år sedan
.gitattributes ad5edd329f feat: add solidity syntax highlighting directive, fixes #671 7 år sedan
.gitignore c1d9da4052 Use hardhat-exposed to reduce the need for mocks (#3666) 2 år sedan
.gitmodules c7315e8779 Add ERC4626 standard property tests (#3792) 2 år sedan
.mocharc.js 8bcf0ad7ab Use Hardhat recommended Mocha configuration (#2805) 4 år sedan
.prettierrc a28aafdc85 Use Prettier for JS files (#3913) 2 år sedan
.solcover.js a28aafdc85 Use Prettier for JS files (#3913) 2 år sedan
.solhint.json 2d1e82c901 remove duplicated 'private-vars-leading-underscore' solhint rule (#2800) 4 år sedan
CHANGELOG.md 147dc89054 Merge branch 'master' into next-v5.0 2 år sedan
CODE_OF_CONDUCT.md 4575a240f7 Create CODE_OF_CONDUCT.md (#1061) 7 år sedan
CONTRIBUTING.md 15d5174139 Fix minor typo in CONTRIBUTING.md. (#3284) 3 år sedan
DOCUMENTATION.md aaa5ef81cf Fix typos (#2343) 5 år sedan
GUIDELINES.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 år sedan
LICENSE 21c5d623d6 Update Copyright notice and include contributors 3 år sedan
README.md a290e13099 Add warning in next-v5.0 branch readme (#3941) 2 år sedan
RELEASING.md 0500c9e53e Use "OpenZeppelin Contracts" where appropriate (#2778) 4 år sedan
SECURITY.md c739d1976b Update security email domain and Immunefi text 3 år sedan
foundry.toml c7315e8779 Add ERC4626 standard property tests (#3792) 2 år sedan
hardhat.config.js a28aafdc85 Use Prettier for JS files (#3913) 2 år sedan
logo.svg d1f336d8fd use svg logo for better scaling 5 år sedan
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 år sedan
package-lock.json 147dc89054 Merge branch 'master' into next-v5.0 2 år sedan
package.json 147dc89054 Merge branch 'master' into next-v5.0 2 år sedan
renovate.json 4fc19ddb8d Add label to Renovate PRs 2 år sedan
slither.config.json 30c3c6c16e Clean up after merging master into next-v5.0 (#3956) 2 år sedan

README.md

Warning Version 5.0 is under active development. The code in this branch is not recommended for use.

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.