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 (Latest)
Upgrading SDK (v3 to v4)
JavaScript SDK (Legacy)
CLI
Validator API
REST API (Legacy)
SQL Specification
Local Development & Testing
Integrations
Choosing a Chain
Using Polygon
Using Optimism
Using Arbitrum
Deploying an NFT on Polygon
Dynamic NFT with Chainlink Automation
On-Chain Reads with Chainlink + Arbitrum
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
Public Metadata for Private Information
Leverage public tables deployed on tableland to describe private content hosted elsewhere.
Overview
If you're looking to store private data on decentralized storage, then Tableland + Lit Protocol is a perfect combo! Tableland provides a powerful SQL-based decentralized storage engine. Lit Protocol provides a flexible decentralized encryption system that you can use to delegate who is able to decrypt your Tableland data.
It’s simple
- Create a new table in Tableland.
- Encrypt the data before putting it into the table and decrypt it when they pull it out using Lit.
Resources
Check out the Lit Protocol dev docs here: https://developer.litprotocol.com/docs/intro
← Previous