Matter Labs, the developer behind ZKsync, launched Prividium Connect on Nov. 10, saying the software enables institutions to privately exchange assets across separate blockchains without a trusted intermediary.
The company also proposed directing interoperability fees from canonical public deployments to ZK through the existing Fee Flow system. Activation, integration and fee parameters still require governance approval, distinguishing the product launch from the proposed token economics.
Matter Labs says Connect has reached mainnet, initially supporting Hyperledger Besu and Prividium Ledger. Each institution runs a connector alongside its existing blockchain. Participants select Ethereum or another Ethereum-compatible settlement chain, including a private chain, where the outcome becomes final.
Connect makes exchanges atomic: either both transfers complete or neither does. Zero-knowledge proofs show that the agreed terms were met without revealing the underlying records. In a securities trade, for example, delivery and payment depend on each other, preventing one party from delivering without being paid, according to Matter Labs.
If an exchange misses its deadline, each party can recover its committed assets without the other party's cooperation, the company says. Neither party can unilaterally reverse an exchange once it is complete. Atomic does not mean instant: the product page says completion still depends on proof verification and the finality of the selected settlement layer.
The page directs institutions to an evaluation, with supported configurations confirmed for each implementation.
A Proposed Route From Fees to ZK
Connect integrates with Prividium Commander, though the products can operate independently. Introduced in October, Commander manages institutions' digital-asset operations. At its launch, CEO Alex Gluchowski told The Defiant that Commander revenue went to Matter Labs, not ZKsync tokenholders. The new plan concerns interoperability fees from canonical public Connect deployments.
“The fee switch is built and being audited,” ZKsync said in its announcement thread. The linked GitHub change describes a switch that is initially off and, when enabled, charges chain operators for each interoperability call. It leaves the forwarder that would send fees to Fee Flow for separate work.
Loading post from X…
View post on XUnder the existing Fee Flow design, anyone can claim accumulated, approved fee assets by paying a governance-set amount of ZK. The ZK then goes to a splitter for burning or distribution according to governance-set parameters. Matter Labs says the Fee Flow contracts are already deployed on ZKsync Era; connecting the proposed fees to them remains subject to approval.
Institutions can also run Connect themselves or choose a provider. The proposed fee route applies specifically to canonical public deployments; it does not commit to directing all Prividium software revenue into ZK.
Source: thedefiant.io. Adapted by NBTC.
Add A Comment
Comments are closed.