ZKsig NFTs

Screenshots

Problem Statement

Click here to watch our videoWe used the FEVM to create ERC-721 NFTs from legally binding agreements like Docusign meets the blockchain.Additionally, we created four delegated authorization contracts for marketplace deal proposals that gates access via NFTs:ProviderNFTDealClient- ensures that a deal provider owns an NFT.ClientNFTDealClient- ensures that a deal client owns an NFT.CommonNFTDealClient- ensures that the provider and client own an NFT.AgreementNFTDealClient- ensures that the provider and client have signed a legally binding agreement (verified via NFT).With this infrastructure in place, a host of marketplace use cases open up:DataDAOonly deal proposals where membership is managed via NFTOn-chain enforced legally binding service agreementsImplement terms of service for a marketplaceEnforce KYCrules for a marketplace

Solution

FEVM to store digital signature and agreement informationFilecoin/IPFS to store encrypted agreement PDFs and metadataFEVM to create NFTs for agreementsFEVM to create DealClientsWe are still unsure about how to get an f410 address or FEVM address from the MarketAPIs call to our DealClients. We've hacked this together via the mocks for now, but in the future, we'll need to figure out how addresses are passed.