[Feel free to edit this Tweet, just tag @Caddi_Finance and include the link below ๐]
โณ๏ธ My swaps are now optimized by @Caddi_Finance, check it out ๐
๐ https://t.co/GKIHt6n5M2
๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐
I just had 154 Rainbow Points dropped into my wallet โ everybody has at least 100 points waiting for them, but you might have more!
Claim your drop: https://t.co/d9mdqaZZQb
๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐
It's time to BLAST OFF
@BLAST_L2 is the L2 with native yield backed by @Paradigm and @StandardCrypto
Join Blast Early Access to start earning yield + Blast Points, redeemable in May
๐ Brace yourselves for the #Linea Entertainment Festival - @galaxy_sidus is in! The event is ON!
Immerse yourself into exciting quests on the LINEA blockchain with astonishing prizes for everyone!
๐ Follow SIDUS on DeGame: https://t.co/EVeAHVMRJO
#Sidus#Giveaway#Gaming
๐ฑThings you may want to know:
1๏ธโฃIs the game ready? โ Download- https://t.co/OPMJf8NjXY
2๏ธโฃWill there be airdrops? โ Become a holder & play game to collect 8Ball Pts for aidrop rewards!
3๏ธโฃWhat is the reward NFT Cue for?๐ฐImportant asset for play2win matches in the next version!
Sign up for early access to #SynFuturesV3!
Coming to #SynFuturesV3:
โ The groundbreaking Oyster AMM
โ Fully on-chain order book
โ Single token concentrated liquidity provision
โ Options for everyday investors & professional traders!
More info๐ https://t.co/wVzEPwguGz
Pull up a chair and become a part of our joyous feast, curated with love by AoD and @BNBCHAIN.๐ฅ
Lift your goblets high, let's toast to this extraordinary alliance. ๐ป
It's time to cheer and celebrate, so let the fun commence๐
๐ 50 Dinolists
๐ https://t.co/vsJ3EgjLFo
โณ 12:00 Sep11 - 12:00 Sep 13 UTC
๐ข Speak up and make a difference! ๐ฅณThe FIRST official #KiloEx feedback campaign with limited #Whitelist is LIVE NOW!
Participate in our campaign and share your valuable advice with us. ๐ฌ๐ If chosen, you'll receive exclusive benefits waiting to be claimed! Don't miss this opportunity to have your voice heard! #Web3Go
๐๐Join our @Galxe campaign now: https://t.co/stnnQsHCOs
#airdrop #decentralize
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