Skip to main content

How do I… use DIGHUb?

Publish and manage your store from the browser. DIGHUb at hub.dig.net is the no-CLI front door: drop in a built site, preview it for free, and connect a wallet only at the moment you publish. This page is the shortest path through the things you'll actually do.

The mental model​

A store is your site's permanent, on-chain identity — you control it with your wallet (your wallet is your account; no email, no password). Each publish seals the current build into one immutable capsule. Building and previewing are free; you pay the uniform capsule price in $DIG only when you publish.

How do I create a store and publish my first capsule?​

Start a new store in DIGHUb ↗, drop in your built folder (dist/ or build/), preview it free on the real read path, then hit Publish and approve the one on-chain spend. That mints your store and publishes its first capsule.

→ Quickstart → Publish from the web

How do I ship an update?​

Re-upload the new build, preview the draft for free, and Publish again. Each update is a new capsule and costs the uniform capsule price; old capsules stay readable forever, and your store always resolves to its latest unless a reader pins a specific version.

→ Quickstart → ship an update · On-chain anchoring

How do I share it / give it a web address?​

The moment a capsule confirms it's readable by its URN / chia:// address — universal, free, nothing to register. For a friendly <name>.on.dig.net handle (or a custom domain with TLS), register one in DIGHUb — an optional, paid step on top of the always-available address.

→ Can I get a *.on.dig.net address or use my own domain?

How do I get tipped for my store?​

Every store has a public tip page (https://hub.dig.net/tip/store/<your store id>), and a one-line script drops a Tip button onto any site. Tips go wallet-to-wallet in $DIG — DIGHUb never touches the funds.

→ Get tipped for your store

How do I let CI publish for me?​

Issue a deploy key (a revocable key that can publish but never touch ownership) in your store's Automation tab, then wire it into CI — or use the GitHub deploy Action for push-to-publish with free PR previews.

→ Deploy keys · Deploy from GitHub Actions

How do I get notified when a deploy finishes?​

Register a webhook in the Automation tab to receive a signed event when a deployment changes state.

→ Webhooks

Stuck?​

  • FAQ — quick answers (cost, updates, privacy, domains).
  • Troubleshooting — the common failures and their fixes.
  • Get help — the community and how to file a good report.

Go deeper​