
@flint_trade_ on Solana. Formerly @anza_xyz. Proof types maxi. Spare time keys, microtones, scifi, tabletop, human languages
Joined October 2018
- Tweets1.9K
- Following467
- Followers2K
- Likes4.6K
Most Solana programs are one typo - or one agent mistake - away from disaster.
Security pros warned us 5 years ago to not do this, but everybody does it. Examples do it. Agents do it. Auditors clear it. Millions drain.
fn withdraw(...) -> Result {
if record.owner != *user.key {
return Err(IllegalOwner);
}
if amount > record.quote {
return Err(InsufficientFunds);
}
// more `if`s here - hope we have enough!
record.quote -= amount;
transfer_out(destination, amount)
}
For both safety and performance, it's time to learn from decades of critical systems engineering, embrace the strength of Rust, and "Parse, Don't Validate." Runtime checks don't belong in a program's internals. They belong at the boundaries.
Read Here 👉 👉 flint.trade/blog/fragile-cod…
Excellent new vid from @3blue1brown.
One common explanation of quantum computing is it "considers all solutions at once, then collapses to the right one."
This sorta-true simplification leads to bad conclusions.
youtube.com/watch?v=RQWpF2Gb…
We are going to mtndao 🔥🏔️🚴🏼
Deploying non-custodial multichain blinks on #Solana
Share 1-click streamlined transactions from wherever they’re at, to wherever you want





