Skip to main content

For content consumers

Open chia:// content that your OWN browser verifies against the blockchain — no host can alter or fake it, private content stays private from the host, and it's permanent and re-hostable anywhere, so nobody can take it down or lock you in.

The mental model​

Paste a chia:// link and the content comes straight from the network — content-addressed and cryptographically verified on YOUR device before it renders. It is fail-closed: tampered or undecryptable bytes never show.

  • Omit the rootHash for the store's latest version: chia://<storeId>/.
  • Include it to pin one exact immutable capsule: chia://<storeId>:<rootHash>/.

Public content needs only the link. Private content also needs a secret ?salt= — like a password.

Get the DIG Browser, or the extension​

  • Get the DIG Browser ↗ — a browser with chia:// and a built-in wallet baked in.
  • The extension for Chrome / Edge / Brave / Firefox — adds chia:// resolution to a browser you already use.

Open chia:// content — latest vs pinned​

The address forms, the clean chia://<store>/ bar, and when to pin a rootHash.

→ The chia:// protocol

Built-in pages, the verified badge & shields​

chia://home, chia://wallet, chia://settings, and the verified badge / shields that show each resource's inclusion-proof verdict for the active capsule.

→ Using window.chia

Public vs private — when you need a ?salt= secret​

Public stores open with just the link; private stores require the secret salt that derives the decryption key.

→ Public vs private stores · Public vs private — what's the difference?

Run content locally (optional)​

Point your browser/extension at a local dig-node for faster, offline-friendly reads — they share one .dig cache. You never need a node to read.

→ Run a node

Get $DIG​

You don't need $DIG to read content. If you want to publish, get $DIG on TibetSwap, dexie.space, or 9mm.pro.

→ Where do I get DIG?

Go deeper: the protocol​