openzeppelin-contracts VS solmate

In this explanation, we use OpenZeppelin’s TransparentUpgradeableProxy.

In parallel with these scalability enhancements, the open source movement has accelerated blockchain innovation. Resources like OpenZeppelin Contracts provide pre‑audited libraries for smart contract development. Open source tools empower developers to iterate quickly, achieve transparency, and establish community governance over projects. Moreover, sustainable open source funding models—such as Gitcoin and GitHub Sponsors—help projects maintain long‑term development and security.

ERC721 is a standard that describes how to build NFTs on EVM compatible blockchains. We use the OppenZeppelin implementaion of ERC721

// SPDX-License-Identifier: GPL-3.0 pragma solidity ^0.8.20; import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v5.0.0/contracts/token/ERC20/ERC20.sol"; interface Sfs {     function register(address _recipient) external returns (uint256 tokenId); } contract ModeToken is ERC20 {     address feeReceiver = msg.sender;     constructor() ERC20("ModeTokenSFSTest", "SFST2") { //Example amount to mint our ERC20         _mint(msg.sender, 1000 10 * 18);   // This is the SFS contract address on testnet Sfs sfsContract = Sfs(0xBBd707815a7F7eb6897C7686274AFabd7B579Ff6); //Registers this contract and assigns the NFT //to the deployer of this contract sfsContract.register(msg.sender);     } }

Lets look the events of Open Zeppelin’s ERC20 token contract:

ERC-777 is difficult to implement properly, due to its susceptibility to different forms of attack(opens in a new tab). It is recommended to use ERC-20 instead. This page remains as a historical archive.

You can also look at Solmate's implementation: https://github.com/transmissions11/solmate

Solmate building blocks

Use battle-tested and audited code. OpenZeppelin, Solmate.

If you are wanting to read some code, here's a an "ERC20" contract (a "money").

https://github.com/Rari-Capital/solmate/blob/main/src/tokens...