Parth (@0xparthdev) profile picture

Smart Contracts Developer @yieldnestfi. prev @aave @_VaporFi @amazon

Blockchain
Joined December 2020
Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)Photo by Parth (@0xparthdev)
good article on @binance on how do they prove or build proof of reserves binance.com/en/academy/artic… didn't understood things about how zk-snarks proof works in that case since not much familiar with it but it seems time to deep dive on ZK in sometime
2
144
so the AI tool used internally gave access to each other machine in same org? Would like to read detailed postmortem as lot of things are missed in this and not properly explained.
1
169
Not all ERC20 blacklist implementations are equal when it comes to asset recovery after an exploit. Comparing USDT vs. USDC for example, the difference in how the smart contract is written resulted in an extra $200m+ USDT frozen in the Binance hack. USDT only checks the sender, not the recipient: a blacklisted address can still receive USDT but can’t move it out. It’s just a honeypot. USDC also checks the recipient: a hacker can’t receive USDC once blacklisted. In the Binance hack, Tether blacklisted the hacker at 09:01:35 PM (UTC). 09:04:23 PM, the hacker transfers another $4m in. 09:44:11 PM, the hacker sends another $200m in. Both transactions went through, delivering USDT into a honeypot where it was automatically frozen. With an implementation similar to USDC, the transfers would have failed, leaving the hacker free to move those $204m to another address. As more projects consider adding blacklisting to their ERC20 tokens, imo they should only check senders, not recipients.
11
4
58
5,277
good read on this eip for integration with signatures where there is need for contract signing eips.ethereum.org/EIPS/eip-1… the best usecase of this is implemented in gnosis safe implementation github.com/safe-fndn/safe-sm…
322
Deep diving on EIP-7702 this weekend Great introductory video by @lightclients youtube.com/watch?v=_k5fKlKB… and by @PatrickAlphaC youtube.com/watch?v=0uy4nd8v… Reading official eip spec was overwhelming at first but this two videos + AI made it click.
244
great overview on market making on exchanges
"Greed makes markets." Annanay Kapila (@annanay) spent years as an HFT quant at Flow Traders and Tower Research before founding QFEX (@QFEX), a perpetual futures exchange for equities, commodities & FX. Cambridge Maths. At his last job, the desk traded $10B+ of volume a day, run almost entirely by algorithms. In this lecture, he builds market making from first principles: - The map of systematic trading: prop money vs. other people's money, HFT vs. mid-frequency, and why every strategy lives in one quadrant - Why prop firms can return 50-100% a year while hedge funds can't: HFT never leaves you holding a big position - The order book from scratch: bids, offers, limit orders, and why the first order on a price level gets the trade - No free lunch: how arbitrageurs force every order book to reveal a fair price without anyone trying to - The entire strategy in one line: bid below fair value, offer above it, collect the difference forever - Market making is "time-spreading risk," warehousing positions between a seller who shows up now and a buyer who shows up later - Adverse selection: you're most likely to get filled precisely when your price is most wrong - Why market makers are completely self-serving, and why that's exactly what makes markets work - The competitive race that compresses spreads: greed among market makers means lower costs for everyone else - Thick books vs. thin books, and the vicious loop that keeps illiquid markets illiquid Highlights: (00:45) The systematic trading map: capital vs speed (01:45) Prop firms vs hedge funds: return-on-capital economics (06:29) A message from Onyx (07:55) Where market making sits: high-Sharpe prop HFT (08:55) Fungibility and why exchanges exist (11:00) How a central limit order book actually works (17:40) No free lunch: arbitrage-free pricing in the book (19:55) Theo: reading fair value from the mid (22:45) Who really posts the book (not retail) (24:35) Market making as warehousing risk across time (27:20) Edge: quoting around your fair value (29:45) Queue priority and the adverse selection problem (33:05) How competition compresses the bid-offer spread (37:40) Thick vs thin books: liquidity begets liquidity (43:55) Scaling to $10B a day on algorithms
241
Great guide on events in solidity and the underlying opcodes for events. Was great read for weekend paragraph.com/@spacesailor/t…
1
5
397
Parth retweeted
Web3 security firms are getting carried away with their AI claims 🧵 Firms are falling over each other to announce AI breakthroughs — some even going as far as saying their agent outperforms their own researchers. Bold claim. Yet not a single one has released their model for public testing. Funny how that works. What makes it stranger — these same founders charging $130k for a 14-day audit are now offering free AI pre-audits. Suddenly so generous 🤔 Here's the thing though, none of these companies have poached a senior AI researcher from Anthropic or OpenAI. These are security researchers who've fine-tuned frontier models on mostly public audit data. Respectable work, but let's not overstate what it is, because everyone is building on the same foundation: → Same frontier models (Claude, GPT-4o, Gemini) → Same public vulnerability datasets → No proprietary data moat → No dedicated AI infrastructure advantage So if everyone has the same ingredients, why are some founders acting like they've invented fire? The gap between any two firms here is a few weeks at best. And the context matters here — the web3 security industry is under real pressure right now. Firms that used to rely on a pool of contract researchers to handle overflow are now getting by with just their core staff. Clients have caught on, rates are being pushed down, and firms are quietly doing more with less. So when you see these AI announcements, ask the one question nobody wants to answer — where are the benchmarks? Where is the model? If it's already free, why not release it? Until then, please go easy on your AI 🫡
8
1
47
2,936
Too many programmers waste time bouncing from one study subject to another. They fear that what they are studying currently is not "optimal." A less charitable interpretation is that most people cannot focus... ...but I don't think this is the correct diagnosis for many people. The space of subjects to study is massive, but time is limited. Therefore, the "fear of misplaced priorities" is reasonable. Here's what I have to say: Bouncing from one subject to another is unquestionably less optimal than picking the "wrong" subject and sticking to it for at least a month. The more you know, the easier it is to pick up other subjects as they "feel related" to something you already know. So don't worry if you "study the wrong subject." Two years from now, it might be the key that makes the right opportunity easy to learn. - Compilers will make you better at leetcode - Operating systems will make you better at blockchains - ZK will make you better at quantum computing Math will make you better at machine learning Plus, the more deeply you study more subjects, the better intuition you will have for what the "right subject is." Without that grounding, you are liable to being swayed by tech influencers who are optimizing for their engagement rather than your well-being. Being a generalist doesn't mean watching 3 hours of content on a lot of subjects. It means having the ability and prerequisites to go deep into an arbitrary subject on command. You can only grow that skill by going deep several times, which only comes through sustained focus. Too many people study a subject until they hit the worst part of the Dunning-Kruger curve, then move on to the next subject. Such a study habit is very destructive.
4
20
3
144
6,777
great work. Nice to see different initiatives taking place to secure onchain contracts and vulnerabilities
Phylax just blocked its first live exploit attempt on Linea. An external integration misconfiguration caused some wallets to approve a 0x Settler address directly. Working with @0xProject, we deployed a targeted mitigation... and the first drain attempt was stopped! Read on
1
335
Is there any detailed articles comparing slippage of Uniswapv2 vs curve V1 and how the dynamics changes based on the reserves in the pool? Any blogs, resources or papers?
172