ZKsync (@zksync) / X

ZKsync

6,295 posts

ZKsync

@zksync

Incorruptible financial infrastructure: a network of chains secured by cryptography, not validators.

Joined November 2019

Pinned
ZKsync
@zksync
Nov 13, 2025
Institutions want to build on Ethereum and leverage its incorruptibility, hard finality, and global liquidity. But many financial use-cases can’t be run on a chain where everything is public by default. Here’s how Prividium extends Ethereum for enterprises:
00:00
499K
ZKsync
@zksync
4h
If it moves, it's on @grvt_io. (powered by @zksync)
Grvt
@grvt_io
Jun 22
IT'S HERE: You shouldn't need a brokerage, a bank, and three apps to trade the world's markets. ⌲ Stocks, ETFs, whole sectors and regions ⌲ Non-custodial, on-chain, always ⌲ One balance that earns while you trade ⌲ No brokerage, no market hours ⌲ 24/7 access UVXY, STXX,
00:00
18K
ZKsync
@zksync
12h
"This is happening. Data, assets and compliance workflows will all be living in the same onchain network." @gluk64 lays out his vision about the ZKsync Network that will enable assets move across Institutions without exposing their books in his conversation with @joerazz.
00:00
29K
ZKsync
@zksync
14h
ZKsync was proud to participate in @DigitalChamber Fly In and engage directly with policymakers on the need for clear digital asset market structure legislation. The industry’s message to Capitol Hill is clear.
00:00
The Digital Chamber
@DigitalChamber
Jun 23
Replying to @DigitalChamber @SenLummis and 4 others
We wrapped our market structure fly-in meeting with 35+ offices on the hill. Many thanks to all offices, incl. @SenJonHusted & Sen. @JohnBoozman, for helping drive crucial conversations on the Clarity Act, digital asset market structure, and the future of blockchain policy.
30K
ZKsync
@zksync
Jun 23
"Composability with privacy is really hard. On the infrastructure side, we are solving this with our private atomic interoperability between Prividiums". @Ozhar discusses the need for composability in regards to onchain institutional adoption on @therollupco.
00:00
32K
ZKsync
@zksync
Jun 23
Watch the full interview 👇
Why privacy is bringing institutions onchain. Omar Azhar, The Rollup Privacy Day.
From zksync.io
5.3K
ZKsync
@zksync
Jun 23
Identity and privacy are critical issues in the future of an agentic economy. We are very happy to have contributed to the latest @ubyx_ paper that examines the governance, liability and regulatory frameworks that agentic commerce requires.
00:00
38K
ZKsync
@zksync
Jun 23
Read the full report 👇 ubyx.xyz/news/2026-06-2…
5K
ZKsync
@zksync
Jun 23
Institutional adoption depends on blockchains capable of supporting compliance, privacy, scalability, and interoperability requirements. Catch @noah_pravecek discussing the Prividium Difference at @TokenizeThisNYC 📌 Where Should the Privacy Layer Live? 🗓️ June 24 | 10AM EST
00:00
32K
ZKsync
@zksync
Jun 22
This is how Trust Infrastructure in the age of AI looks like. Powered by ZKsync 👇
GenLayer
@GenLayer
Jun 21
1,000,000 decisions onchain And nobody had to intervene once
00:00
33K
ZKsync
@zksync
Jun 22
Replying to @zksync
Delivery and payment settle as one event across two independently governed Zones, proof recorded on @ethereum, with the trade kept private and no mutual trust required. That is private atomic DvP on Prividium. Learn more 👇
Prividium® | ZKsync
From zksync.io
10K
ZKsync
@zksync
Jun 22
Replying to @zksync
7/ Expiration, Assets Unlocked Every flow has a deadline. If: • one side never locks, or • verification fails in time → the flow expires. Each Zone reads expired state from @ethereum and unlocks its assets. No loss. No partial settlement. Fully safe abort.
00:00
10K
ZKsync
@zksync
Jun 22
Replying to @zksync
6/ Executed & Finalized Once verified: • Zone A receives Y • Zone B receives X Both sides execute their legs atomically, and finality is recorded on @ethereum.
00:00
5.3K
ZKsync
@zksync
Jun 22
Replying to @zksync
5/ Mutual Trustless Verification Each Zone independently reads the Flow ID dan IMT root on @ethereum. Verification is done against Ethereum’s canonical state, not each other or the coordinator. No mutual trust required.
00:00
4K
ZKsync
@zksync
Jun 22
Replying to @zksync
4/ Link & Confirm Commits Locks are linked back to the agreement spec. If hashes match the Flow ID → agreement is confirmed. This becomes the finality signal: both locks exist, verified, and matched.
00:00
3.9K