Attestation Station

Screenshots

Problem Statement

Our tool allows for a PDF legal contract to be minted as an NFT that is linked to an ERC20 token and attestation information via Sign Protocol in it's metadata. I used Open Sea's metadata standard to allow for custom attributes to be added, which basically followed this order:select the PDF legal document that details what rights the NFT will havedefine the NFT name, description, attributes etcmint ERC20 token for use in Defi such as a uniswap AMMadd ERC20 token into NFT metadataupload PDF and put IPFS hash into metadatamint NFT with the included metadata attributes (ERC20 + Document Hash)Sign Protocol to attest that NFT has that Token + Document so that in the future if the owner attempts to mint a different token or attach a different document the differences will be detectable.add the attestation to the metadata and re-apply by setting the tokenURI with the updated metadata urlFor the attestations I used the schema creation tool from their UI but created and read the attestation via their SDK. Fleek for IPFS.

Solution

I was able to use some boilerplate frontend code, then created a multi-step form to walk someone through uploading data to IPFS using Fleek, minting an ERC20 token, then signing all that metadata with Sign Protocol. Nothing particularly fancy with integrations from rainbowkit, viem, wagmi, chakra ui etc.