feat(vendor): add Gateway Open Privacy Suite - #189
Open
mandrigin wants to merge 2 commits into
Open
Conversation
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.
Adding a Vendor/Protocol
Protocol Name: Open Privacy Suite
Company: Gateway.fm
Brief Description:
Adds a vendor card for the Open Privacy Suite access and disclosure layer. It covers private EVM deployments, including permissioned Besu networks, as well as Gateway private L2 and validium compositions, with the Reth-specific encrypted-state add-on documented separately from baseline OPS guarantees.
Documentation Link: https://gateway-fm.github.io/open-privacy-suite/
Status: testnet
Checklist
Additional Notes
The card maps the deployment to existing EthSystems patterns and states the access-layer trust boundary explicitly: an unmanaged raw node or indexer bypasses OPS filtering.