Sarah (Schwartz.lens)
@schwartzswartz
Followers
3K
Following
15K
Media
38
Statuses
1K
Building web3 things | Dev Rel @zksync | prev @fuel_network
Denver, CO
Joined December 2015
Seriously though we need more ZK in sci fi.
There were so many movies & books about AI before it ever existed ⏭️ everyone hyped to build with AI today. 👉 We need to put ZK into the culture
0
0
1
ZK is the endgame fr though
🤯 two 5090s now prove every L1 EVM block 🤯 The @zksync Airbender team pulled off something insane ahead of tomorrow's https://t.co/ihbHrH45FM demo. Mainnet proofs on two gaming GPUs. One box, ~1kW—basically a toaster. Props to @robik, Michael Carrili, @MarcinM02, @Shamatar.
0
1
24
happening now! come join the space where we are talking about the future of institutional privacy onchain via @zksync
0
2
15
ooo this is gonna be interesting
@wormhole @Aptos @BTC_OS @StellarOrg @FlareNetworks @PythNetwork @SUPRA_Labs @WalrusProtocol @auroraisnear @HathorNetwork @0G_labs @0xProject @arbitrum @boundless_xyz @lifiprotocol @Pi_Squared_Pi2 @ComposeNetwork @ssv_network @DINBuild @flipsidecrypto @NexusLabs @avax @Calyxdotxyz @MantaNetwork @nreach_io @VOIDappsxyz @therollupco @AmMuroch @liesleichholz @robbie_rollup @danreecer_ @Supermooncamp @vargs_g @RosuGrigore @e_obukhova @DanTheMan8300 @tomerweller @JonEvansJones @AptosLabs @rrigoni @societalruin @Jemorla @KemarTiti @beefyfinance @Stacks Join us at Multichain Day | Devconnect 2025 for a Panel Discussion on Multichain Interop: Coordination, Messaging, and Liquidity Flow! Featuring: ✔️ @wormhole ✔️ @LucidLabsFi ✔️ @offchain ✔️ @zksync ✔️ @therollupco RSVP: https://t.co/eBmOcjdRw6
0
1
4
You can also check out my tutorial for building a crosschain defi app using interop messages:
code.zksync.io
Learn how to send and verify an interop message from any ZKsync chain.
0
0
1
For a full guide for sending and verifying interop messages, check out the interop messages guide in the ZKsync docs.
docs.zksync.io
A guide for sending and verifying interop messages with ZKsync Connect.
1
0
2
Limitations for this first stage of interop include: 🚫 No support for selecting destination chains 🚫 Lack of replay protection 🚫 No cancellation mechanism 🚫 No support for sending assets or calling contracts These limitations will be addressed in phases 2 and 3.
1
0
2
One example use case for interop messaging would be to unlock experiences on a chain based on activities on another chain. You can see this working in my demo: https://t.co/qQPGr3g2c6
2026 prediction: multichain / crosschain apps will be everywhere. I built one using ZKsync's first version of interop: stake on one chain, get rewards on another. Full tutorial below 👇
2
1
1
After the interop root is updated on other ZKsync chains via the L2InteropRootStorage contract, the message can be verified using the proveL2MessageInclusionShared method in the L2 message verification contract deployed at 0x0..10009 on each ZKsync chain.
1
0
3
Once the message is sent and the batch of the tx is executed, ZKsync Gateway’s MessageRoot contract emits an event indicating that a new interop root was generated. The MessageRoot contract collects messages from different chains and aggregates them into a single Merkle tree.
1
0
3
To send a message, you can call the sendToL1 function on the L1Messenger contract, which is pre-deployed on every ZKsync chain at address 0x0..8008. The function name was kept from previous versions, but it does not restrict messages from only being verified on the L1.
1
0
3
These messages are the foundation to unlock more complex crosschain activities in the future, like bridging assets and interacting with contracts across different chains.
1
0
3
The message itself has no destination chain or address. It’s simply a payload created by a user or contract that gets broadcast. There is no expiration for when messages can be verified. They remain verifiable indefinitely.
1
0
2
An interop message consists of arbitrary data and has two simple properties: ➡️ Anyone can send a message. ➡️ Anyone can verify that a given message was successfully sent on some chain.
1
0
4
Early next year ZKsync is going to launch phase 2 of universal interop for ZKsync chains. Phase 1 (interop messages) is already live. To recap how phase 1 works, I made these diagrams showing the full lifecycle of sending and verifying interop messages:
5
10
72
👀👂✍️
SATURDAY NOV 22ND: Ethproofs day is thrilled to host @portport255 from @zksync (MatterLabs / Airbender) who will be presenting: "zkSync Airbender: Fullstack zkVM Customizations"
0
1
3
I did another quick test - finalization time is currently under 4 minutes 💀. That's > 4x faster than other rollups
ZKsync Atlas testnet transactions are literally ZK proved, verified, and finalized on Sepolia in less than 7 minutes 🤯
4
5
54
The best explainer thread yet on private ZK chains
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:
3
1
38
“A corporation simply can’t move their transactions on a public chain. This is where Prividiums come to play enabling enterprises to have privacy, access controls & selective disclosures” @Ozhar, on the @therollupco, explaining why Prividiums are purpose-built for institutions.
2
2
27
If you're interested in web3 privacy, I highly recommend reading this
Read the full blogpost 👇 https://t.co/IFr7YD4JgW
1
1
16