I didn't expect that taking a break from X would make me miss an airdrop Guess it might be a good idea to subscribe to a service that scans for eligible airdrops and sends notifications/emails

For me, life-changing decisions often happen in November and December for some reason, so I want to start summarizing the year The books I read so far (latest to oldest) and the main idea I took from each * [Brené Brown - Daring Greatly]( https://t.co/TVKxbFG2QN) Being

> Is it late to enter into web3 security? Hard to say, but I think it doesn't pay more than dev jobs anymore, though it's still good because you can start even without a company, through contests and bb > Which programming language would be in high demand, and which one would

I was thinking about how young undergrads with no tech experience become super experts in web3 security From the interviews I’ve listened to, I think there are two answers to it 1. Connections/team Basically you have somebody who shows you the right way to do things and the

I feel like eventually web3 SR will be an AI operator, verifying agents' findings and directing them to the right bugs and places to investigate

It’s always the same advice for a balanced life: nurture your relationships, pursue challenging goals, spend time in nature, and make room for fun Lately, it’s also all about sports and healthy food

One of the most underrated skills is choosing the right contest/BB—it can boost your rewards by up to 10x+ Sometimes it's about luck, but also using a rare language or technology, or entering smaller contests when most others are focused on big ones that are happening at the

A protocol I've started using when experiencing high anxiety/worries caused by burnout/tiredness/exhaustion: - The main goal, once you recognize it, is getting out of Fight or Flight (FF) mode - Then address the issues that caused the stress - Making decisions

For web3 audits rn I see a few problems with AI, based on my experience with Codex (gpt5 high reasoning) 1. Hallucinations: * when you already know the code, AI is very helpful as a reminder of how the code works, since you see its errors anyway and it helps with fuzzy

There's always a trade-off between going deep and being fast, which is true in most fields. Deep or wide. Not sure what's best in BB It looks like the best approach is treating BBs as a river of possibilities Instead of trying to extract every bug from one project, just take

Interesting observation: if previous audits took about a month, it'll usually take me at least that long to find the first bug No prior audits: usually a week

I just tried making a podcast from a @blockthreat weekly newsletter (week 37) 1. Copied all the links from the page https://t.co/5y4Ic4CDru 2. Added them to NotebookLM 3. Generated an audio overview P.S. This was just a quick first attempt and I ran into some

I'm looking for a way to safely run npm/hardhat projects without getting pwned, and with the recent news of a supply chain attack, this is back on my mind https://t.co/bddKCgyqmS I think isolating it in Docker should be possible, but I don't feel like I have the skills to set it

I recently read a Scrum book, and I'm thinking about the concept of story points, or effort, or "brain fuel" It kind of explains why we can work all day on some tasks, while other short tasks completely drain our energy and tank our productivity for the rest of the day, even

I've noticed a pattern in my BB strategy: I'll start on a medium/low-reward one, find some C/H/Ms, get overconfident, then try a harder project with bigger rewards, but the audits are much better and the codebase is less complex, find nothing, and then go back to

What works short-term and makes money short-term can lead to losses and bad results in the long run One example is overwork; after a while, you just lose focus and the ability to think deeply, so you're not producing any valuable findings Another is not learning—it saves money

I use https://t.co/rDD2a3SdIS pretty often to see how a protocol's website looks to a user with a certain balance/stake (e.g. a whale) But you can also use it to impersonate contracts (e.g. a Treasury) and see how much a protocol has staked on other protocols like Aave, its

I was reminded again recently that when I submit an issue on BB, 90% of the time the team's questions are unpredictable So to save time, it's not worth overthinking their questions and pre-emptively writing answers in the report, beyond the common sense

Working too much can cause you to forget to make money It's easy to get stuck, lose the big picture, and have no energy for new opportunities No time to sharpen the saw That background thinking that happens when unfocused is important too