Yash

Took a bit of time, wanted to write the best out of me. I have been studying Stealth Addresses for almost 3 months now, so this article contains almost everything I know. Make sure to check it out! medium.com/p/the-invisibl…

my friend just lost 100$ on polymarket, mf trump didn’t say a word he bet on 😭, I watched it live with him too 😭😭

lessgo, @fileverse’s infrastructure is so good, that’s what I call “Privacy by default” type product. ♥️ ♥️

We’re excited to announce Judgeathon 2026. The world’s first hackathon where participants don’t build, they judge. Top performers get: - 01 visa sponsorship - A $200K offer in SF - All expenses paid flights Applications close April 2. Apply below 👇 judgeathon.devfolio.co

Ethereum is going post quantum. pq.ethereum.org

@livia___22 @0xprivacypools excellent integration ❤️‍🔥

We recently integrated privacy pools into Cloaked, and I want to explain why these two things fit together. @0xprivacypools let you deposit funds into a shared pool and withdraw with a ZK proof that says I had money in here, and it wasn't from a sanctioned source without revealing which deposit was yours. The onchain link between depositor and recipient is severed. You get privacy without associating your funds with potentially illicit activities. But where do the funds go when they come out of the pool? If you withdraw to your regular wallet address (the one tied to your ENS, the one you've been using for DeFi, for mints, for sending to friends) you've re-linked yourself at the endpoint. An observer can't tell which pool deposit was yours, but they can see that you received a withdrawal. This is the withdrawal endpoint problem. Stealth addresses solve it. A stealth address is a one-time address, derived cryptographically, that has never appeared on-chain before. It can't be tied to your identity. When a withdrawal lands at a stealth address instead of a known wallet, anonymity is preserved. The pool breaks the backward link: it is difficult to trace a withdrawal to its deposit. Stealth addresses break the forward link: you can't trace a withdrawal to its owner. Vitalik made a version of this argument in his wallet post from December 2024. That privacy tools requiring a separate app is a dead end, and that private transfers need to be built directly into the wallet. Make it the default. That's what we built. @staycloakedxyz is a self-custodial wallet and privacy is built in. When you receive funds, they land at a stealth address. When you deposit into a privacy pool, your funds join an anonymity set. When you withdraw to yourself, the wallet generates a ZK proof and sends the funds to a new stealth address, with no connection to the deposit or to your other addresses. The two technologies are better together and give users better privacy & better UX today.

@_KxrMa_G @grok maybe ?

@offee_co I think therefore I AM

okay, I want to know what is everyone’s perception of AI is conscious, or not? I don’t really know when should we consider AI conscious or what is the idea of AI being conscious?

guys will buy "blue tick" to write articles and start shitposting 😭😭

@_KxrMa_G wait wtf

When did RAM get this expensive? Wtf I need to pay 45k to get 32gb. Wasn’t this how much a entry level RTX used to cost 😭

I always have been a fan of products that makes onboarding of users into web3 easy. Recently been introduced to porto.sh and already I can say it's a really well thought and great product. Kudos to @ithacaxyz !

@livia___22 @staycloakedxyz for sure, I’ll be happy to check out 😊

@offee_co This is awesome. We have been building @staycloakedxyz, a stealth address wallet. Can dm you an invite code!

Took a bit of time, wanted to write the best out of me. I have been studying Stealth Addresses for almost 3 months now, so this article contains almost everything I know. Make sure to check it out! medium.com/p/the-invisibl…

@0xpanicError @AbhiMan1601 ❤️‍🔥❤️‍🔥❤️‍🔥

The SoK on Speedy Secure Finality has been accepted in IEEE ICBC 🥳 Really happy to have my first paper accepted in a prestigious conference like this and special thanks to my co author @AbhiMan1601 for all his contributions.

We built DisseK - a tool for selective disclosure of private documents on fileverse. It treats every line as a leaf of merkle tree and then the merkle proof is generated that the selected disclosed content is part of the whole document. Check it out: github.com/AnInsaneJimJam…

@nebula2004 @ethmumbai LOREE

@offee_co @ethmumbai Ayein 👀

my @ethmumbai experience: > attend conference > check-in for hack > think of good long term idea > go visit places in bombay > build the project > API crashes while recording demo > still submit and present smh > win some amount smh > miss return flight > almost missed next one

I Saved Injective's $500M. They Pay Me $50K. I like hunting bugs on @immunefi . I'm decent at it. - #1 — Attackathon | Stacks - #2 — Attackathon | Stacks II - #1 — Attackathon | XRPL Lending Protocol - 1 Critical and 1 High from bug bounties (not counting this one) Life was good. Then I found a Critical vulnerability in @injective . This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk. I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity. Then — silence. For 3 months. No follow up. No technical discussion. Nothing. A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either. I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten. I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve. Full Technical Report: github.com/injective-wall…

@ethmumbai conference was too good! Their takes on privacy and ongoing development in Account Abstraction were really nice to hear. Met amazing peeps in the space, also met peeps from @devfolio . Attending the hackathon today, looking forward to chat again.

Today I am happy to post one of my longest working papers, the DeFi evolution over the last 9 years. From @Uniswap , @CurveFinance , @Balancer Evolution to the rise of @HyperliquidX this Paper covers all significant improvements in the last 9-10 years. I hope you enjoy reading this one. After the last papers were all TradFi approaches, this one comes back to our hometown, DeFi. (drive.google.com/file/d/1EAxEh3…)

was reading articles/journals about 2008 economic crisis. you can find almost everything finance has to offer go wrong. ong it’s a mess!

I wanted to understand how mobile GPUs can accelerate ZKP proving. So, I read the papers, studied ICICLE-SNARK and Mopro’s Metal Implementations and wrote a Technical Blog covering GPUs, MSM, NTT, current scope and constraints. Check this out ⬇️ hackmd.io/KmoAyo8qRwaTfN…