Seeing a lot of folks leave web3 security as the game changes The fun of “read code and try to break it” is giving way to orchestrating agents and triaging their findings Still security, but a different kind of work. What gives you an edge is (as always) still being figured out

Looking at your friend's LLM prompts tells you more about how they think than their social media feed ever will

In life, there's time to make money, time to study, and time to spend with family—but never time to waste

Web3 is teaching you finance in a cool way. From understanding the financial primitives while researching DeFi projects to learning how fundraising and VCs function, and how many of the world's biggest companies got started - and how they keep dictating the next big thing

Story Time 📖 I was a humble kid at school. I wasn't the good student, nor the bully, nor the funniest (well, I believed I was, but when you're quiet, no one can know it). I didn't like the system because, even back then, I felt you had to prove yourself to the ones above you and be awarded for it. And imo, people were awarded for the wrong qualities and skills. Everything felt artificial. I still believe that's true for most modern systems, but now I understand why it's needed. When I first found out about blockchain and web3, it instantly caught my interest. I didn't think about the reason behind it, but it has a lot to do with the freedom and possibility. You see decentralization — protocols earning millions in fees where no one even knows who founded them, thriving just because the product is good and no one can stop it with regulations, laws, etc. It's like the jungle, but on the internet. Smart contract contests are the only thing I know of where you provide value without any friction and get paid better than most highly paid jobs in the US. I really hope to see the greatest crypto comeback soon. 🚀

Daily reminder for Solana builders: Instruction stack depth caps at 5 — your top-level ix + 4 nested CPIs. Reentrancy only exists via self-CPI; A→B→A throws ReentrancyNotAllowed If your flow already sits near that ceiling, ask whether multisigs will touch it. A Squads execution burns one level of depth before your program even starts running

BonkDAO lost ~$20M this week and no contract was hacked. Every transaction was valid. An attacker spent ~$4M buying BONK, then passed a treasury-draining proposal with 7 wallets (2.9% turnout), clearing quorum by a hair — 882.38B vs 879.95B BONK. The code executed the vote flawlessly. That's the point. Audits verify code correctness at a moment in time. They can't see the live economic state — price, treasury value, and quorum drifting — until $4M of votes can move $20M of treasury. That's not a bug in the code. It's a config no audit is scoped to catch. An invariant a monitor enforces at runtime: a treasury transfer must not execute while the market value of the votes backing it < the value it moves out. Bonk violated it 5:1. Pair it with a timelock so a flagged proposal pauses for a guardian instead of settling instantly. Detection + a pause is a security procedure on top of a code security audit. Security has a lot of layers and the worst part is that if you leave one layer uncovered, it may compromise the entire system. Take notes, think twice and continue to progress!

Bear market is just an oppertunity to catch up with the latest technology and innovate

One invariant neutralizes inflation & donation attacks — the vector behind most vault drains Checkpoint the rate. Revert + auto-pause on >X% deviation per block A vault's share rate (totalAssets/totalSupply) moves in bps per day. Exploits move it 10–1000x in one tx

Quick tip on how to open a Visual Studio Code preview of a GH repo at a fixed commit: -> After the repo path paste "/blob/{commit}" then enter -> You open a GH view at the commit -> Press "." and you're redirected to vscodе.dev/githib/... for the given commit hash

Do you need any other proof?