SansScript

The project, called SansScript, is an innovative tool that combines web2 newsletter features with web3 capabilities. It enables users to create, publish, and subscribe to diverse newsletters in a decentralized and censorship-resistant way. SansScript leverages web3 technology to ensure content permanence on a decentralized network and allows content creators to receive direct payments from their audience without intermediaries. It uses different protocols for certifications, messaging, notifications, accessing and querying data, storage and payment solutions. Overall, SansScript aims to provide a transparent, decentralized, and user-friendly platform for newsletter creation, distribution, and monetisation. Empowering writers, embracing Web3 and unleashing decentralized newsletters.

SansScript uses many different protocols to allow users to write, read and subscribe to newsletters in a decentralised, censorship-resistant way. It uses attestations from the @EAS protocol, sends messages using the @XMTP protocol, @Safe{Core} SDK kits to allow users to login with an email or address and let them pay with FIAT or Crypto, @The Graph for indexing and querying data, @IPFS for storing images of newsletters, @WorldCoin to have verified humans, @ApeCoinDAO for allowing users to pay in ApeCoin in a native way and the @Push protocol to notify users when there is a new message from any newsletter they have subscribed to.

Users can sign in to the dApp using two methods: the Metamask SDK or the Safe Sing-in Kit using Account Abstraction. Newsletter creators can verify with Worldcoin and then create a newsletter profile using a smart contract that indexes data in a new subgraph. Once the newsletter is created, readers can access the interface and subscribe to an existing newsletter. Users can subscribe to newsletters by paying with USDC and ApeCoin or using the on-ramp solution provided by Safe. Once the user pays for the subscription, the API triggers an attestation, which is done using a custom schema on EAS, and then this information is passed into the smart contract. When a creator writes a new newsletter, the protocol checks which address has an active subscription and sends the message via Xmtp and sends notifications via push protocol.