AdSpaces

Screenshots

Problem Statement

👋 Our goal is to create a crypto-native web traffic monetization platform, honoring the principles of web3: decentralization, self-custody & composability. Thus we develop a web3 dapp with as many components completely decentralized as possible, keeping rewards functionality on-chain to enable interoperability.MVP includes:Create AdSpace listingsBundle AdSpace integration with websites in a simple embed codeVerify listing websites have indeed integrated our codeBrowse AdSpace listingsCreate an advertising Campaign - store media & metadata on decentralized infrastructureClose an Advertising Deal - matching a Campaign to run on an AdSpace for an agreed time & price.User Dashboard - manage owned AdSpaces / Campaigns

Solution

Our platform is deployed on Optimism GoerliWe are using TableLand as our main storage layer; all deals, adspace listings and campaigns are stored in distinct tables owned by our AdSpaceFactory contract.Our AdSpaceFactory contract deploys a new AdSpace contract for each AdSpace listing triggered by a user, and also updates TableLand with the new entries.Said AdSpace contract also implements ERC721Enumerable and mints an amount of Equity NFTs selected by the user (1 - 20 NFTs max) which correspond to proportional equity on the revenue generated by the AdSpace.These NFTs can be traded on secondary marketplaces ( we are leveraging QX as secondary sales marketplace for our NFTs ) or used in any other ERC721 compatible protocols like lending.We built a full in-browser IPFS node for users to upload their campaigns file and have them accessible on the IPFS network in a completely decentralized manner.We used Quicknode as provider for all contract interactions (querying the AdSpace contracts, DAI contract approvals)We are retrieving ENS avatar from user addresses and displaying on the frontend (if any)Finally our JS library AdSpaces.js loads ads by fetching data from completely decentralized infrastructure (TableLand & IPFS)