diff --git a/docs/digstore/cli/onchain-anchoring.md b/docs/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/docs/digstore/cli/onchain-anchoring.md
+++ b/docs/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/docs/support/faq.md b/docs/support/faq.md
index 6198452..f7dda17 100644
--- a/docs/support/faq.md
+++ b/docs/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/de/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/de/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/es/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/es/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/fr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/fr/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/hi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/hi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/hi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/hi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/hi/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/hi/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/hi/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/hi/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/id/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/id/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/id/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/id/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/id/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/id/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/id/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/id/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/ja/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/ja/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/ko/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/ko/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/ru/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/ru/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/tr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/tr/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/vi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/vi/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
index 81d9148..8c65f03 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/digstore/cli/onchain-anchoring.md
@@ -75,6 +75,8 @@ The price is **uniform per capsule** — the same whether you mint (`init`) or c
 
 **$DIG** is the DIG Network token (a Chia CAT). The $DIG payment is included **atomically in the same spend bundle** as the mint or deployment root update — there is no separate transaction. The memo on the DIG output is the store id. Before submitting, each command prints the cost and your current balance; if the wallet is short on XCH **or** DIG the command blocks with a clear message rather than broadcasting a partial spend. Use `digstore balance` to check your spendable XCH and DIG at any time:
 
+Publishing through [DIGHUb](https://hub.dig.net) with a **Super Supporter** NFT held in your wallet halves the capsule price. DIGHUb checks live ownership across every address in your wallet at publish time and shows/charges the discounted amount, the same live check used for the [handle discount](../../support/faq.md#can-i-use-my-own-domain). The discount applies only while the NFT is in that wallet; if it's staked, moved, or sold, DIGHUb charges the full price instead. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one. The `digstore` CLI's `init`/`commit` always spend the full live price shown above — the discount currently applies only when publishing through DIGHUb.
+
 ```sh
 digstore balance          # shows XCH (mojos), DIG (3-decimal), and receive address
 digstore balance --json
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
index 9c553f6..a15030f 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md
@@ -6,6 +6,7 @@ keywords:
   - universal installer
   - dig-node install
   - dig.local
+  - dig-dns
   - Windows service
   - launchd
   - systemd
@@ -32,6 +33,29 @@ The installer registers **`dig.local`** for your machine so consumers on the sam
 The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones.
 :::
 
+## Browse `.dig` names directly {#browse-dig-names-directly}
+
+Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns)
+— a local `*.dig` name resolver — as an OS service (Windows Service / macOS
+LaunchDaemon / Linux systemd):
+
+```sh
+curl -fsSL https://dig.net/install.sh | sh -s -- --with-dig-dns
+```
+
+This lets a browser open `http://<storeId>.dig/<path>` directly: dig-dns resolves the
+store's chain-anchored root and serves its content from your dig-node. The installer
+wires OS split-DNS (or an NRPT rule on Windows) and, as a fallback, a PAC proxy file
+for browsers that bypass the OS resolver (e.g. a browser forcing DNS-over-HTTPS) —
+either path alone is enough for `.dig` URLs to load. It never edits `/etc/hosts`,
+never rewrites URLs, and never intercepts TLS. Run `dig-dns doctor` any time to check
+which path is live and get a fix hint for what isn't.
+
+The [extension](../audiences/content-consumers.md)'s "open a chia:// address or DIG URN"
+input on its home screen detects `dig-dns` automatically: with it installed and running, opening
+an address navigates straight to its real `http://<storeId>.dig/` page; without it, the same
+address still opens, rendered inside the extension.
+
 ## On Debian-family systems
 
 Prefer the signed, `apt upgrade`-able native path: → [Install on Ubuntu/Debian via apt](./apt.md).
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/support/faq.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/support/faq.md
index 6562b9e..f7dda17 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/support/faq.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/support/faq.md
@@ -25,6 +25,8 @@ Short answers to the questions that come up most. Follow a link to go deep.
 
 A **uniform per-[capsule](../concepts.md#capsule) price**, paid in $DIG at the live rate — the same whether you mint your first one (`init` / first Publish) or ship an update (`commit` / re-Publish) — plus a small XCH transaction fee. A store's lifetime cost is the uniform per-capsule price × the number of capsules. The price is [uniform by design](../digstore/cli/onchain-anchoring.md#why-the-price-is-uniform).
 
+DIG Super Supporters pay **half**: publishing through DIGHUb with a Super Supporter NFT held in your wallet halves the $DIG price shown and charged. DIGHUb checks live ownership across your whole wallet at publish time, so the discount applies only while the NFT is in that wallet — the same live check used for the [handle discount](#can-i-use-my-own-domain) below. Mint a Super Supporter badge (150 $DIG) at [hub.dig.net](https://hub.dig.net) to get one.
+
 ## Can I try it for free?
 
 Yes. **Scaffolding, building, and previewing cost nothing.** You spend DIG only when you publish a capsule on-chain. Start from the [Quickstart](../quickstart.md) — build and preview a draft for free, fund a wallet only at the Publish step.
@@ -61,6 +63,8 @@ Yes — over the **read path**. The moment a capsule confirms on-chain it's read
 
 A store does **not** get a `*.on.dig.net` subdomain automatically. You get one by **registering a handle** for the store in DIGHUb — a paid registration that pins the store to that name. (Your account handle and a store's slug are separate namespaces; they don't auto-expose a subdomain.) DIGHUb also supports custom domains with TLS. Either way, the store is already readable by its URN / `chia://` address without any of this. See [DIGHUb ↗](https://hub.dig.net).
 
+DIG Super Supporters pay **half** for a handle registration. The discount applies only while the Super Supporter NFT is **held in the wallet you're paying from** — DIGHUb checks the live chain across all your wallet's addresses at purchase time. If the NFT is staked, moved, or sold, the discount doesn't apply and DIGHUb shows the full price up front (so the payment is never underfunded). To get the discount, keep the NFT in your wallet when you register.
+
 ## What happens if I lose my seed?
 
 The store stays on-chain and existing content stays readable, but **you can't publish new capsules** to it. Back up `~/.dig/seed.enc` and your mnemonic. See [On-chain anchoring](../digstore/cli/onchain-anchoring.md).
diff --git a/package.json b/package.json
index 934cbdf..7ad2869 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "docs-dig-net",
-  "version": "0.3.10",
+  "version": "0.3.11",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",
diff --git a/static/openrpc-node.json b/static/openrpc-node.json
index 33c73da..db2d5e7 100644
--- a/static/openrpc-node.json
+++ b/static/openrpc-node.json
@@ -2,7 +2,7 @@
   "openrpc": "1.2.6",
   "info": {
     "title": "dig RPC — node profile (local dig-node / in-process DIG Browser)",
-    "version": "0.3.9",
+    "version": "0.3.11",
     "description": "The NODE PROFILE: a distinct, smaller surface than the network profile. Of the byte methods it implements ONLY dig.getContent (local-first, else proxy); everything else proxies upstream or returns -32601. It ADDS node-only methods the security model depends on — chiefly dig.getAnchoredRoot (the CHIP-0035 on-chain head, the trusted root for mandatory root-pinning), dig.stage, and cache.*. Gate on dig.methods rather than assuming one uniform surface. See https://docs.dig.net/docs/protocol/dig-rpc#node-profile.",
     "license": {
       "name": "GPL-2.0",
diff --git a/static/openrpc.json b/static/openrpc.json
index 6b26cb3..e05cda0 100644
--- a/static/openrpc.json
+++ b/static/openrpc.json
@@ -2,7 +2,7 @@
   "openrpc": "1.2.6",
   "info": {
     "title": "dig RPC — DIG Network Content Interface (network profile)",
-    "version": "0.3.9",
+    "version": "0.3.11",
     "description": "The network-wide read interface for DIG content over JSON-RPC 2.0 — the NETWORK PROFILE served by the canonical node at rpc.dig.net. Blind by construction (the node holds no URN and no key), verifiable without trust (merkle inclusion proofs against the chain-anchored root), and streamable at any size. There is no `decoy` field on the wire and no CDN. See https://docs.dig.net/docs/protocol/dig-rpc.",
     "license": {
       "name": "GPL-2.0",