GATEWAY
Sign inDiscuss your architecture
Open Privacy Suite

Open Privacy Suite.

Identity-aware policy, selective disclosure and audit evidence for configured EVM RPC and explorer surfaces—using standard JSON-RPC.

Book an Open Privacy Suite demoReview the architecture
Standard JSON-RPC control boundary
Institutional EVM environment
Application · wallet · serviceAuthenticated request
Open Privacy SuiteAuthenticate · evaluate · shape
Full viewConsistent pseudonymRedacted view
Why Open Privacy Suite exists

Regulated onchain finance cannot assume universal transparency.

A shared ledger can preserve a common record without giving every participant the same view of every transaction, position or customer.

The default public model returns the same network-visible state to each reader. Gateway's institutional model evaluates an authenticated request and returns a role- and purpose-bound view.
Default public model

Network access reveals the same state.

A public RPC query returns the chain-visible record without a role-specific view at the ledger layer.

01 · QueryNetwork reader
02 · Access basisPublic RPC endpoint
03 · Delivered state
Participant A0x71a4…b09c
Participant B0x71a4…b09c
Observer0x71a4…b09c
Visibility basis
Network reach
Delivered view
Same chain-visible fields
Gateway institutional model

Policy determines the authorised view.

The same ledger can serve different views according to authenticated identity, role, purpose and grant.

01 · QueryAuthenticated principal
02 · Policy boundaryIdentity · role · purpose
03 · Authorised result
Permitted role0x71a4…b09c
Scoped roleparty-027
Unauthorised roleredacted
Visibility basis
Identity · role · purpose
Delivered view
Full · pseudonym · redacted
JSON-RPC enforcement

Intercept the request before it reaches the node.

Open Privacy Suite is designed as a standard JSON-RPC proxy between authenticated applications and an EVM endpoint. It evaluates supported calls, shapes the returned view and records the decision without relying on a proprietary node protocol.

An authenticated application sends standard JSON-RPC through the Open Privacy Suite proxy. The proxy intercepts, evaluates, filters or redacts the request and response before contacting a compatible EVM client.
Private-network modePermissioned EVM · direct RBAC pattern
Public-network modePublic EVM · proof / bridge pattern
01 · CallerApplication · wallet · servicePrincipal and intended purpose
Open Privacy Suite proxy
  1. 01Authenticate
  2. 02Resolve role + purpose
  3. 03Evaluate method + resource
  4. 04Filter or redact
03 · EndpointCompatible EVM clientNo proprietary node protocol required
Response returns through the same decision pathApproved dataConsistent pseudonymRedaction or opaque denial
Standard-interface client and stack patterns
GethErigon / cdk-erigonRethBesuNethermindLineth stack
Confirm client, method, batch, multicall and trace coverage for the target deployment.
Policy model

Narrow permissions. Approve disclosure. Keep the view consistent.

Roles inherit a bounded scope; disclosure changes the delivered view for a defined recipient and time window. The same outcome can shape RPC responses and a privacy-aware explorer.

02 · Permission + disclosure model

Authority narrows. Disclosure expires.

Principals inherit a bounded grant; resource rules define exactly what that grant can reach.

Principal hierarchyEach level can narrow its parent
  1. 01
    OrganisationMaximum delegated scope
  2. 02
    GroupNarrower operating role
  3. 03
    User · app · agentEffective permission
Resource depthRules become more specific
  1. 01
    ContractRead · write · administer
  2. 02
    Function selectorSpecific callable method
  3. 03
    Parameter constraintAllowed argument or range
Selective disclosure outcomePer address or configured resource
Full0x71a4…b09cApproved value
Pseudonymparty-027Consistent alias
Redacted••••••••Value withheld
  1. 01Request + purpose
  2. 02Recipient approves or rejects
  3. 03Grant active until deadline
  4. 04Expiry or revocation

Self-service grants may narrow effective access; they do not expand it.

03 · Consistent view + evidence

One decision shapes each configured surface.

The same disclosure outcome can be carried from the proxy into a privacy-aware explorer.

Policy outcomePseudonymparty-027
RPC responseparty-027
Privacy-aware explorerparty-027
Access decisionDisclosure grantExpiry / revocation
PreviousH(n−1)
CurrentH(n)
NextH(n+1)
Configured forwardingSIEM / webhook

Consistency applies to configured OPS proxy and explorer surfaces. Raw node, administrator and connected-system access remain separate deployment controls.

Core capabilities

Six capabilities. One policy boundary.

Participant eligibility, delivered views, disclosure workflows and evidence work from one coordinated policy model.

01

Privacy zones

Define configured participant and data boundaries for private-network or public-network patterns.

02

Identity-aware permissions

Cascade scope from organisation to group to user, application or agent—with restrictive inheritance.

03

Policy enforcement

Evaluate supported RPC methods down to contract, function-selector and parameter constraints.

04

Selective disclosure

Return a full value, consistent pseudonym or redaction through an approved, time-bounded grant.

05

Private explorer

Apply the configured visibility outcome consistently across RPC responses and explorer views.

06

Audit and evidence

Link in-scope decisions in a tamper-evident hashchain and forward configured events to a SIEM.

Deployment contexts

Add controlled visibility where the financial product operates.

Define the enforcement points, identity sources and delivered views for the target environment.

  1. 01Existing EVM environment
  2. 02Sovereign network
  3. 03Institutional L2
  4. 04Payments or stablecoin environment
  5. 05Tokenized-asset environment
Platform context

A flagship control product inside Gateway Platform.

Open Privacy Suite is Gateway-owned technology. Institutional systems and approved specialist providers remain outside the Platform boundary and connect through defined interfaces.

Open Privacy Suite is a Gateway-owned privacy and controls product inside Gateway Platform. Institutional systems connect at defined interfaces, while specialist providers remain outside the Platform boundary.
Institutional systemsApplications · IAM · SIEM
Gateway-owned technology boundaryGateway Platform
Managed environmentsInteroperabilityOpen Privacy SuiteFinancial-product infrastructureProduction operations
Outside the Platform boundaryIdentity · assurance · other selected providers
Technical context and deployment notes

Technology touchpoints

These names provide architecture context only. Any integration, relationship, availability or production claim requires confirmation for the deployment.

Microsoft Azure / Entra IDPrivado IDGeth · Erigon · Reth · Besu · Nethermind · Lineth stackSIEM / observability interfaces

Enforcement boundary

Open Privacy Suite governs configured application, explorer, reporting and RPC enforcement points. Raw node, infrastructure-administrator and integrated-system access remain separate deployment controls.

Review Gateway’s control methodology →
Scope Open Privacy Suite

Define who needs to see what, and why.

Bring the roles, systems and disclosure requirement. We will map the candidate control boundary.

Book an Open Privacy Suite demo Explore Gateway Platform