Sabitlenmiş Tweet
Pavel Naydanov
154 posts

Pavel Naydanov
@pnaydanov
Solidity developer @MetaLamp_Web3 // Solidity Wanderer 🌌
Katılım Ağustos 2023
140 Takip Edilen47 Takipçiler

@ohMySolboy @AtriumAcademy It was challenging for me, even though I already knew how Uniswap works and was studying the architecture of version 4 at a high level. I'm also gradually moving on to the topic of limit orders.
English

@pnaydanov @AtriumAcademy Delta framework in Uniswap is tricky (at least it was for me in the beginning), especially if you didn’t work with previous Uniswap versions.
I am occupied atm with Limit Order hook. A lot of new things find out about Uni V4 workflow.
English

🧩 How I Finally Understood Uniswap v4 Delta Settlement
Half a year ago I tried to write a #Uniswap v4 hook that modifies swap deltas. After fighting with CurrencyNotSettled() for too long, I gave up and closed the laptop.
Today I finally cracked it.
Thanks to @AtriumAcademy, it finally clicked.
Main insight:
In a v4 hook you can’t just change amountIn and amountOut magically. Everything you put into the deltas, the hook must either settle itself or compensate for.
Otherwise the PoolManager will throw CurrencyNotSettled() and ruin your day.

English

To practice exactly this, I built PublicSaleHook (github.com/PavelNaydanov/…).
What it does:
➡️ While the pool hasn’t reached the USDT CAP → the token is sold at a fixed price (8 META for 1 USDT).
➡️ No LP fees during the sale.
➡️ Liquidity withdrawal is locked.
➡️ Once the CAP is reached → the hook turns off and the pool works as a regular AMM.
The hook calculates what the “native” AMM swap would be using SwapMath, compares it with the fixed sale price, and then compensates the difference from its own balance — or save the excess.
It’s definitely not production-ready (the code is quite ugly in places), but it’s an excellent way to deeply understand delta settlement mechanics in Uniswap v4.
English

I'm currently going through the Uniswap Hooks Incubator by @AtriumAcademy and put together a clean guide on how to calculate human-readable prices in Uniswap v3 and v4:
🔸How to get price from tick and from sqrtPriceX96
🔸Adjusting for token decimals
🔸Why tick and sqrtPriceX96 give slightly different prices and when to use which
🔸How it works in v4 with PoolManager + StateView
Useful for both developers and on-chain data parsers.
Read here: github.com/fullstack-deve…
English
Pavel Naydanov retweetledi

🚀 Big news!
I’ve been accepted into the Uniswap Hook Incubator UHI9 (April 2026 cohort) - @atriumacademy and @UniswapFND (who’s providing the grant).
Super excited! Ready to build and learn from the best! 🔥

English

@_indigonico It looks like you need to replace lovable in something like that.
English

@lovable_dev is this a platform or a sophisticated exit scam?
My profile hasn't loaded for a week -> Can't access projects -> Can't reach "Pro" support -> Billing bot keeps hitting my card & charging fees for failed attempts.
I’m literally paying for being locked out. 10/10 AI experience.
Fully switched on Claude code by @claudeai



English

BattleChain sounds like the next evolutionary step in competitive audits: real assets, real economic incentives, and the ability to attack a live contract. A white-hat hacker doesn’t write a report - they either find the vulnerability and claim the assets, or they don’t.
But I still don’t fully understand how this can actually work on mainnet.
1⃣ The concept works great for simple, isolated contracts - vaults, tokens, staking pools, etc. But a real DeFi protocol is quite a bit more complex. It usually includes:
- oracles,
- DEX integrations,
- dependencies on protocols like Aave,
- cross-chain messaging, and so on.
I’m not sure how all of that can be properly simulated on BattleChain. Testing a protocol on an isolated L2 with mocks instead of real infrastructure stops being “mainnet conditions” and basically becomes a testnet… just with real money.
2⃣ Will protocols actually be willing to deploy liquidity to a separate L2 purely for testing? Small projects count every single penny. Deploying to a test L2 adds extra time and overhead before mainnet launch. And how do we know there are enough hackers participating to confidently say the audit was truly deep and comprehensive?
Overall, the idea is really interesting and probably long overdue — especially given all the growing questions around traditional audits. I’ll be watching closely for the mainnet launch. This is exciting!
Cyfrin Audits@cyfrin
As of today, BattleChain testnet is LIVE. The pre-mainnet, post-testnet blockchain, where whitehats legally attack your smart contracts before they reach production. Deploy. Get attacked. Ship stronger. Here's why we built it, what it is, and how you can get involved 🧵
English

🏃♂️ Deployment frontrunning is getting wild
Just deployed several contracts on @BNBCHAIN. Immediately checked the explorer - four failed txs already hit the new addresses.
All trying to call initialize(), init(), _init(), etc. right after creation.
These are classic proxy initialization signatures. Scammers / MEV bots scan the mempool, predict your contract address, and frontrun your own initializer call - hoping to claim ownership or critical roles before you do.
The crazy part? Only one of my contracts was actually a proxy. The other three were plain contracts with no init functions at all. Still got bombed with the same calls.Either bots blindly spam common signatures on every new deployment… or their targeting script is just broken 😅
Rule that never changes:
Deploy proxy + call initialize() in the exact same transaction.
Separate tx = you're donating control to the fastest searcher. Deployment is now a real attack vector. Treat it accordingly.

English
Pavel Naydanov retweetledi

People said my Strawmap was too long - here is the cheat sheet.

James | Snapcrackle@Snapcrackle
English

@pashov Moreover, I tried it on my real project, which was undergoing an audit, and it found three fundings. I was familiar with two of them, but the third was new to me.
English

@pnaydanov Interesting, any chance you can share that simple contract sir?
English

@pashov Yeah, I can. But this is still too much to do here. Is there another way I can share the contract with you?
English
Pavel Naydanov retweetledi

🚨 Our annual Solidity Developer Survey is live and we want your input.
Take 5 minutes, shape the roadmap, and help us prioritize language design, performance, and developer experience improvements.
Fill it out here → solidity.survey-research.net/solidity-survey
✨ Bonus: participants can opt in to win a DevCon 2026 ticket.

English

Thrilled to share that I've completed the GMX Perpetuals Trading course! 🎉
@CyfrinUpdraft, thanks!
Even though the lessons didn't load at times or the quiz questions were mixed up, it's still an amazing course.
Check it out 👇 profiles.cyfrin.io/u/pavelnaydano…
English
Pavel Naydanov retweetledi

How @1inch Aqua works under the hood
Our Solidity Tech Lead @pnaydanov just dropped a technical deep dive into 1inch Aqua. With the dev release fresh out this is your chance to explore the protocol's architecture before it hits the mainstream narrative.
A must-read for builders and DeFi power users looking to stay ahead.
MetaLamp@MetaLamp_Web3
English
Pavel Naydanov retweetledi

Some interesting numbers coming out of the @HyperliquidX dashboard
I’ll admit I had my doubts about perp DEX integrations within wallets, but the volume doesn't lie. @MetaMask and @phantom are facilitating billions in trades and capturing millions in revenue.
even the average revenue per user remains in the green. attached a pie chart of the top 10 API users — the distribution is worth a look.
looks like the "wallet-as-an-interface" play is more viable than I thought


English


