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
);

💡

You could easily track other providers such as Pinata and other storage entries such as Filecoin, SIA, or Arweave.

Example table in Tableland

id	file_name	file_type	ipfs_cid	provider	ipfs_gateway
1	onboarding.pdf	PDF	`QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR`	filebase.com	https://ipfs.io/ipfs/
2	guidelines.pdf	PDF	`bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi`	filebase.com	https://ipfs.io/ipfs/

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

IPFS

← Previous

Use Cases

On this page

Track & Manage Content on IPFS
Overview
Resources