Chain profile
Permissioned
Prividium (Cari Network ZK substrate).
Abstract. Cari Network LLC (consortium operator) · Matter Labs (ZKsync core)
Facts
Chain identity at a glance.
- Type
L2-zk
- Native settlement
- Tokenized DDA tokens (per-bank, e.g., HUNT-DDA, KEY-DDA, MTB-DDA — VERIFY exact token symbols)
- Account model
- Bank-issued DDA token (1:1 demand deposit; FDIC follows the deposit; token is a ledger representation, not a separate liability)
Important — verify before relying
Show our work.
This profile carries inline VERIFY markers on
every field whose value depends on the model's recollection
rather than independent primary-source confirmation.
Renderers and compliance officers MUST verify each claim
against the operator's primary documentation before any
client-facing reliance.
Full discipline header — including sources,
architectural-distinctness narrative, and per-field VERIFY
inventory — at compliance/registries/chains/prividium.ts.
Vendor stack · L5 → L1
The 5-layer Stable Stack.
Each row is one named vendor slot from the chain's vendorStack. Solid markers are code-enforced
(the chain blocks or signs); dashed markers are
policy-enforced (the chain flags, humans or systems act on
the signal).
L5 → L1 — application down to network
L5 · Application
consortium-app
Cari Network multi-bank application — DDA mint/burn, interbank transfer, commercial payment, liquidity sweep, stablecoin bridge
C1C8C9C13 ◇ policy-enforced
bank-treasury-system
Member-bank core banking systems (Fiserv DNA · FIS IBS · Jack Henry SilverLake patterns)
C8C9 ◇ policy-enforced
L4 · Account
account
Bank-issued DDA token (1:1 with underlying demand deposit account; FDIC-insured up to limits)
C1C9 ◆ code-enforced
validator-node
Per-bank Prividium validator node (each member bank operates its own sub-ledger and validator)
C1C8 ◇ policy-enforced
custody
Member-bank treasury custody (the deposit itself remains on the bank's balance sheet — token is a ledger representation)
C1 ◇ policy-enforced
L3 · Execution
smart-contract
Cari Network deposit-token smart contracts (mint · burn · transfer · authorization gate per bank policy)
C13C16 ◆ code-enforced
zk-proof
ZK-balance-proof system — proves balance + authorization without revealing customer identity
C13C16 ◆ code-enforced
transfer-restriction
Per-bank policy contracts (KYC inheritance from issuing-bank's master register; allowlist enforced per consortium charter)
C1C16 ◆ code-enforced
L2 · Consensus
consensus
BFT consensus among member-bank validator nodes
C10 ◆ code-enforced
zk-prover
ZKsync prover infrastructure (Matter Labs prover)
C10 ◆ code-enforced
L1 · Network
network
Prividium network — ZK proofs settle to Ethereum L1 for finality anchoring
◆ code-enforced
Fig. 1 —
Vendor slot per layer; solid border = code-enforced, dashed
border = policy-enforced.
Bridges supported
Cross-chain transport surface.
- Cari → CCTP → Circle USDC (C6 path · regime-crossing bridge to GENIUS-Act stablecoin perimeter)
Related paths
Paths that route through Prividium (Cari Network ZK substrate).
Compliance paths whose settlementChains
include prividium or whose steps execute
on this chain.
Source
Where the truth lives.
compliance/registries/chains/prividium.ts —
full discipline header, sources, and per-field VERIFY
inventory live in the chain-profile source file. See the path resolver to see
this chain in a resolved compliance journey.
Explore the architecture
Pick a thread.