@masknetwork x @lens roadmap
21/02/2026

(I used Plaud Note Pro)

Meeting Notes

· Product transition status and background

o Ownership and responsibilities for Lens have largely transitioned (~99.9% complete), with remaining legacy issues tied to legal/shareholder matters and domain-related storage incidents.

o Mutual agreements with partners are in place (e.g., Area Lab grant/fee waivers for “last chain,” same terms as earlier PR).

o A lab attack occurred around last October; competition started 5 months ago. Ongoing efforts are dedicated to resolving legacy tech and partner-related items.

· Roadmap priorities: usability fixes, storage, and wallet integration

o Immediate fixes:

§ Extend login session beyond the current 7-day limit to months or a year.

§ Address storage limits, optimize large multimedia uploads, and engage new storage partners (centralized and decentralized) to lower costs and improve efficiency.

o Wallet integration:

§ Use existing crypto wallets as login gateways; avoid proliferation of new private keys.

§ Improve UX and support across wallets (e.g., Rainbow, OKX, exchange-backed wallets); clarify that assets may remain on L1/exchanges while the chain key is primarily for login.

§ Support Social Graph and DIDs; enable sending to handles, mutual connection insights, and block awareness.

§ Provide SDKs for multi-DID support (Mask’s API.w2.bio; compatibility with Lens, Farcaster, etc.) and encourage wallets to integrate multiple decentralized social ecosystems.

o Growth phase (post-fixes):

§ Pursue use cases like enhanced comment sections (e.g., Polymarket) and revive less active users.

§ Partner with apps (Warp, Firefly, WorkCoin with chat → potential posting) and promote cross-client collaboration.

§ Work step-by-step: fix infra, optimize clients, educate partners on social graph core.

o Timeline: Aim to address priorities within 6–9 months.

· Protocol stance and product primitives

o No protocol or smart contract changes planned; protocol remains suitably permissionless.

o Feature needs will be implemented via custom actions and backend/lens-level changes.

o Avoid migrations; Lens chain is Validium, and proposals like ZK-SYNC primitives requiring chain updates are not preferred now. Focus on multi-chain EVM alignment.

· Mini apps and cross-app login

o Mini apps are coming to Orb with shared QR login across Lens apps, reducing repeated wallet connections; SDK testing is underway (email client example).

o Intention to adopt an open, universal mini-app approach aligned with webview UX (learning from WhatsApp-style URL-to-app experiences); criticism of non-open “Caster” mini-apps.

o Related ecosystem context includes Farcaster Frames and David Brown’s Open Frame/XAM Common Protocol.

· Lists, playlists, and namespaces

o Support for on-chain list functionality (decentralized music/video playlists in Grove) can be implemented via simple smart contracts wrapped as “open action” post actions.

o Move towards proper group/club namespaces like @group/name; Orb has a namespace contract that doesn’t require a target account. Plan to provide shared namespace APIs and integration.

· Direct messaging (DM) and chat features

o Collaboration with Orb (DMs exist); open to integrating DMs across clients with potential XMTP alignment.

o Open technical questions: push notifications and decentralized read receipts (“seen” state). DMs remain core; a proposal is planned.

· Private posts, encryption, and payments

o Decentralized encryption for private posts is feasible; the priority is frictionless cross-chain one-click payment (major EVMs, possibly Solana) to make gated content meaningful.

o Current Lens client usability issues (wallet connection, token bridging) necessitate improved cross-chain payment support.

· Content warnings and adult content handling

o Strengthen content warning mechanisms across clients; may evolve to app or protocol-level guidance.

o DMCA handling: prefer labeling and frontend selective display/hiding, preserving on-chain transparency; disputed content can be directed to open-source clients when required.

· Polymarket and client integrations

o Firefly integrates Polymarket; wallets may add similar features. Webview-based integrations are straightforward, enabling attachment to Lens accounts and use via Orb.

· Lens API open sourcing and component licensing

o Backend is a single repo with significant off-chain components; first move more on-chain or make reproducible, then consider open sourcing.

o Orb backend likely open source; frontend not planned (duplication concerns, mobile complexity). Firefly’s web-related stack (HTML/JS) is more likely to be open-sourced than mobile-specific parts.

o Lens v3 contracts are currently “unlicensed”; plan to revisit licensing (e.g., MIT or GPL) after internal discussions.

o Commitment to open source parts helpful to the community and support with implementation Q&A.

· Build on Lens versus forking; governance and LIPs

o Encourage building on Lens rather than forking; collaborate and share protocol evolution.

o Governance token is possible but not meaningful now; prefer non-speculative governance (SBTs, handle-based weight, behavior-based voting).

o Clarify protocol vs app boundaries; adopt compatible external solutions when sensible (e.g., XMTP for DMs).

o “Sign-in with Lens” should avoid risky wallet interactions for simple posting; welcome “do-not-build” proposals when partners excel.

· Grove: private files and large media

o Clients can encrypt private file uploads today. Grove (IPFS wrapper) has a 125 MB limit; larger files and streaming (no transcoding) are challenges.

o Plan to work with ecosystem partners on large files and streaming improvements; explore client-side streaming enhancements.

· Token rewards contract access; rewards and incentives

o Request to open public access to token rewards contract is under consideration; governance and privacy implications require discussion.

o Past cash/points rewards attracted professional “farmers”; pivot to real-world coupon incentives (e.g., dining, coffee, gaming) targeted to genuine users, citing successful Haidilao partnership (~100,000 SGD coupons, verifiable engagement).

· ML model updates

o Plan to refresh and streamline ML model hosting and backend integration; leverage Web3 bio/history data. Model hasn’t been updated in over a year.

· Onboarding content creators and addressing monetization realities

o Creators resist crypto payments and worry about piracy/DMCA; implement frontend verification, selective display/hiding, and transparent labeling instead of takedowns.

o Meme/content coin models are inadequate for serious creators; improve real-world monetization, including payments and pay-to-unlock DMs.

o Build genuine relationships with adult creators and journalists; learn from BlueSky’s reputation systems, domain verification, and common payment/communication tools (Substack, Signal).

· Why builders and users should return to Lens now

o Lower gas costs and scalable data storage (e.g., L1 blobs) make Lens more attractive than 2022-era constraints on Polygon.

o Centralized platforms have become more closed/expensive (API/agent posting costs), strengthening the case for decentralized social.

o Plan to let users project/mirror social graphs (e.g., Twitter follows) onto Lens via GDPR-compliant JSON writes.

o Lens can continue gas sponsorship via API with abuse safeguards; focus on clearer tooling and documentation for developers and AI builders.

· Desired applications and experiments

o Email-related experiments (many users rely on AI-assisted email).

o Pay-to-unlock plus creator economy plus DM flows enabling monetized direct messaging with strong UX.

o Use Lens social graph verification for finance/trading/copy-trading apps.

Next Arrangements

☐ Extend login session duration beyond 7 days.

☐ Optimize storage limits and multimedia handling; finalize partnerships with storage providers (centralized and decentralized).

☐ Improve wallet support and UI/UX across key wallets (e.g., Rainbow, OKX, exchange-backed wallets); communicate wallet integration philosophy and provide SDKs for multi-DID support.

☐ Enhance Social Graph and DID features (send to handle, mutual friend insights, block awareness).

☐ Coordinate with app partners (Warp, Firefly, WorkCoin) for feature optimizations, posting, and cross-client feature sharing.

☐ Develop improved comment sections (e.g., for Polymarket) and encourage webview integration across clients.

☐ Draft proposal for universal, open mini-app integration aligned with webview UX; leverage QR login sharing.

☐ Outline smart contract and “open action” approach for on-chain playlists/lists in Grove.

☐ Prepare a DM integration plan covering push notifications and decentralized “seen” states; evaluate XMTP alignment.

☐ Define cross-chain, one-click payment flow for gated/private posts across EVM (and possibly Solana).

☐ Strengthen content warning standards and propose protocol-level guidance; implement DMCA verification and selective display/hiding.

☐ Document and share group namespace API and contract details.

☐ Engage ecosystem partners for large media handling and streaming (transcoding) for Grove; improve client-side streaming.

☐ Review and decide on a license for Lens v3 contracts (e.g., MIT or GPL); identify which Orb/Firefly web components to open source and publish repositories.

☐ Provide a public guide/FAQ for developers on open-sourced parts and contribution paths.

☐ Plan ML model refresh and integration into backend ecosystem.

☐ Assess feasibility and governance implications of opening token rewards contract access.

☐ Design and pilot coupon-based reward programs targeting authentic users.

☐ Develop and document social graph projection/mirroring from Twitter to Lens (GDPR-compliant).

☐ Maintain gas sponsorship via Lens API with abuse monitoring; improve developer documentation and simplify key management/onboarding flows.

☐ Define and implement labeling mechanisms to support AI-only social experiments on Lens.

☐ Establish outreach plan to engage professional content creators (journalists, adult creators) for onboarding feedback.

AI Suggestions

AI Suggestions