schnorr-verify VS openzeppelin-contracts

Would it maybe be better to incorporate web3 tools into the existing network? Constructing an entirely separate parallel set of servers and software, and getting enough people to use them, seems pretty costly and difficult. What about instead using the metadata events to publish web3 addresses in association with a npub address, similar concept to https://github.com/nostr-protocol/nips/blob/master/05.md, and including an additional web3 generated signature as a tag for events you want to be verifiably associated with your Eth wallet? The features you describe like using ens and direct NFT ownership checking would be possible this way, only needs a client that supports them. The dns based identity does enable some workarounds for using eth addresses. The problem is those events are still signed shnorr sigs of sha256 hashes. That is something that can be worked around and there already is existing solutions in sol (https://github.com/noot/schnorr-verify)

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.