Skip to content

fix(dig-node): correct Discord invite (imposter link -> official) #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MichaelTaylor3d merged 1 commit into from
Jul 12, 2026
Merged

fix(dig-node): correct Discord invite (imposter link -> official) #30

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion USER_JOURNEY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Loading