You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Transaction data remains offchain, so internal details such as trades and balances stay confidential.
23
24
Each block is verified on Ethereum using zero-knowledge proofs.
24
-
Chain operators can selectively disclose data to auditors or regulators without exposing the full ledger.
25
+
Chain operators can selectively disclose specific data (for example, bytecode or token supply) to auditors or regulators without exposing the full ledger.
26
+
27
+
**Role-Based Permissioning:**
28
+
Prividium introduces a dynamic permissioning system managed through the **Admin Dashboard**, replacing static YAML files.
29
+
Administrators can:
30
+
31
+
- Add and manage users with Okta or crypto-native (SIWE) authentication
32
+
- Create roles such as *Trader*, *Auditor*, or *Admin*
33
+
- Assign permissions for contracts and functions directly in the UI
34
+
- Configure selective disclosure for public endpoints
35
+
36
+
Access control is enforced by the **Proxy RPC**, which validates user tokens against the **Permissions API** before any on-chain call is executed.
25
37
26
38
**Built-in Compliance:**
27
-
Role-based access controls, single sign-on integration, and support for KYC, KYB, and AML workflows are built in.
28
-
Only authenticated and authorized users can interact with the chain, enabling policy enforcement from day one.
39
+
Single sign-on with Okta, address-level identity binding, and fine-grained access policies are integrated out of the box.
40
+
Only authenticated and authorized users can interact with the network, enabling compliance with KYC, KYB, and AML requirements from day one.
29
41
30
42
**Ethereum Anchoring and Interoperability:**
31
43
Each batch of transactions is finalized on Ethereum using a validity proof, ensuring tamper-proof integrity and trustless settlement.
32
44
Assets and data can move between Ethereum and other public or private ZKsync Chains
33
-
using native zero-knowledge-based bridges without relying on external custodians.
45
+
using native zero-knowledge-based bridges without external custodians.
34
46
35
47
**Scalability and Performance:**
36
-
As a Validium chain, ZKsync Prividium stores state off-chain, enabling high throughput and low transaction costs.
37
-
It supports latency-sensitive use cases like trading and payments without compromising on security.
48
+
As a Validium chain, ZKsync Prividium stores state off-chain, achieving high throughput and low latency.
49
+
It supports trading, payments, and settlement use cases that demand both privacy and speed.
50
+
51
+
---
38
52
39
53
### What Data Is Public
40
54
41
-
Only the state root hashes and zero-knowledge proofs are posted to Ethereum.
42
-
No transaction inputs, addresses, or calldata are visible or inferable from public chain data.
55
+
Only the **state roots**and **zero-knowledge proofs** are posted to Ethereum.
56
+
No transaction inputs, addresses, or calldata are visible or inferable from public data.
43
57
44
-
The only additional public data appears when interacting with non-private chains, such as deposits or withdrawals to Ethereum or other rollups.
45
-
These interactions will be visible on the receiving chain.
58
+
Selective disclosure can optionally expose verified metrics such as total and circulating token supply, or contract bytecode,
59
+
through public read-only endpoints.
46
60
47
-
All other transaction and state data remains inside the private chain database, accessible only to the operator.
61
+
Interactions with public networks such as deposits or withdrawals remain visible on the receiving chain,
62
+
but all other state data is kept private within the Prividium database.
48
63
49
64
To learn more about data availability in the ZK Stack, visit the [Validium page](/zk-stack/customizations/validium).
50
65
66
+
---
67
+
51
68
### How It Works
52
69
53
-
ZKsync Prividium enforces privacy and access control at the API layer, using infrastructure built into the ZK Stack.
70
+
ZKsync Prividium enforces privacy and access control using built-in infrastructure within the ZK Stack.
54
71
55
-
- Access control is configured in a YAML file that defines which users or groups can call specific contracts and methods.
56
-
- Users and applications connect through a Private RPC proxy, which enforces access policies on every request.
57
-
- Authenticated users receive access tokens tied to their role, giving them a filtered view of the chain.
58
-
- Full RPC and explorer access is restricted to chain operators and internal systems.
72
+
- Users authenticate through **Okta SSO** or **Sign-in With Ethereum (SIWE)**.
73
+
- All calls pass through the **Proxy RPC**, which checks the user’s token and permissions against the **Permissions API**.
74
+
- Roles and permissions are defined in the **Admin Dashboard**, not static YAML files.
75
+
- Access is controlled at the contract-function level, with optional restrictions based on function arguments.
76
+
- Auditors and regulators can use **Selective Disclosure** to view approved on-chain data without accessing the private ledger.
77
+
- Full RPC and explorer access remain restricted to chain operators and internal systems.
59
78
60
-
The chain runs as a Validium. It executes transactions privately and stores state off-chain in a secure database.
61
-
Each batch of transactions produces a zero-knowledge proof and a new state root that are submitted to Ethereum.
62
-
This anchors the private chain to Ethereum, ensuring security and finality without exposing sensitive data.
79
+
The chain runs as a Validium. It executes transactions privately and stores its state off-chain in a secure database.
80
+
Each batch of transactions produces a zero-knowledge proof and a new state root submitted to Ethereum.
81
+
This anchors the private chain to Ethereum, ensuring verifiable security and finality without revealing sensitive data.
A built-in role-based framework that manages **users**, **roles**, **permissions**, and **selective disclosure** through the **Admin Dashboard**.
36
+
Administrators define who can read or write to contracts and configure disclosure settings without modifying code or YAML files.
37
+
38
+
-[**Proxy RPC**](/zk-stack/prividium/proxy):
39
+
The secure interface that filters every request based on the policies defined in the Permissioning System.
40
+
It validates user tokens issued via Okta or crypto-native (SIWE) login and enforces role and argument-level restrictions before forwarding to the sequencer.
0 commit comments