Mosaic

Problem Statement

The Mosaic Content Protocol enables:Content Creation: Creators upload content to IPFS via Lighthouse and register it on ENS domainsMicropayments: Users pay to access content with small payments (e.g., 1 cent)Curation Staking: Users stake PYUSD tokens on content they believe will be popularRevenue Sharing: Payment from content consumption is distributed to stakers based on their vault sharesENS Integration: Content is versioned and accessible via ENS text records (e.g.,artist.eth,researcher.eth)Content LifecycleCreation:createContent("bitcoin-whitepaper", ipfsHash, price, commission)Deploys dedicated vault for the contentSets ENS text record:contentId@1 = ipfsHashCreator becomes initial ownerAccess: Users callbuyAccess(contentId)Pays PYUSD to content vaultReceives soulbound ERC1155 access tokenGains permanent access to contentStaking: Users stake PYUSD in content vaults to earn from future access purchasesUpdates: Creators can update content versions:updateContentVersion(contentId, newIpfsHash)Increments version:contentId@2 = newIpfsHash

Solution

Core ComponentsContentAccessToken: ERC1155 contract managing content creation, access control, and paymentsSimpleVault: ERC4626 vault for staking PYUSD tokens and earning rewards from content consumptionENS Integration: Content metadata stored in ENS text records with versioning (content@versionformat)🏗️ ArchitectureCreator uploads content → IPFS (Lighthouse) → ENS text record → Smart Contract ↓ User pays for access → Mints Access NFT → Payment → Content-specific Vault ↓ Distributed to Stakers🛠️ Technical StackBlockchain: Ethereum (Sepolia testnet)Payment Token: PYUSD (6 decimals)Storage: IPFS via LighthouseNaming: ENS text records for content resolutionTesting: Foundry framework