🕯️codeislight.eth 🕯️

🧵+12M in "stuck" crypto might be recoverable. As long as the deployer nonce on another chain is not burnt and the private key is still around. The recovery mechanism is based on CREATE opcode in the EVM. Special thanks to @pcaversaccio for help validating this finding. 1/9

@RikispRikisp They're goated!

I was about to write a whole essay about why most AI audit tools are just bs and why BailSec’s is different but the tldr is that it actually understands the protocol context, finds real issues and helped my devs improve the code a lot before the audit commit it is also run by pro auditors rather than by the same devs who wrote the code and may be naturally biased when reviewing their own work from a founder’s pov, tho, i think one of the metric that really matters is that it has already saved us roughly $250k and significantly improved security i don’t think i need to add anything else

@0xCharlesWang that's pretty dope!

Notably is that this has been the very very first iteration. Now it’s around 5-10x better

SC-AI assessment by @bailsecurity has been incredible. ahead of our main audit it spotted serious issues, and the act of resolving them made us reflect on and revise key design decisions and simplify modules that could have otherwise been problematic. By far it's the best AI auditing tool out there I have experienced so far thanks to the extent and depth it can analyze that a manual review might miss. We ran it over multiple rounds, roughly a day per module and it kept surfacing findings worth fixing. Running it recursively is what really paid off, audit a module, fix it, run it again, with fewer findings each pass until they came back clean. I believe it's a must-have as a preflight assessment before any serious audit engagement.

> someone deployed a contract on blockchain > didn't advertise it to any users > a random mev bot starts interacting with it > gets drained > looking for legal action whose fault is it though?

@ProgrammerSmart Ohhh that's really clever! So it's exponentially iterative

Clever way to reverse 32 bytes simple method -> 32 iterations clever method -> 5 iterations # input A B C D E F G H # swap 1 byte B A D C F E H G # swap 2 bytes D C B A H G F E # swap 4 bytes H G F E D C B A Code #L23-L44" target="_blank" rel="nofollow noopener">github.com/risc0/risc0-et…

@0xngmi since a decent amount (30m$+) was tipped off to @titanbuilderxyz validator, is there any possibility of compensation?

someone just swapped $50m for $36k on cowswap through aave's frontend, effectively losing 50m if you try to make this swap on llamaswap the UI won't let you at all, buttons get locked we've spent years building a price API with the highest coverage of defi tokens to avoid this

@apoorveth @Rabby_io 🫩

This demo was released 1.5+ yrs ago And we are still waiting for dapps to support ERC-5792

just noticed that Multicall3 first and last 2 bytes are mined to have "Call" lol multicall3.com 0xcA11bde05977b3631167028862bE2a173976CA11

@cz_binance @BNBCHAIN Majority are bots tho 😂

2.4 million people use @BNBChain, daily.

@SECGov 👏

Curious about crypto wallets and how to store and access crypto assets? Check out our Crypto Asset Custody Basics Investor Bulletin. investor.gov/introduction-i…

@ProgrammerSmart Yaaay!

Visualize Foundry tests tx-graph-eight.vercel.app 1. Execute Foundry test, output test trace to a JSON file 2. Upload test trace JSON and ABIs (under /out) 3. Run the visualizer

@apoorveth @inversebrah Greatest thing i've seen on CT so far

Run `npx inversebrah` get lil shid in your terminal! @inversebrah

@apoorveth @notnotstorm this is the kind of double counting that matters :)

⚠️ Duplicate events on Tempo when transferring tokens

AWS did it again! They have introduced a novel way for developers to build Agents. Today, when you build an Agent, you start with a simple goal, then end up juggling prompts, routing logic, error handling, tool orchestration, and fallback flows. One unexpected user input and the whole thing collapses. Strands Agents framework by AWS approaches Agent building differently. It takes a model-driven approach that lets the LLM decide how to plan, choose tools, and adapt to edge cases on its own. You provide the capabilities and guardrails, and the model handles the workflow, which is different from the brittle agent frameworks we typically use. Here are the highlights. - TypeScript SDK > You can build Strands agents in both Python and TypeScript. The TS SDK gives a modern async-friendly workflow and works with any provider. Amazon Bedrock, OpenAI, Anthropic, you name it. Swap models or providers without touching your agent code. - Edge device SDK > You can run agents directly on small devices using local models, with bi-directional streaming. - Strands steering > Instead of writing massive prompt blocks to force an agent into a workflow, Steering lets you guide it toward a desired outcome. The model handles the steps dynamically, which keeps agents flexible and reduces token use. - Strands evals > A practical evaluation suite that lets you test agent behavior, compare versions, catch regressions, and validate correctness or safety before deploying. This is critical as agents move from demos to production. Everything is fully open-source! One particularly interesting thing is that Strands pairs with AgentCore, AWS’s secure platform for running agents at scale. So you can prototype with Strands in a few lines of code, then deploy in AgentCore with built-in policies, monitoring, and real-world evaluations. This is important because: - You build workflows that adapt rather than break. - You choose the models and providers you want, without rewrites. - You can run agents on cloud, on device, or inside your own network. - You can evaluate, refine, and trust them before putting them in front of users. You can find the Strands Agents GitHub repo in the replies! If you want a hands-on demo showing how to build a Strands agent and deploy it to AgentCore, tell me, and I’ll record one. Thanks to AWS for building this and working with me today!

@notnotstorm Low-key that was the best Polymarket ad i've seen, well done @paradigm 👏

found a pretty major data bug it turns out almost every major dashboard has been double-counting Polymarket volume (not related to wash trading) this is because Polymarket's onchain data contains redundant representations of each trade. receipts ⬇️⬇️

@0xcuriousapple Diff between day and night

going to small codebase which compiles in secs after humongous via-ir one is such a relief here I am speed

@Loopify "You are high in April, shot down in May" ~ Frank Sinatra

this is why leverage is haram

@litocoen 0.3% haircuts i'm hearing 👀

let the liquidity flow tron is live on bungee

@cz_binance @binance

@cz_binance @binance congrats!! here is screenshots of your baby since 2017 🐥

More than 300,000,000 users trust @Binance. 🙏🙏🙏