Here's a call graph I just made for my internal code review. New rebasing token code headed to audit + formal verification in a week. 1/4

(Thanks @brockjelmore for the fun tool)

@0xKaden People building with oracles assume they correctly return the price of the underlying asset. Attackers make them not correct, then have parties.

@alcueca @josephdelong Ah - gotcha. I just in a desktop browser. This isn't a problem I have.

@MitchellAmador First read through I thought you were advocating for the building of big walls for astriod survival!

@fbsloXBT @oknetizen Yes, this is the correct one. Thanks!

@nisedo_ This will be awesome! Looking forward to using it in code reviews.

@rocketrepreneur Followers only is the way. Plus it trains the algo.

I had a long talk with Poolpi when we were designing the Origin ARM, and that talk was critical to building a product that was easy to integrate. Really appreciate the time.

"Check the numbers [on the new product/feature] and make sure things are working right. We have only tested, audited, formally proved, and fuzz tested it. Who knows if actually works." ~me

@maurelian_ @gakonst Here to second this. Super powerful, currently a pain to do anywhere.

RT @wavey0x: during the @PrismaFi shutdown process, the @ResupplyFi team came across multiple high severity bugs one of which bricked repa…

So DeepSeek was using ClickHouse. It's not a surprise. ClickHouse is the DeepSeek of databases.

@_hrkrshnn The part that says what it takes to build a successful product.

@jsn_yrty My guess would be the majority of bug reports a project receives are either this or an LLM making stuff up.

Bug bounty hunting is about "impact" - preventing losses that are exploitable. The "exploitable" part is why the critical tier payoffs are so high in crypto. TLDR: hunting for "impact" gets you: - 100-10,000x bigger payouts - 1/1000 the rejections - Crits in perfect code 5/5