metadata: {"type": "project", "title": "OpenZeppelin Contracts", "logoImg": "bafkreidefiqxzn5cznwyscxrbg2vpjiylnk3ykbhmtri6gmsmpih6oip7q", "website": "https://openzeppelin.com/contracts", "bannerImg": "bafkreienqyjupdt325s74fyddeej4cfd2cpu5obahzkltv6t7e6yhmnbri", "createdAt": 1699213748696, "userGithub": "xdaluca", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..YeAM27-tNP1xmGXyH97avn5i2WX7HBsDEWYI3hcLkcVHXPHb4rk1ZUlnh698xg3jCTKatIf07oG_x361R8xwDw", "type": "Ed25519Signature2018", "created": "2023-11-05T19:31:45.455Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-11-05T19:31:45.455Z", "expirationDate": "2024-02-03T19:31:45.455Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xfdF797C29AcB326F3902254ab5ae2419eBDfc595", "hash": "v0.0.0:KX1erYmpd5esGjYHxkoEQvJoNdTPmusXFF0ZgSW6g5w=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#OpenZeppelin#80516439"}}}, "description": "**OpenZeppelin Contracts Library**\n\nSince the early days of Solidity in 2016, OpenZeppelin Contracts has been the go-to library for smart contract development. Today it is used by everyone from development teams of the largest projects transacting billions of dollars each day to individuals building blockchain applications.\n\nThe Contracts Library is owned by the OpenZeppelin team, however, the roadmap is highly collaborative and involves a lot of feedback from the Ethereum ecosystem. In addition, to this our team is regularly involved in introducing new ERC and EIP specifications or providing feedback and improvements to the Solidity programming language.\n\n**Impact Metrics**\n\nThe following metrics demonstrate the widespread use and impact of the OpenZeppelin Contracts Library:\n\n- Total Value Locked in OpenZeppelin Contracts on Ethereum Mainnet: $15.67B\n- Active Contracts (2023 YTD): 78,629\n- Deployments (2023 YTD): 26,581\n- Transactions Processed (2023 YTD): 61,062,561\n\nPlease keep in mind that these estimates are approximate. The method used to calculate these on-chain metrics uses [Allium](https://www.allium.so/) to extract data from the Ethereum Mainnet and the [Smart Contract Sanctuary](https://github.com/tintinweb/smart-contract-sanctuary) to segment the data into Total and Verified with OpenZeppelin contracts.\nTo view the full stats [click here](https://contracts.openzeppelin.com/security).\n\n**5.0 Release**\n\nRecently, the team released our 5.0 version of the contracts library, the first major release since 2021. This latest release introduced:\n\n- [Modern best practices](https://blog.openzeppelin.com/introducing-openzeppelin-contracts-5.0#AModernizedContracts5.0)\u00a0work out-of-the-box, including\u00a0[namespaced storage](https://blog.openzeppelin.com/introducing-openzeppelin-contracts-5.0#Namespaced)\n- [Simplified codebase for ever-improving security](https://blog.openzeppelin.com/introducing-openzeppelin-contracts-5.0#Simplifications)\n- [Efficiency improvements, including reduced gas consumption](https://blog.openzeppelin.com/introducing-openzeppelin-contracts-5.0#gas-efficiency)\n- [Modernizing access control with AccessManager](https://blog.openzeppelin.com/introducing-openzeppelin-contracts-5.0#redefining)\n- [More advanced testing, including new fuzzing and formal verification rules](https://blog.openzeppelin.com/introducing-openzeppelin-contracts-5.0#best-in.class)\n\nThe OpenZeppelin team also invested 38 audit weeks to secure the 5.0 release. Please visit our [security center](https://contracts.openzeppelin.com/security) for further details on the security and metrics related to the contracts library.\n\n**Usage of Funds**\n\nThe funds will be used to continue developing the contracts library, provide continuous security checks for new versions and implement feedback from the community received after the 5.0 release. ", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "OpenZeppelin", "projectTwitter": "openzeppelin"}
name: OpenZeppelin Contracts