
engineering @EnsoBuild | smart contract security
Blockchain
Joined March 2023
- Tweets1.1K
- Following868
- Followers1K
- Likes6.6K
BK | ⌘ retweeted
We’re live at @dappcon_berlin Berlin 🛠️
Come visit the Enso booth and see how we’re powering onchain apps behind the scenes.
And don’t miss today’s talk and workshop:
🧠 Shortcut to Building Onchain w/ @connor_enso – 17:05, HALLE
👨🍳 Shortcuts Kitchen w/ @nenadvitt – 17:45, Workshop Room
(psst… there’s a surprise for all workshop attendees 👕)
BK | ⌘ retweeted
Those who had closely followed @EnsoBuild might have discovered this last week when @BKWeb3 added it 😆 and I asked him "You sure they have BNB??? I don't see it in the frontend!!", to which he replied "Maybe it's coming up~~ 😉"
BK | ⌘ retweeted
The time has come to call on you, the Enso community, to vote for Enso on @KaitoAI
Follow the step-by-step guide below. Big things are coming ↓
BK | ⌘ retweeted
I’m looking for a long-term business partner!
My goal for the next few years is to build a world-class boutique web3 security firm! I see so much opportunity in this industry but it’s hard to do it as a solo player.
I’m looking for a person with a strong technical or business skillset.
> DM me if you’d like to team up!
I’d appreciate a retweet for visibility.
BK | ⌘ retweeted
🧵Solidity version 0.8.24 is out.
This version introduces couple of interesting features:
- Transient storage opcodes (EIP-1153)
- MCOPY opcode (EIP-5656)
Transient storage opcodes (EIP-1153)
TLOAD and TSTORE opcodes manipulate state like storage opcodes but the state is discarded after every transaction.
Since the state is discarded after every transaction, this is cheaper than storing the values in the storage state, because they do not require disk access.
Examples of using TLOAD and TSTORE:
- Reentrancy locks using TLOAD and TSTORE will be cheaper than using SSTORE and SLOAD
- Possibility to introduce single transaction ERC20 approvals, which would be cheaper than regular approvals.
Fun fact - this proposal was created almost 6 years ago and it has a fan page.
MCOPY opcode (EIP-5656)
MCOPY opcode helps to copy memory state in a cheaper way.
Before 0.8.24, to copy a memory state MLOAD and MSTORE opcodes were used to do so. MCOPY allows to do the same action with one opcode and spend less gas.
MCOPY matches the other copying instruction like CALLDATACOPY and RETURNDATACOPY.
Conclusion
I am very excited for the transient storage - I think it will bring a lot of interesting use cases.
@PopPunkOnChain and @optimizoor are probably cooking up something already with the new opcodes cuz gas bad.
BK | ⌘ retweeted
Awards have been announced for the $36,500 USDC @VenusProtocol audit 🤝
Top 5:
🥇 Testerbot - $10,783.76 USDC
🥈 @0xDetermination - $1,161.45 USDC
🥉 @BKWeb3 - $983.50 USDC
🏅 ether_sky - $859.90 USDC
🏅 SpicyMeatball - $855.53 USDC (1/2)
BK | ⌘ retweeted
Regardless of what my clients are seeking, whether it's smart contract security research, Web3 consultation, or Web3 app development,
I assure them that I will always strive to exceed their expectations.
Satisfied clients are invaluable in building lasting relationships.
BK | ⌘ retweeted
1/7 Smart Contracts emit events on crucial actions.
But do you know how to make the most of these events?
Join me on this thread to explore the power of events. 🧵
BK | ⌘ retweeted
In my 2 years working in Web3:
@AaveAave and @Chainlink have by far the best documentation of anyone out there:
✅ Everything is very well explained
✅ You don't get confused
If you are just getting into Web3 - I highly recommend going through both of the protocol docs
BK | ⌘ retweeted
Smart Contract issue breakdown:
"price is calculated wrongly in BoundedStepwiseExponentialPriceAdapter"
This is the medium impact issue I reported on the latest @indexcoop audit contest on @sherlockdefi
✅ Summary
BoundedStepwiseExponentialPriceAdapter contract incorrectly calculated the price, where in the math equation mistake was made:
- Contract used a formula - scalingFactor * e^x - 1
- Actual formula - scalingFactor * (e^x - 1)
Because of that priceChange value is incorrect, which furthermore impacts the rebalance in the protocol.
✅ How did I find it?
When I am going into an audit:
- I always assume that there must be an issue
- I am skeptical about the code base
- Ask a lot of questions
When I got to the BoundedStepwiseExponentialPriceAdapter contract, I always assume that nothing is correct until I can prove it otherwise.
I ran tests, added the console logs, and noticed that the returned value from getPrice function does not match the expected output.
This is where I started changing variables in the tests and found what was the issue.
Conclusion:
Missing parentheses in the math formula caused the value to be incorrect.
I really hope that today you have learned something from this tweet.
Good luck catching in the next audits! 😎
BK | ⌘ retweeted
The report is in for @LybraFinanceLSD's audit with Code4rena🔎
Total findings:
High risk: 64 total, 8 unique
Medium risk: 147 total, 23 unique
Congrats to top report authors @0xJCN (gas) @0xnevi (QA) and Sathish9098 (analysis)
Read more➡️ code4rena.com/reports/2023-0…
BK | ⌘ retweeted
Replying to @pcaversaccio @Uniswap
Agree the takedown was unnecessary considering its just a github PR and not in production
Was not aware until I saw this tweet, but quickly dug in and we will be withdrawing the takedown / agree it was a mistake
Sorry about that
BK | ⌘ retweeted
Multicall3 is now deployed at the same address on 105 chains multicall3.com/deployments
BK | ⌘ retweeted
VCs simply don't get
- It is not that hard to get an ERC passed.
- ERC != consensus
- Community consensus is what matters.
- Many important ERCs (like NFT's ERC-721) reached wide adoption before written ERC
Think about ERC as NPM package. That might get you closer to truth.
BK | ⌘ retweeted
It's always weird when you find a contract with significant TVL and yet the source code isn't published. Why would anyone put money into a smart contract that doesn't have its source code published? Isn't that a core tenet of DeFi?





















