About
Protocol
Walkthroughs
Integrations
Intro to NFT Metadata
Tutorials
Smart Contracts
Concepts
Playbooks
Learn
Track & Manage Content on IPFS
Create table for tracking asset name, type, and location (CID) on IPFS.
Overview
Web3 and IPFS go hand-in-hand. But one thing has always remained difficult, how to track the metadata associated with hashes stored on the IPFS, Filecoin or Arweave networks. Tableland allows projects to create tables of assets, where each asset is a row, and the raw data is a column pointing to a hash on IPFS. The data can be extended further to add useful metadata such as pinning gateways or storage providers that are making that hash available when users aren’t.
CREATE TABLE AssetTracker (
PRIMARY KEY (id),
TEXT file_name,
TEXT file_type,
TEXT ipfs_cid,
TEXT provider,
URL ipfs_gateway
);
Example table in Tableland
id | file_name | file_type | ipfs_cid | provider | ipfs_gateway |
1 | onboarding.pdf | PDF | QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR | ||
2 | guidelines.pdf | PDF | bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi |
Any app can now read the table and easily reconstruct the provenance of the data as well as the best place(s) to go fetch the data.
Resources
← Previous
On this page