ethereum-developer-tools-list VS openzeppelin-contracts

Great project! Getting people being able to actually test and debug stuff on the local chain is a massive pain in the bum. Have you thought about adding this to: https://github.com/ConsenSys/ethereum-developer-tools-list/blob/master/README.md

Sure, https://github.com/ConsenSys/ethereum-developer-tools-list/blob/master/README.md

Check out scaffold-eth on GitHub, it has a bunch of branches of example projects that you can look at. Also, Consensys has a great repo which compiles a ton of great resources for Blockchain development.

I am not sure exactly what you are looking for. Consider "listening" directly on the Github: https://github.com/ConsenSys/ethereum-developer-tools-list

Ethereum Developer Tools List

#1: Long list of Ethereum developer tools, frameworks, components, services.... please contribute! | 58 comments #2: First Ethereum project: Automated reoccurring payments (Solidity, Reactjs, Truffle, Ganache) | 29 comments #3: Ethereum 2.0 has officially launched | 32 comments

// 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.