Açıklama Yok

Ernesto García 6d18435098 Add `RELEASING.md` docs (#3981) 2 yıl önce
.changeset 790cc5b65a Add timestamp based governor with EIP-6372 and EIP-5805 (#3934) 2 yıl önce
.github 6d18435098 Add `RELEASING.md` docs (#3981) 2 yıl önce
audits 88a64a802e Update guidelines and project documentation (#3966) 2 yıl önce
certora 0c89a8b771 Automate release process via Changesets (#3915) 2 yıl önce
contracts 2c711d0b05 Restrict ERC721Wrapper wrap by direct transfer (#4043) 2 yıl önce
docs 94cd8ef12e Add ERC721 Wrapper (#3863) 2 yıl önce
hardhat a28aafdc85 Use Prettier for JS files (#3913) 2 yıl önce
lib 96ff934ad0 Update `forge-std` submodule to `v1.2.0` (#3885) 2 yıl önce
scripts 790cc5b65a Add timestamp based governor with EIP-6372 and EIP-5805 (#3934) 2 yıl önce
test 2c711d0b05 Restrict ERC721Wrapper wrap by direct transfer (#4043) 2 yıl önce
.codecov.yml 93bc3b657b Remove Codecov Patch status outside PRs 3 yıl önce
.editorconfig d3ff81b37f Remove line length configuration for markdown files 3 yıl önce
.eslintrc 2336bd3e8e Simplify ESLint config (#3903) 2 yıl önce
.gitattributes ad5edd329f feat: add solidity syntax highlighting directive, fixes #671 7 yıl önce
.gitignore c1d9da4052 Use hardhat-exposed to reduce the need for mocks (#3666) 2 yıl önce
.gitmodules c7315e8779 Add ERC4626 standard property tests (#3792) 2 yıl önce
.mocharc.js 8bcf0ad7ab Use Hardhat recommended Mocha configuration (#2805) 4 yıl önce
.prettierrc a28aafdc85 Use Prettier for JS files (#3913) 2 yıl önce
.solcover.js a28aafdc85 Use Prettier for JS files (#3913) 2 yıl önce
.solhint.json 2d1e82c901 remove duplicated 'private-vars-leading-underscore' solhint rule (#2800) 4 yıl önce
CHANGELOG.md d625cb45ea Include EIP-5267 discovery in EIP-712 (#3969) 2 yıl önce
CODE_OF_CONDUCT.md 88a64a802e Update guidelines and project documentation (#3966) 2 yıl önce
CONTRIBUTING.md 6d18435098 Add `RELEASING.md` docs (#3981) 2 yıl önce
GUIDELINES.md d6fb3d645f Add guidelines for pull requests (#4002) 2 yıl önce
LICENSE 88a64a802e Update guidelines and project documentation (#3966) 2 yıl önce
README.md 88a64a802e Update guidelines and project documentation (#3966) 2 yıl önce
RELEASING.md 6d18435098 Add `RELEASING.md` docs (#3981) 2 yıl önce
SECURITY.md 88a64a802e Update guidelines and project documentation (#3966) 2 yıl önce
foundry.toml c7315e8779 Add ERC4626 standard property tests (#3792) 2 yıl önce
hardhat.config.js 3b591a48ac Add storageLayout to outputSelection 2 yıl önce
logo.svg d1f336d8fd use svg logo for better scaling 5 yıl önce
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 yıl önce
package-lock.json dfcc1d16c5 Bump http-cache-semantics from 4.1.0 to 4.1.1 (#4024) 2 yıl önce
package.json 260e082ed1 Add a library for handling short strings in a gas efficient way (#4023) 2 yıl önce
renovate.json 740ce2d440 Update renovate.json 2 yıl önce
slither.config.json a5af0adce4 Ignore reentrancy in`executeBatch` and update Slither config (#3955) 2 yıl önce

README.md

OpenZeppelin

NPM Package Coverage Status GitPOAPs Docs Forum

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.
  • 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 with the goal of providing a secure and reliable library of smart contract components for the ecosystem. We address security through risk management in various areas such as engineering and open source best practices, scoping and API design, multi-layered review processes, and incident response preparedness.

The security policy is detailed in SECURITY.md, and specifies how you can report security vulnerabilities, which versions will receive security patches, and how to stay informed about them. We run a bug bounty program on Immunefi to reward the responsible disclosure of vulnerabilities.

The engineering guidelines we follow to promote project quality can be found in GUIDELINES.md.

Past audits can be found in audits/.

Smart contracts are a nascent techology and carry a high level of technical risk and uncertainty. Although OpenZeppelin is well known for its security audits, using OpenZeppelin Contracts is not a substitute for a security audit.

OpenZeppelin Contracts is made available under the MIT License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including OpenZeppelin. As set out further in the Terms, you acknowledge that you are solely responsible for any use of OpenZeppelin Contracts and you assume all risks associated with any such use.

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.

Legal

Your use of this Project is governed by the terms found at www.openzeppelin.com/tos (the "Terms").