diff --git a/Cargo.lock b/Cargo.lock
index a7954da..ba79b7d 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1956,7 +1956,7 @@ dependencies = [
 
 [[package]]
 name = "dig-node-service"
-version = "0.25.0"
+version = "0.25.1"
 dependencies = [
  "axum",
  "base64",
diff --git a/Cargo.toml b/Cargo.toml
index ef96ec3..7cf0885 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -31,7 +31,7 @@ edition = "2021"
 # (`[workspace.package].version`), so it MUST be set here for a release to fire
 # (§3.6). The library crates (dig-node-core/dig-runtime/dig-wallet) keep their own
 # independent versions — only the released binary tracks the workspace version.
-version = "0.25.0"
+version = "0.25.1"
 
 # Release hardening, matching digstore: keep integer-overflow checks ON in release.
 # The node parses untrusted serialized input and does offset/length arithmetic over
diff --git a/README.md b/README.md
index 9304165..ae008cf 100644
--- a/README.md
+++ b/README.md
@@ -381,7 +381,7 @@ USER_JOURNEY.md   the dig-node user/operator/agent journey, surfaces, and ecosys
 
 - **Docs:** [https://docs.dig.net/docs/run-a-node](https://docs.dig.net/docs/run-a-node) — running a
   local `dig-node` (install, configure, point a client at it).
-- **Discord:** [https://discord.gg/dignetwork](https://discord.gg/dignetwork) — questions, help, and
+- **Discord:** [https://discord.gg/v78aygUZt](https://discord.gg/v78aygUZt) — questions, help, and
   the rest of the DIG Network community.
 
 ## License
diff --git a/USER_JOURNEY.md b/USER_JOURNEY.md
index f411cbf..653754e 100644
--- a/USER_JOURNEY.md
+++ b/USER_JOURNEY.md
@@ -185,7 +185,7 @@ every subcommand (machine output to stdout, prose to stderr).
 | **dig-node ↔ DIG Browser (native)** | Same wire contract and cache semantics; `dig-node` is the standalone-service form for users who run the extension in a normal browser rather than the native fork. |
 | **DIG Browser "My Node" controller → dig-node** | The browser drives the `control.*` admin surface over loopback, reading the control token from `<config_dir>/control-token` and sending it as `X-Dig-Control-Token`. The contract (methods/params/results, `x-requires-auth`, error codes) is discoverable via `/openrpc.json` / `rpc.discover`. |
 | **docs.dig.net** | The canonical dig-RPC param/result schemas are published by docs.dig.net; this node's `/openrpc.json` is the local method+error **discovery** surface that aligns with it. Run-a-node docs: [https://docs.dig.net/docs/run-a-node](https://docs.dig.net/docs/run-a-node). |
-| **Discord** | Questions, help, and the DIG Network community: [https://discord.gg/dignetwork](https://discord.gg/dignetwork). |
+| **Discord** | Questions, help, and the DIG Network community: [https://discord.gg/v78aygUZt](https://discord.gg/v78aygUZt). |
 
 See the repo `README.md` for the full configuration table and `SYSTEM.md` (ecosystem root) for the
 shared contracts and interaction map.