Tidak Ada Deskripsi

Francisco 91df66c4a9 Implement suggestions from audit of 4.9 (#4176) 2 tahun lalu
.changeset 8d633cb7d1 Merge pull request from GHSA-93hq-5wgc-jc82 2 tahun lalu
.github 473d0b6884 Add Codecov token 2 tahun lalu
audits 88a64a802e Update guidelines and project documentation (#3966) 2 tahun lalu
certora 86f6eb2c9c Add FV specification for ERC721 (#4104) 2 tahun lalu
contracts 91df66c4a9 Implement suggestions from audit of 4.9 (#4176) 2 tahun lalu
docs 1c8df659b9 Clarify Governor Bravo compatibility scope (#4090) 2 tahun lalu
hardhat a28aafdc85 Use Prettier for JS files (#3913) 2 tahun lalu
lib 58a62916de Bump and pin Forge Std submodule (#4102) 2 tahun lalu
scripts f2346b6749 Add fuzz tests for the Checkpoints library (#4146) 2 tahun lalu
test 91df66c4a9 Implement suggestions from audit of 4.9 (#4176) 2 tahun lalu
.codecov.yml 93bc3b657b Remove Codecov Patch status outside PRs 3 tahun lalu
.editorconfig d3ff81b37f Remove line length configuration for markdown files 3 tahun lalu
.eslintrc 2336bd3e8e Simplify ESLint config (#3903) 2 tahun lalu
.gitignore 1a60b061d5 Add Pausable FV (#4117) 2 tahun lalu
.gitmodules 58a62916de Bump and pin Forge Std submodule (#4102) 2 tahun lalu
.mocharc.js 8bcf0ad7ab Use Hardhat recommended Mocha configuration (#2805) 4 tahun lalu
.prettierrc a28aafdc85 Use Prettier for JS files (#3913) 2 tahun lalu
.solcover.js a28aafdc85 Use Prettier for JS files (#3913) 2 tahun lalu
.solhint.json 2d1e82c901 remove duplicated 'private-vars-leading-underscore' solhint rule (#2800) 4 tahun lalu
CHANGELOG.md eedca5d873 Merge release-v4.8 branch 2 tahun lalu
CODE_OF_CONDUCT.md 88a64a802e Update guidelines and project documentation (#3966) 2 tahun lalu
CONTRIBUTING.md 6d18435098 Add `RELEASING.md` docs (#3981) 2 tahun lalu
GUIDELINES.md d6fb3d645f Add guidelines for pull requests (#4002) 2 tahun lalu
LICENSE 88a64a802e Update guidelines and project documentation (#3966) 2 tahun lalu
README.md 3f610ebc25 Fix typo in README (#4129) 2 tahun lalu
RELEASING.md 6d18435098 Add `RELEASING.md` docs (#3981) 2 tahun lalu
SECURITY.md 88a64a802e Update guidelines and project documentation (#3966) 2 tahun lalu
foundry.toml ead3bcaccb Fix spurious CI check failures (#4160) 2 tahun lalu
hardhat.config.js 3b591a48ac Add storageLayout to outputSelection 2 tahun lalu
logo.svg d1f336d8fd use svg logo for better scaling 5 tahun lalu
netlify.toml b56e00eb61 Fix documentation previews in pull requests (#2015) 5 tahun lalu
package-lock.json ea2d5ad2e7 Update lockfile (#4080) 2 tahun lalu
package.json 4fb6833e32 Formal verification using Certora (#4084) 2 tahun lalu
remappings.txt dd1265cb1d Improve `ERC4626` test coverage (#4134) 2 tahun lalu
renovate.json 740ce2d440 Update renovate.json 2 tahun lalu
requirements.txt e739144cb0 Update dependency certora-cli to v3.6.4 (#4110) 2 tahun lalu
slither.config.json a5af0adce4 Ignore reentrancy in`executeBatch` and update Slither config (#3955) 2 tahun lalu

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 technology 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").