Home
About
What is Tableland?
Rigs NFT
Our Vision
Open Beta
FAQs
Protocol
Limits
Deployed Contracts
Response Times
Considerations & Tradeoffs
Affecting Tableland State
Walkthroughs
Prerequisites & Repos
Quick Start
JavaScript SDK
CLI
JSON RPC API
REST API
SQL Specification
Chains
Choosing a Chain
Using Polygon
Deploying an NFT on Polygon
Intro to NFT Metadata
NFT Metadata Standards
Crafting NFT Metadata with SQL
Store & Edit Metadata with the CLI or SDK
Serving NFT Metadata from Smart Contracts
Tutorials
Build a Dynamic NFT in Solidity
Creating a Dynamic NFT with p5.js & Tableland
Smart Contracts
Creating Tables from Contracts
Configuring Table Write Access
Solidity to SQL Types
Using Remix
Concepts
URI Encoding
Table Queries & Joins
Table Writes & Updates
Incrementing Values Automatically
Query Optimization & Gas
Playbooks
Create a Key-Value Store Table
Create an Immutable Table
Create a Table for Immutable Files on IPFS
Learn
Use Cases
Code Examples
Security
Web3 Basics
Roadmap
Community
Paywalls via NFT Ownership
Create paid content that is only visible to the current owners of an NFT.
Overview
Mirror.xyz articles can often have limited edition NFTs included to support the authors. E.g., see the article here.
There are a few ways we could play with this. One is that the authors could create follow-up content that only the NFT owners can read. How? Whenever they author the new content they should encrypt it for only the current owners of the nft and embed it in a table. Example, 10 owners, 10 different encryptions. Selling the NFT wouldn’t get you access to old content, but it would get the new reader access to content going forward. Pretty cool! We’ve seen hackathon projects try to do similar with Threads before.
Resources
← Previous
On this page