<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>futureprotocol</title>
        <link>https://paragraph.com/@futureprotocol</link>
        <description>undefined</description>
        <lastBuildDate>Tue, 28 Apr 2026 04:08:11 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[The new age of digital property ownership]]></title>
            <link>https://paragraph.com/@futureprotocol/the-new-age-of-digital-property-ownership</link>
            <guid>A3ZVOdXcrpEKIDyhwBq3</guid>
            <pubDate>Mon, 10 Oct 2022 03:46:42 GMT</pubDate>
            <description><![CDATA[Lewk.app is a place where you can mint, buy, and re-sell polygon NFT keys and augment the utility in-house by creating NFT-gated digital properties (e.g. secret text, calendar links, etc ) on lewk.app Unlock protocol has an integration to lock a webpage with integrations with Wordpress and Drupal, but there is no component level locking and no existing solution for non Wordpress, Drupal users. Decentraland, guild.xyz, use unlock protocol to gate discord and telegram, but no solution for build...]]></description>
            <content:encoded><![CDATA[<p><strong>Lewk.app is a place where you can mint, buy, and re-sell polygon NFT keys and augment the utility in-house by creating NFT-gated digital properties (e.g. secret text, calendar links, etc ) on </strong><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="http://lewk.app/"><strong>lewk.app</strong></a></p><p>Unlock protocol has an integration to lock a webpage with integrations with Wordpress and Drupal, but there is no component level locking and no existing solution for non Wordpress, Drupal users. Decentraland, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="http://guild.xyz/">guild.xyz</a>, use unlock protocol to gate discord and telegram, but no solution for building the CMS with native token gating configuration, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="http://cal.com/">cal.com</a> uses unlock protocol to lock secret meetings. But what if you can token gate your calendar, blogs, and chat all in one place? </p><p>We are building a solution to satisfy the need to have finer-grain gated elements (or we call digital properties) hence ownership of it, we also support minting, buying and selling the token in-house in Polygon. </p><p>We call it a B2B2C access token marketplace and SDK for “buy my NFT then ask me anything” app, changing the access and ownership of digital properties from consumable &amp; commodity to investment. </p><p>You might ask: </p><p>Why pay in NFT when I can pay via stripe? The answer is: so you can resell it later or transfer the ownership if you want!! (e.g. sell your web blog, access to your calendar, your social post? no easy way in web2, but we are creating a market for it thanks to blockchain technology)</p><p>Imagine you can buy an e-book backed NFT and read it, then you can easily re-sell it later, we let you opt-in mint a proof-of-knowledge NFT and give the original author x% (say 50%) royalties, and you recoup 50% of the cost. ** **</p><p>Now, if we zoom out and look at all the digital content and web/mobile front end element, we can decouple the content from the gating condition (which can be NFT keys + Web2 social verification), and it gives us the freedom to scale up the former to be a headless CMS API to be used across mobile / web client and across devices, and the later being configurable gating conditions per semantic element (think component library in any product design system) via admin dashboard + analytics. ** **</p><p>We envision this being a platform for any brands, business,  creators, and knowledge influencers etc etc creating member-only experience by creating a headless token-gatable CMS where the admin indicates the type of component and the gating NFT contract address, token ID, and chain ID and push exclusive content to their token holders. (And yes, there is ways to notify your NFT holders you have created new exclusive content in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="http://lewk.app/">lewk.app</a>, think the web3 equivalent of you posting an update and all your friends get notifications.)</p><p>This is just the beginning of claiming ownership of digital properties beyond just the jpeg. (e.g. you can directly auction the access to your calendar,  your playbook anything you can think of on a web page or mobile UI, etc)</p><p><em>We are believers in community-first approach and will appreciate any advice or suggestions in building close relationships with our potential customers or ideas in lowering user friction.</em></p><p>P.S. </p><p>We are also big believers of the “client-driven protocol” approach —  First creating use cases with cool app which attracts users, then open up the “server side” to be multi-chain and a reusable, and composable API/protocol for other startups/communities to build Dapps on. </p>]]></content:encoded>
            <author>futureprotocol@newsletter.paragraph.com (futureprotocol)</author>
        </item>
    </channel>
</rss>