Product first teams win. This is exactly why we prioritize code over whitepapers.

Remote = optimize for skill. In-person = optimize for efficiency. 30 people, 6 continents at our offsite. Half the "rude" people on Slack are just direct. The other half are actually tall.

'Project X is partnering with Project Y' = press release 'This founder called to say our code quality saved them 3 months of debugging' = actual relationship The crypto industry confuses announcements with outcomes. Real builders know the difference.

Been thinking more about the Soham drama and it missed the point. Tier 3 protocols can't afford dedicated devs. Big protocols have 1-2 people handling billions in TVL. The problem isn't multi-protocol devs - it's misleading people about your capacity.

Working with @AvailProject taught us something: even infrastructure builders need infrastructure. Their feedback: "You don't have to build as much" became our best sales pitch. We're the infra for the infra.

You don't call installing AC at your grandpa's house a revolution. Why do we call bringing TradFi on crypto rails a revolution? If anything, i would call it overdue

Really excited for this

Or in other words: Why build infrastructure when numbers go up?

Standard crypto playbook: Raise → TGE → Dump vested tokens → Exit This attracts mercenaries optimizing for quick liquidity events. We tell people upfront: this will take years, you'll need to understand complex architecture, and success means long-term ecosystem health over token pumps. Great soft filter so far.

Very wrong take I heard recently: ZK makes staking obsolete. ZK: 'Cannot cheat' Staking: 'Expensive to cheat' ZK proves correctness. Staking ensures liveness, coordination, and fair value distribution. Most systems need both. Math AND money.