Vladislav Volosnikov retweeted
"With Prividiums, it's now possible for Institutions to build and operate private systems as part of the global Ethereum network, with all the control and compliance they require."
@anthonykrose, Product @zksync, writes for @ethereum about Privacy & Incorruptible Finance.
Vladislav Volosnikov retweeted
ZKsync prover optimizations just hit mainnet. Big gains on speed & cost. Feel free to read more (technical) details here: amstelden.com/zksync-prover-…
DMs open for follow-up questions.
It is possible to track gas deltas in hardhat-gas-reporter now
github.com/cgewecke/hardhat-…
Vladislav Volosnikov retweeted
Why do we have "stack too deep" errors? JVM, WASM, CLR are all stack machines too but don't have this issue! Why is EVM different?
I looked under the hood at Solidity codegen to find out. Check out my first post in a series about compiling for the EVM:
frang.io/blog/codegen-for-st…
Vladislav Volosnikov retweeted
Fixing solidity stack too deep errors be like
source: Rural Balance Master
Just published brief explanation of our Elastic fee concept from last paper in Algebra Protocol:
medium.com/@vladvolosnikov/e…
More price impact - bigger fee. It's simple, right?..
If you are really greedy, then logical branching in a EVM is gas-expensive. Used an interesting trick to help optimize abs function in OpenZeppelin:
github.com/OpenZeppelin/open…
Made a little contribution with my pull requests and issues for 5.0. Open source libs/tools/projects are important for all, imo everyone in tech should sometimes participate in their development
Every time you've deployed an OpenZeppelin contract, a contributor has been there to ensure its robustness.
The upcoming release of Contracts 5.0 is a significant leap forward, underpinned by the spirit of open-source. The open-source ethos enhances security through the diverse insights brought by crowd-sourced examinations of the code. Community collaboration, coupled with meticulous attention to each detail and functionality got Contracts 5.0 to the highest standard. Credit to all!
We owe a special acknowledgment to the OpenZeppelin Security Services audit team, led by @xaler2 and Andripol (GitHub handle). Their rigorous examination was instrumental in identifying a total of over 80 issues, and a number of additional recommendations.
The core ethos of OpenZeppelin Contracts revolves around creating public goods. We thrive on giving back and amplifying the voice of our community. Our appreciation extends to all contributors. As we contribute to the blockchain movement, we’re crafting the future of the open economy together.
For those without a Twitter handle displayed on GitHub, we're acknowledging you with your GitHub handles.
Following is a list of all external contributors to OpenZeppelin Contracts 5.0 :
@ownerlessInc
@allwin199
@balaji_pachai
@bxmmm
@clau_Bv23
@mohitvdx
@PaulRBerg
@pcaversaccio
@pgrimaud_
@RenanRSouza35
@serg_tikhomirov
@vittominacori
@0xVolosnikov
Trevorgjohnson
rjwalters
Sebastiantf
qiweiii
MollyHe5
NishantKoyalwar
CodeSandwich
Hicham010
kfishnchips
lhemerly
Lol
Are solidity devs properly aware of how degen it is to use optimizations during compile time?
Check out the #1 finding in a @trailofbits audit report.
github.com/ajna-finance/audi…
Just published yet-another-solidity-optimization-article, but with a couple of interesting moments sometimes forgotten by devs (I promise)
link.medium.com/aIH4KeeHWBb
Found out that I has 3 GitPOAPs for my humble contributions
gitpoap.io/p/volosnikov.eth










