zkSync SDKs in five languages
Integrators connect through SDKs our team built and maintained. zkSync documentation credits Vareger as the SDK author.
Stack and topics
| Industry | Blockchain infrastructure |
|---|---|
| Region | Global |
Context
The client and the problem
zkSync is a scaling and privacy engine for Ethereum: low-fee transfers of ETH and ERC-20 tokens, atomic swaps, limit orders and native layer 2 NFTs. A network like this only grows if exchanges, wallets and apps can integrate it quickly, and they integrate in the language their own stack already uses.
zkSync needed one team to own the libraries its integrators depend on, keep them in step with the protocol, and help integrators when something did not work.
What we built
What did we build?
We took responsibility for the whole set of SDK libraries zkSync offers its customers and integrators.
- SDKs in five languages. Go, Python, Rust, Android and iOS libraries, built and maintained by our team, plus a Dart SDK. zkSync documentation lists Vareger as the SDK author.
- Protocol features. Later work added EIP-712 typed signatures and deterministic contract deployments, and migrated the test suites across frameworks.
- Integration support. Our engineers advised zkSync customers on integration approaches and resolved their issues, so the network's core team did not have to.
How we worked
Team and process
This was a partnership rather than a fixed project. Each library had to follow the protocol as it changed, keep the same behaviour across languages and stay usable by teams who had never touched zero-knowledge rollups before.
We kept the libraries consistent with each other, tested them against the network and answered integrator questions directly.
Facts
Project facts
| Fact | Detail |
|---|---|
| Client | zkSync, Ethereum layer 2 network |
| Our role | Owner of the SDK libraries for integrators, integration support |
| Languages | Go, Python, Rust, Android, iOS, Dart |
| Topics | Ethereum layer 2, zero-knowledge rollup, EIP-712, deterministic deployments |
| Public proof | zkSync documentation credits Vareger as SDK author |
Result
Where it stands
Integrators connect to zkSync through SDKs our team built and maintained. The same work is the base of our zero-knowledge practice: SDKs, on-chain verifiers and threshold proofs.
Next step
Building something similar?
A 30 minute call with Oleg. You leave with a clear view of scope, risks and the next step.
Oleg Pun
CEO, Vareger
