docs(security): add TEE-isolated relayer as a community high-assurance option#155
Open
Ashwin-3cS wants to merge 1 commit into
Open
docs(security): add TEE-isolated relayer as a community high-assurance option#155Ashwin-3cS wants to merge 1 commit into
Ashwin-3cS wants to merge 1 commit into
Conversation
…e option Extends the "Mitigating relayer trust" section with a fourth deployment mode: running the relayer inside a Nitro Enclave (via the community nautilus-memwal-relayer template). This is positioned as an optional high-assurance path for operators who self-host the relayer and want to prove to their end users that it is behaving exactly as the attested image specifies. Existing managed / self-hosted / manual options are unchanged and remain the recommended defaults.
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
1 participant
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.
Summary
Adds a short mention of the community-contributed
nautilus-memwal-relayerto the existing Trust & Security Model doc (docs/fundamentals/architecture/data-flow-security-model.md) as an optional high-assurance deployment mode. No changes to recommended defaults; no new pages.Scope of change
One file. Adds:
The framing positions this as the path for operators self-hosting the relayer who want to prove to their end users that the relayer is behaving exactly as the attested image specifies — without changing the recommended defaults or shipping new product surface in MemWal itself.
Notes
The relayer repo itself is already in sync with MemWal
dev(apalis-backed wallet jobs, latestagent_idmetadata, SDK v0.3 signing). This PR is docs-only and does not introduce any new dependency on the community repo from inside MemWal.