← Back to home

mint-to-atst

As soon as a NFT has been minted, issue an attestation in the atst system from OP - the attestation sender is the deployer of the NFT contract and the receiver is the minter

Screenshots

mint-to-atst screenshot 1
mint-to-atst screenshot 2
mint-to-atst screenshot 3
mint-to-atst screenshot 4
mint-to-atst screenshot 5

Problem Statement

The project allows to issue an attestation from the deployer of a NFT smart contract to the minter of said NFT automatically.We use a demo smart contract for NFT from thirweb https://thirdweb.com/thirdweb.eth/OpenEditionERC721Alchemy is used for listening to the NFT smart contract mints and send a webhook to a cloudflare worker https://www.alchemy.com/custom-webhooksThe cloudflare worker receives mint events from the alchemy webhook. It does the atst creation from the contract deployerThe schema for the atst is https://optimism-goerli-bedrock.easscan.org/schema/view/0xedc8a2bf856db87850a0483a7f090abc12cafcb6fa477c3732b5e52b65f4e959. It mainly a stringmintedwhere we store the transaction hash of the mint.

Solution

The worker folder is cloudflare worker deployed at https://worker.sliponit9471.workers.dev/ It receives POST from the alchemy webhook listening to mints. First it derivers the minter address and the mint transaction hash from the body of the webhook. Then it sets up the attestation services withthose data, plus a provider, plus a signer 5the contract deployer but could be anything), plus the schema UID. Then the worker issues the attestion and returnsThe frontend folder contains a webpage deployed on cloudflare pages at https://mint-to-atst.pages.dev/ - it is mainly an embed to a thirdweb page to mintThe eas folder contains a script to issue a attestation; unused, just for debugging

Hackathon

ETHOnline 2023

2023

Contributors