Welcome to @toly, co-founder of Solana!

He's kindly agreed to do an AMA — starts in ~1 hour at 1:00pm ET.

Reply with your questions below!

A sufficiently decentralized social network. farcaster.xyz

Toly! In the heat of bugs and messy code, how important are audits and making sure clean code are pushed? I recall you tweeting about this recently. we at @chainfoxhq $CFX are building on solana access to automated repos for L1/L2. We combine AI with both static and dynamic analysis — not just fuzzing — allowing us to uncover deep security issues like unsafe APIs, dependency tree vulnerabilities, and composability bugs. We currently support Solidity, Rust, Go, and Move, and continue to build language-aware checkers in collaboration with academic researchers. We've even found bugs on your official RPC providers. and you even retweeted us in our first week live!

https://farcaster.xyz/nilsumthing/0x2b664676

@chainfoxhq marketing and strategy lead, former f500 campaign marketer

Absolutely, assuming bugs exist and baking in assertions is key. We’ve been leaning hard into invariant checks lately, and seeing how much they reveal even in supposedly safe code. Formal verification is definitely the north star, but we’ve found combining static + dynamic methods with aggressive invariants gets us surprisingly far already. Curious how you think teams should balance speed vs. rigor as ecosystems scale. Also pinged you on time.fun from @ChainFoxHQ — would be great to continue the convo there if you're open (it expires tonight 😬)

Code defensively.  Assume your code has bugs.  Add asserts all over the place for invariants. Fuzz the code.  Get formal verification (takes a while)