Moon Maths is live on Giveth. giveth.io/project/the-moon-a… If you’ve ever wanted ZK explained like a map (not a wall of symbols), this is the project: open-source, free, narrative-driven. If it’s useful to you, consider funding the next chapters: Finite Fields → Groth16.

If you aren’t lifting to kpop demon hunters you probably won’t lift the weights “up, up, up”

REMINDER: apps are wrapping up soon (sept 24) 75 spots only → 6 weeks of rust + solana security → free to join for everyone cohort #2 is almost locked. if you want in, now’s the time: 🔗 rektoff.xyz/bootcamp

Dear Crypto Community & Privacy Advocates, This is an urgent call: My trial begins July 14, and we’re facing a critical shortfall. I need to raise $500K in the next few days and $1.5M within a couple of weeks to sustain our fight - covering escalating legal fees, expert witnesses, and research as the case extends beyond the initial 2-week projection. My team is working nonstop to defend code as free speech, protect software development , and push back against government overreach that threatens us all. If you can help, please donate now - every contribution counts in this battle for our freedoms: freeromanstorm.com This is urgent 🚨 nitter.net/rstormsf/status/194381… Thank you. 🙏

Been listening to @bountyhunt3rz podcast everytime I take a walk For all security researchers wanting to reach god level but feel like they are stuck, I recommend checking out the episode with @0xFlint_ The discussion gave me fuel to work better/harder piped.video/IJAIpciVRYg?si=WfoY…

How to succeed as an independent security researcher: 1. Choose one goal for the next 12 months: focus on either learning or earning. This will provide clarity and enable you to get what you want. 2. Play the long game: One week's winnings or a single audit doesn't define you, especially as an independent security researcher. When things don't go your way, pick yourself up and keep moving forward. 3. Build trust: I once saw @cmichelio advocating for a finding in a competition that wasn't his, arguing it deserved a high severity (it was marked as medium). Even though it reduced his payout from that competition, he did the right thing. With security, the commodity you are selling is trust; it is easy to lose and hard to earn. 4. Understand that the protocol team is your customer. They're paying you to help secure their codebase. Treat them as you would expect to be treated as a paying customer when purchasing a product or service. If you treat them as adversaries, you'll struggle to find long-term success in this industry. 5. On judging: understand that judging will never be perfect. In any competition or bounty, the knowledge hierarchy usually goes like this: the team that created it knows the most, followed by security researchers, and then the judges. If judges had a deeper understanding of the protocol than the security researchers, they would likely be competing and earning significantly more money. For a sports analogy, both Ronaldo and Messi have faced unfair calls from referees, yet they don’t let their careers be defined by a single decision. 6. Make friends: This industry is perfect for solo and detached work. However, you would go further by making friends. Meet security researchers at conferences or the Cantina open doors next to your city. 7. Finally, hustle and grind 🫡

Looking at other industries re how they approach security: medium.com/p/df0c6a01e9dd

Some people today are discouraging others from learning programming on the grounds AI will automate it. This advice will be seen as some of the worst career advice ever given. I disagree with the Turing Award and Nobel prize winner who wrote, “It is far more likely that the programming occupation will become extinct [...] than that it will become all-powerful. More and more, computers will program themselves.”​ Statements discouraging people from learning to code are harmful! In the 1960s, when programming moved from punchcards (where a programmer had to laboriously make holes in physical cards to write code character by character) to keyboards with terminals, programming became easier. And that made it a better time than before to begin programming. Yet it was in this era that Nobel laureate Herb Simon wrote the words quoted in the first paragraph. Today’s arguments not to learn to code continue to echo his comment. As coding becomes easier, more people should code, not fewer! Over the past few decades, as programming has moved from assembly language to higher-level languages like C, from desktop to cloud, from raw text editors to IDEs to AI assisted coding where sometimes one barely even looks at the generated code (which some coders recently started to call vibe coding), it is getting easier with each step. I wrote previously that I see tech-savvy people coordinating AI tools to move toward being 10x professionals — individuals who have 10 times the impact of the average person in their field. I am increasingly convinced that the best way for many people to accomplish this is not to be just consumers of AI applications, but to learn enough coding to use AI-assisted coding tools effectively. One question I’m asked most often is what someone should do who is worried about job displacement by AI. My answer is: Learn about AI and take control of it, because one of the most important skills in the future will be the ability to tell a computer exactly what you want, so it can do that for you. Coding (or getting AI to code for you) is a great way to do that. When I was working on the course Generative AI for Everyone and needed to generate AI artwork for the background images, I worked with a collaborator who had studied art history and knew the language of art. He prompted Midjourney with terminology based on the historical style, palette, artist inspiration and so on — using the language of art — to get the result he wanted. I didn’t know this language, and my paltry attempts at prompting could not deliver as effective a result. Similarly, scientists, analysts, marketers, recruiters, and people of a wide range of professions who understand the language of software through their knowledge of coding can tell an LLM or an AI-enabled IDE what they want much more precisely, and get much better results. As these tools are continuing to make coding easier, this is the best time yet to learn to code, to learn the language of software, and learn to make computers do exactly what you want them to do. [Original text: deeplearning.ai/the-batch/is… ]

Some thoughts on applying complex system analysis to smart contract security research (for aspiring smart contract security researchers) medium.com/@cyfe45/applying-…

Let's go! I've just completed the Cyfrin Updraft Assembly and Formal Verification course! 🔥 I've learned about: - Assembly, Yul and Huff - Opcodes - Formal and invariant testing And way more, completely for free! Check it out here 👇 updraft.cyfrin.io/courses/fo…

The single most important advice for a new bug bounty hunter was dropped by infosec_us_team in the Immunefi discord: "Rewire your brain so that instead of hunting for 'bugs' or 'mistakes', you hunt for a specific 'impact'..." Your income will go way up because... 🧵 1/5

In essence, security research is about mastering four key processes • Question everything • Challenge assumptions • Explore integrations • Look for bugs in it By mastering these 4 core actions, you can make good money 💴

💣 The MOTHER of ALL ALPHA is here. I officially present to you: THE ART OF AUDITING web3-sec.gitbook.io/art-of-a… The first community-driven resource that consolidates thousands of hours of expertise from the sharpest minds in the industry. I have spent the past 3 months scraping the leaderboards, collecting wisdom from some of the best in the game. After nearly 80 DMs and countless inspiring conversations, the final product is here for everyone to explore and benefit from. 🔥 What’s inside? Lessons from 52 top-performing, highly-respected auditors, including: - Multi-million-dollar bounty hunters - Multiple competition winners - Leaders at the top of all-time rankings 📗 KNOWLEDGE THAT IS EVERLASTING Over 2,500 years ago, Sun Tzu wrote The Art of War, and its lessons remain timeless. Inspired by that legacy, we created The Art of Auditing - a resource designed to capture knowledge that stands the test of time. Platforms will evolve, judging criteria will shift, and bugs will come and go—but the core principles outlined here will always hold true. 🧠 REAL VALUE FOR EVERYONE The Art Of Auditing has the specific goal to deliver ALPHA and INSPIRATION to EVERYONE, even the TOP-tier auditors.That’s why every contributor is a proven expert with a stellar track record. 🛠️ NEVER ENDING PROJECT I thought I could reach all the great auditors out there in one go, but it turned out there are too MANY of them and I am just ONE guy. I'm not sure if I even covered 50%🤯 There’s still an immense wealth of knowledge waiting to be added to this project. Every experienced auditor with achievements is INVITED to contribute to this collective knowledge base at ANY TIME. 💪 CREDITS All credit and recognition go to the 52 incredible auditors who made this resource a reality. Each of them committed to contributing and each of them DID. Despite this being one of the busiest periods in the industry, they gave their most precious resource - their time. Having experienced it firsthand, I can confidently say that each one of them has extreme integrity and a deep sense of responsibility. If you plan to work with any of them, rest assured: 🫡 These auditors DELIVER I'm tagging all the great names below👇

Governance smart contracts contain attack vectors that have been exploited multiple times in recent years. Here is a 10/10 blogpost on governance vulnerabilities, very useful for devs and security researchers. 10x to SigmaPrime for it🫡 blog.sigmaprime.io/governanc…

Mastering Ethereum 2nd Edition coming. This can only be good, the 1st edition is a forever must-read Ethereum book✌️

i strongly believe that AI will further increase the gap between good and bad software engineers. it is not a great equalizer like many might think it is. code writing itself was never the differentiating factor for developers. the ability to think critically, design scalable systems, and solve complex niche problems is what separates the great engineers from the bad. yeah it's awesome that you can create simple hobby projects in 20 minutes now, but those skills were already being commoditized. LLMs can effectively replace code monkeys. on the other hand, the great software engineers are no longer burdened by writing arduous syntax, and can instead focus on system design, efficient architectures, and fault tolerant services. LLMs just further enhance shipping velocity for already talented devs.

Illustration of how a smart contract should progress from first draft of code to deploy.