Danil Lugovskoy ∎

Blockchain/Backend python developer

[ALEX | ZK @gluk64]

Open source will win the market for strategic financial infrastructure. That is why we are open-sourcing the core of Prividium today. The German Central Bank 🇩🇪 is the first institution to deploy it independently in its own environment.

Sovereignty begins with the freedom to leave

Putting software in an institution’s own data center gives it physical custody, but that alone is not sovereignty. If the institution still depends on the vendor to maintain and evolve the system, it holds the hardware while the vendor controls the future. The real test is simple: can the institution keep operating after the relationship ends?

Making the code public makes the right to leave real. A contract can promise continuity; public code lets the institution secure it for itself. The institution can replace the vendor without replacing the system.

Institutions must control their own rules

A permissioning engine determines who can enter a financial system and what each participant can do. These are the institution’s policies expressed in software. When the vendor controls that software, the institution depends on the vendor to enforce and change its own rules.

Opening the Prividium permissioning engine places those rules under the institution’s control. It can inspect the logic, change it and run the complete core independently. Sovereignty now extends from the infrastructure to the policies that govern every participant inside it.

Open infrastructure will win

Open-weight AI is already winning deployments it loses on benchmarks. Some institutions prefer a model they can run and adapt to a more capable model available only through a supplier. Model rankings change every few months; the ability to operate independently survives the ranking.

A closed financial platform can grow only as far as institutions are willing to accept its owner as a permanent dependency. Open source removes that ceiling. Institutions can adopt the same infrastructure without tying their continued operation to the same company. Institutions that would never agree on a vendor can still converge on an open standard, bringing more of the financial system onto ZKsync.

[frogmonkee @frogmonkee]

Yall are goofy

[ZKsync @zksync]

ZK is the Endgame

[Danil Lugovskoy ∎ @deniallugo]

@getclave ApplePay with cryptocurrency, I've been waiting forever for this feature

[ZKsync @zksync]

Squad up 🫡

L1 network @cronosapp, supported by https://t.co/iGxwPhTk3O, is embracing ZK Stack and joining the zkSync hyperchain network on Ethereum! With more than $350M in DeFi TVL, today’s launch of Cronos zkEVM testnet is a significant scalability milestone in advancing their mission for the mass adoption of crypto.

∎ Access to the Ethereum ecosystem ∎

Building a hyperchain with ZK Stack enables Cronos to gain secure, fast, and cost-effective access to the Ethereum ecosystem’s dapps and users.

∎ Free flow of users & liquidity ∎

Hyperchains are seamlessly interconnected via hyperbridges, which allow Cronos to natively exchange information and transfer value between different hyperchains, while tapping into the users and liquidity of the entire hyperchain ecosystem.

∎ Freedom through customizability ∎

Leveraging ZK Stack, Cronos retains unrestricted rights to the code as well as the autonomy to customize and shape every aspect of its chain –– for instance, modifying the chain’s native gas token to be the CRO token.

∎ Don’t FOMO — Learn about ZK Stack ∎

To easily launch your own sovereign ZK Stack hyperchain or learn about how your team can build with ZK Stack, head to https://t.co/CBY79asDHp or reach out at [email protected].

[Anthony Rose @anthonykrose]

There might be more to say about this tomorrow, but for today I think @gluk64's comments also express how I feel.

[ALEX | ZK @gluk64]

Every decision we make as a team towards building @zksync is driven by our ethos, which is based on integrity and transparency. We have made honest mistakes in the past, but we always did our best to openly acknowledge them and take responsibility. And will always do so in the future.

However, today’s accusations are unfounded, misleading, and extremely disappointing coming from a team I highly respect.

The reader of the Polygon Zero post is left with the impression that Boojum is largely using Plonky2 code with little innovation, and that we allegedly re-used this code without providing any attribution to the original work. These claims could not be further from truth.

I really want to believe in the good intentions of the Polygon Zero team (which I highly respect for their excellent work). I am deeply passionate about the mission of @zksync and the amazing work our team is doing, and I’m sure the same applies to the authors of the post and their work. Alas, passion can at times lead to rushed arguments and inaccurate statements.

So I’m going to share pure facts here and let the reader come to their own conclusions. Here is what you need to know:

• Both Plonky2 and Boojum are implementations of the RedShift construction (PLONK + FRI).

• RedShift (1) was introduced by @the_matter_labs team 3 years before Plonky2 paper. (2)

• Plonky2 team never gave us credit (although they refered to RedShift in their paper). We never bothered. It’s great to see someone improving on your work!

• Only ~5% of the Boojum code is based on the code of Plonky2.

• For the reused code, a clear attribution is provided in line #1 of the main file of the module. (3)

• The rest of the files are provided as they are. If they contained more information about the authors, we would obviously have copied that.

• In addition, the README file contains an acknowledgement to Plonky2. (4)

• In addition, the intro post contains an attribution to Plonky2, with specific names of the authors. (5)

We could have done it better. The community rightfully pointed out that there is a more standard approach to attributions, which we will wholeheartedly apply from now on.

Open Source is all about genuine cooperation. If the Polygon Zero team wanted additional credit, the easiest way would have been to submit a pull request which we would have happily accepted. Going ahead with public accusations of a complete lack of attribution (even if it was true, which is not the case here) is anything but the spirit of the Open Source movement. If you’re not happy about others – including potential competitors – using parts of your code, maybe Open Source is not for you?

Now, the part that I am most surprised about is complaints about benchmarking.

The whole point of neutral 3rd party benchmarks is to compare apples to apples, going beyond marketing noise and nuances of implementation. If you are unhappy with the choice of the benchmarking function (SHA256) or your implementations being unoptimized, why put your code out for benchmarking in the first place and then endorse it? (6) (7)

If someone can take 5% of the Boojum code and make it 10x faster, not only will we consider this a breakthrough work and immediately hire this person, – @shamatar will name one of his cats in their honor.

We all stand on the shoulders of giants. Boojum is built leveraging the work of the brightest minds contributing to the field of cryptography. And we fully agree with the Polygon Zero team: “We can sustainably build software in the open, leveraging the combined talent and expertise of entire communities, and everyone benefits.” This is why Boojum was open-sourced under a free permissive license the moment it was released to the public, just like ZK Stack, and like every other software component we will ever create for @zksync. Each of them is a small step on the long journey to scale Ethereum along with its values.

(1) https://t.co/fMHBxZvras

(2) https://t.co/OCOzO7cz0T

(3) https://t.co/dgf8TykbhQ

(4) https://t.co/XWfmXyhyLU

(5) https://t.co/Zqee5bmbwN

(6) https://t.co/49ngijVdas

(7) https://t.co/ZFyIWqZQEg

[Multichain (Previously Anyswap) @MultichainOrg]

1. On May 21, 2023, Multichain CEO Zhaojun was taken away by the Chinese police from his home and has been out of contact with the global Multichain team ever since. The team contacted the MPC node operators and learned that their operational access keys to MPC node servers had been revoked. Furthermore, these MPC node servers, like all other ordinary servers, were actually running under Zhaojun's personal cloud server account. No member of the team has access to Zhaojun's personal cloud server account, so nobody can log on to these MPC servers.

2. Later, the team established contact with Zhaojun's family and learned that all of Zhaojun's computers, phones, hardware wallets, and mnemonic phrases were confiscated by the authorities. Since the inception of the project, all operational funds and investments from investors have been under Zhaojun's control. This also means that all the team's funds and access to the servers are with Zhaojun and the police.

3. Due to the lack of information about the case, the team could only maintain project operations to the best of their abilities through the remaining access on some non-MPC servers that hadn't been revoked yet. Per the lawyer's suggestions, the team has chosen to cooperate as much as possible with the demands of Zhaojun's family and adhere to the requirements of local laws and regulations, refraining from disclosing unauthorized information about the case to the public.

4. On May 30, in a responsible approach toward the community, the team released the news about Zhaojun's disappearance and informed the community about the technical issues currently faced.

5. On June 4, Zhaojun's family successfully logged into the cloud server platform using the historical information on his home computer. However, Zhaojun's family only allowed Multichain team engineers physical access to the home computer to fix technical issues with Router2 and Router5.

6. During this period, Zhaojun's family and the lawyer were in communication with the police. The team was not informed about the details of the case but was notified that Zhaojun would be released soon and was asked to continue maintaining the system and await further updates.

7. The Multichain protocol continued to operate as designed. The team made every effort with limited resources to sustain the operation of the Multichain protocol and resolve user issues as much as possible.

8. On July 7, user assets locked on the MPC addresses were transferred to unknown addresses abnormally. According to Zhaojun's sister, login information from an IP address in Kunming was found on the cloud server platform, along with a series of operations transferring funds from the MPC addresses.

9. On July 9, Zhaojun's sister transferred the remaining user assets in the router pool and subsequently notified the team and several project parties of this asset preservation action. The funds were transferred to EOA addresses controlled by Zhaojun's sister.
0x1eed63efba5f81d95bfe37d82c8e736b974f477b
0x6b6314f4f07c974600d872182dcde092c480e57b

10. On July 13, according to information provided by Zhaojun's family, the police took Zhaojun's sister into custody. Now, Zhaojun's sister is also out of contact. The status of the assets she has preserved is uncertain, so the team believes it is necessary to inform the community about all the known circumstances.

11. Due to the lack of alternative sources of information and corresponding operational funds, the team is forced to cease operations. If there are any further notifications and developments, the team will update the community accordingly.

12. The Multichain team does not have the access to Domain Account to redirect or bring down the frontend https://t.co/v2pWSycJ0k. Please help amplify and ask users not to use the Multichain service anymore.
Can @GoDaddy help to bring down https://t.co/v2pWSycJ0k? Thanks.

[ZKsync @zksync]

Sharing the first draft of The ZK Credo — a declaration of the foundational principles for the emerging ZK-powered Internet of Value.

v1 is now live on GitHub for community discussion and feedback from the Credo's rightful owner: You!

👇 1/6

https://t.co/BdEH5pecC6

[ZKsync @zksync]

THIS TWITTER ACCOUNT IS COMPROMISED!

Do not trust it until confirmed by @the_matter_labs and @gluk64

@TwitterSupport, @elonmusk please respond to support requests!

[Danil Lugovskoy ∎ @deniallugo]

@ArtyShatilov wen token

[Danil Lugovskoy ∎ @deniallugo]

@samrags_ О круто!!

[Danil Lugovskoy ∎ @deniallugo]

@zksync, @the_matter_labs’s zkRollup for trustless, scalable payments is now live on Ethereum mainnet!

Give it a try: 👉👉 https://t.co/BirK6dmRE3

Claiming my trial tokens: 0xf29368c967e8d8de18a9857c0b7bcf92b56c070b05b75ac31ad3975d9ee1a3c3

[Danil Lugovskoy ∎ @deniallugo]

@zksync, @the_matter_labs’s zkRollup for trustless, scalable payments is now live on Ethereum mainnet!

Give it a try: 👉👉 https://t.co/BirK6dmRE3

Claiming my trial tokens: 0x60db3046b3c8a6d34acf6262a9ff4e466f9f6b522a3c9a22ae6eb9c1e681e623

[Danil Lugovskoy ∎ @deniallugo]

@zksync, @the_matter_labs’s zkRollup for trustless, scalable payments is now live on Ethereum mainnet!

Give it a try: 👉👉 https://t.co/BirK6dmRE3

Claiming my trial tokens: 3647900268665560

[Danil Lugovskoy ∎ @deniallugo]

@zksync, @the_matter_labs’s zkRollup for trustless, scalable payments is now live on Ethereum mainnet!

Give it a try: 👉👉 https://t.co/BirK6dmRE3

Claiming my trial tokens: 3607332964714642

[Danil Lugovskoy ∎ @deniallugo]

@Mr_Freid Вот так всегда, только пару раз не ответишь на твит, из за разного рода последствий и сразу про тебя гадости говорят...)

[Danil Lugovskoy ∎ @deniallugo]

@metrobait едет домой... http://t.co/48eQ8Wla