nostr VS openzeppelin-contracts

Other things that might be worth looking into: Nostr for comms https://github.com/fiatjaf/nostr

nostr (https://github.com/fiatjaf/nostr) seems to be a minimal possible solution. It doesn't seem to be much in use though, so I guess once that happens a few issues will come up.

Nostr [1] seems interesting. I don't trust the idea of "relays" on the long term but it seems like it should be possible to develop alternative ways to distribute the content, and it can be a way to bootstrap the network in the short term. Though at this moment it seems a bit too bare-bones, and it would need some interesting application built on top of it to make it usable.

[1] https://github.com/fiatjaf/nostr

https://github.com/fiatjaf/nostr comes to mind as so far the best example of p2p social networking.

I don’t know if this is the answer you’re looking for because it’s not tied to a cryptocurrency but take a look at nostr: https://github.com/fiatjaf/nostr

It’s a protocol that allows nodes to gossip event messages amongst each other. The event relays can be used as a backend to provide data to your web/desktop/mobile apps.

Nostr stands for "Notes and Other Stuff Transmitted by Relays". It is a new type of social experience on the web where "dumb" relays can be used to send messages from one user to another, in a secure, censorship resistant manner.

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