ERC20 token with the following features:  - Premint your total supply.  - No minting function. This allows users to comfortably know the future supply of the token.

ERC20 token with the following features:  - Premint your total supply.  - No minting function. This allows users to comfortably know the future supply of the token.  - Methods that allow users to burn their tokens. This directly decreases total supply. Used to burn tokens from the supply.

ERC20 token with the following features:  - Premint your initial supply.  - Mint as many tokens as you want with no cap.  - Only the contract owner can mint new tokens.

ERC20 token with the following features:  - Token owners can vote on Governance/DAO proposals.  - Premint your total supply.  - No minting function. This allows users to comfortably know the future supply of the token. Used with Governance/DAO contracts for voting.

This contract allows payments to be split among a group of accounts. The split can be in equal parts or set in percentages. The way this is specified is by assigning each account to a number of shares. Of all the Ether that this contract receives, each account will then be able to claim an amount proportional to the percentage of total shares they were assigned. The distribution of shares is set when you deploy the contract and can't be updated afterwards. Payments must be claimed from the contract by each user. NOTE: This contract assumes that ERC20 tokens will behave similarly to native tokens (Ether). Rebasing tokens, and tokens that apply fees during transfers, are likely to not be supported as expected. If in doubt, we encourage you to run tests before sending real value to this contract.

ERC20 token with the following features:  - Premint your total supply.  - Minting is allowed, but only up to the maximum cap.

This contract implements the ERC721 standard for non-fungible tokens (NFTs). It allows users to create, own, transfer, and manage unique tokens. The contract includes functions for minting tokens, transferring ownership, checking balances, and managing approvals. It also provides metadata functions for retrieving token names, symbols, and URIs.

This contract acts as a proxy, delegating calls to another contract specified by `_implementation()`. It handles the delegation of calls, copying data, and returning results.

This ERC20 contract implements a standard token with basic functionalities such as transferring tokens, checking balances, and approving token allowances. It also includes functions for minting and burning tokens. The contract keeps track of token balances using a mapping and allows for the setting of token name, symbol, and decimals.

The ERC1967Proxy contract is an upgradeable proxy contract that allows for the initialization of an initial implementation and provides a function to retrieve the current implementation address. It utilizes the ERC1967Utils library for upgrading and calling the implementation.

Delays the execution of a separate contract function. Primarily used as part of a DAO Contract module which acts as a timelocked controller. When set as the owner of an `Ownable` smart contract, it enforces a timelock on all `onlyOwner` maintenance operations. This gives time for users of the controlled contract to exit before a potentially dangerous maintenance operation is applied. By default, this contract is self administered, meaning administration tasks have to go through the timelock process. The proposer (resp executor) role is in charge of proposing (resp executing) operations. A common use case is to position this {TimelockController} as the owner of a smart contract, with a multisig or a DAO as the sole proposer.

The MyTokenWrapped contract is an ERC20 token wrapper that allows users to wrap and unwrap an underlying ERC20 token. It inherits from multiple ERC20-related contracts and overrides necessary functions for compatibility.

0xmonsoon

Allarious

andresbach

CallMeGwei

canercidam

clarkhenry

cre-mer

cylon56

dylankilkenny

ericglau

ericnordelo

ernestognw

frangio

martriay

MCarlomagno

mwakaba2

nikitastupin

shahnami

sipox11

Vanclief

xdaluca

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.