The problem Paper solves

Traditional publishing platforms (Medium, Substack) act as rent-seeking intermediaries. They control the creator's identity, gatekeep the revenue, and force intrusive ad networks on readers that don't directly benefit the author. Creators suffer from platform lock-in, while advertisers struggle to find high-intent, niche audiences in a decentralized way.

Paper solves this by turning content into a sovereign monetization asset:

• For Creators: It provides wallet-native provenance. Articles are minted as ERC-721 "On-chain Publication Records." Authors keep 100% of their earnings from paywalls and sponsored slots, routed through peer-to-peer smart contracts.
• For Readers: It introduces a friction-less "Pay-per-Read" model using the x402 protocol. Instead of monthly subscriptions, readers pay tiny amounts of ETH/USDC to unlock specific high-value content directly to the author.
• For Advertisers: It removes the complexity of Web3 ad buying. Using PaperBot, an AI-driven inventory agent, advertisers can discover trending articles, upload creatives, and fund campaigns via a Telegram chat.
• For Identity: By leveraging ENS subnames (e.g., author.paper.eth), Paper ensures that a creator’s reputation and audience are portable and not owned by a single database.

Challenges we ran into

1. AI Agent Economic Identity: Getting an AI agent (PaperBot) to handle complex financial transactions—like calculating campaign costs and executing swaps via HeyElsa was difficult. We integrated the HeyElsa x402 SDK, allowing the bot to use "Agentic Commerce" to pay for its own API calls and facilitate user payments for ad slots seamlessly.

2. Seamless ENS Onboarding: Registering subnames usually requires multiple transactions and gas. To make it "Web2-easy," we implemented a server-side ENS Registrar that allows users to sign a message claiming their username.paper.eth identity, which our backend then executes on-chain, drastically lowering the barrier to entry for new writers.

3. Markdown Rendering in Telegram: Formatting rich-text article previews for a Telegram bot is notoriously buggy. We built a custom markdown "cleaner" and parser to ensure that decentralized content looks professional and readable within the chat interface.

4. Decentralized Gating Logic: A major hurdle was ensuring content remained private on IPFS until a payment was verified without requiring a centralized database. We solved this by building a Conditional Content API that intercepts requests, checks the on-chain "Paid" state for the user's address, and only then streams the full content from IPFS.