zkChick

just loving zk 🌎

[zkChick @zkchick]

Creativity and long-term vision is the key. Dare to imagine.

[Astal Marketplace @AstalMarket]

Astal on @zksync is now live on mainnet!
Coming next - @Solana

✅No middleman fees
✅No forced pricing
✅Instant payments

https://t.co/R873DzOS5Y

[Astal Marketplace @AstalMarket]

Them: But you are a small project.
Us: Just for now. Our direction is clear, our vision is the biggest.

[Astal Marketplace @AstalMarket]

The only decision you should have to make at checkout:
which token you want to pay fees in.

🔜 on mainnet
https://t.co/bl15ikLgek

[Astal Marketplace @AstalMarket]

$ASTAL token locking completed.

Please join us for a live stream with our founder @inesisljami - more info about the lifestream available soon.

[zkChick @zkchick]

@inesisljami This hits. Screens reward performance, not presence — and most of us are exhausted from acting.

[zkChick @zkchick]

User facing products coming to life 🤓

[Ines I. | txFusion @inesisljami]

First order and payment just went through on @AstalMarket testnet🚀 This is only the beginning.🔥 Public launch is coming soon.

What digital shops & products do you want to see here first?

@zksync tech, @txFusion_io build

[zkChick @zkchick]

boring day, anyone anything interesting to share?

[txSync | Astal ecosystem @txSync_io]

The future of txSync is LIVE!!

Today, we’re excited to introduce our new website, redesigned to reflect who we are and what’s coming next for the Elastic Ecosystem @zksync

𝗦𝗰𝗿𝗼𝗹𝗹 𝘁𝗼 𝗲𝘅𝗽𝗹𝗼𝗿𝗲 🧵⬇️

[txFusion @txFusion_io]

Looking for a career opportunity in #web3?

TxFusion team is expending, and we are currently looking for:
🛠️ #FullstackDeveloper
🛠️ #RustDeveloper
🛠️ #FrontendDeveloper
🛠️ #BackendDeveloper

More info ➡️ https://t.co/67ZAnJd38f

[Antonio (∎, ∆) @uF4No]

Must watch presentation from @LajkoKalman at @EthCC about ZK Stack, hyperchains and hyperbridges 👇

https://t.co/KGuAk1z3zu

[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

[SmartecVitalik @Smartecio]

I have been seeing rumors that @zksync is tracking users' IP addresses. I am not a member of the team, but I believe the zkcredo release made it clear that they would never do such a thing. It is completely against the ethics of web3. There are many other ways to combat sybil attacks, and zkSync recently partnered with @0xNomis to do just that. This method does not involve IP addresses at all; it only tracks your on-chain activity on the zkSync network and assigns you a score based on that. So, rest assured that no one is taking your IP addresses. zkSync would be the last team to do such a thing.

[0xRamon.eth @ramonIsTweeting]

Loved the product-led mindset here! Great job @thirdweb

[OpenZeppelin @OpenZeppelin]

How did @zksync Era get to mainnet 40% faster? 🚀

@the_matter_labs engaged OpenZeppelin for Continuous Audits on their zero-knowledge Layer 2, enabling the organization to shave 4 months off of their development time without compromising security.

👇
https://t.co/ERmVsLT5fN

[ZKsync @zksync]

[∎∎∎∎∎∎ ]

Multiple announcements are coming soon. Before kicking off a new era together, let’s review zkSync 2.0’s recent testnet data—including nearly 9 Million transactions over the past four months.

[ZKsync Developers (∎, ∆) @zkSyncDevs]

We've just released the hardhat-zksync-verify plugin, which allows devs to verify smart contracts deployed on our testnet from the terminal or programmatically.
We've added all the information about it including code examples in this section of the docs: https://t.co/goBoBxc9aR

[zkChick @zkchick]

@JemAlesso @SBF_FTX True.