Add a Verified TEE mode toggle to the Nexus provider - #47
Open
Marketen wants to merge 2 commits into
Open
Conversation
Nexus also runs a Gateway inside a trusted execution environment, reachable through the Nexus Local Proxy package. Hermes could already be pointed at it by hand-editing the base URL, which meant nobody did. The toggle switches OPENAI_BASE_URL between the standard Nexus API and the local proxy. That is the whole change: Hermes speaks plain OpenAI HTTP either way and never implements attestation itself. The proxy is the only thing on the node that verifies the enclave and encrypts prompt bodies to it, so pointing at it is all that is required, and there is no second implementation of security-critical code to keep in step. Enabling it probes the proxy rather than assuming it is there. The probe reads the proxy's own verification state instead of attesting anything here, and reports what was checked and which Gateway release is running, so the user can see the claim rather than take the toggle's word for it. A node without the package installed is told to install it; a proxy that is running but has not verified says so, because it will not carry prompts in that state. The probe also pulls the Gateway's model catalog through the proxy, so the model field offers real IDs instead of asking the user to copy one from a web page. The toggle is restored from the saved base URL, so reopening the wizard does not silently turn it back off. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: e20dba4 This is a development version and should only be installed for testing purposes.
Hash: (by dappnodebot/build-action) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Verified TEE mode toggle to the Nexus provider in the setup wizard. It switches
OPENAI_BASE_URLbetween:https://nexus-api.dappnode.com/v1http://nexus-local-proxy.dappnode.private:3301/v1Nexus runs a Gateway inside a trusted execution environment, reachable through the Nexus Local Proxy package. Hermes could already be pointed at it by hand-editing the base URL — which meant nobody did.
Why it's only a base-URL switch
The local proxy is the only thing on a DAppNode that verifies the Gateway's enclave attestation and encrypts prompt bodies to it. Hermes speaks plain OpenAI HTTP either way and never implements attestation itself, so there's no second copy of security-critical code to keep in step.
The probe
Enabling the toggle probes the proxy rather than assuming it's there. It reads the proxy's own verification state rather than attesting anything in Hermes — one verifier on the node, everything else reads its answer.
Three outcomes, all tested against a live proxy pointed at production:
It also pulls the Gateway's model catalog through the proxy, so the model field offers real IDs instead of asking the user to copy one from a web page.
Testing
Ran the wizard server against a real Nexus Local Proxy container verifying live production:
{ "reachable": true, "verified": true, "status": "verified", "gateway": "https://nexus-api-tee.dappnode.com", "sourceRevision": "893f4c9f306707b83f3b41782f25eb05adbc4f30", "checks": 9, "models": 15 }With the proxy stopped:
{ "reachable": false, "verified": false, "reason": "not installed or not running" }Both files syntax-checked (
node --checkand avm.Scriptparse of the inline block).Notes
dappnode/dappnode/SKILL.mddocuments the mode so the agent can explain it.🤖 Generated with Claude Code