The age of one-time token due diligence is over. A given "token" can easily involve 300+ changing contracts.
We've built a balance sheet graph for every token, so you can see all protocol/token dependencies and then model economic and operational risks.
D² is dedicated to research on how protocols work, why they behave the way they do, and how they can be designed better
The schedule is now live, with talks spanning:
→ DeFi Microstructure
→ Perpetual Futures & Derivatives
→ Mechanism Design
→ Prediction Markets
→ AMMs
Had a great discussion repping @Stablecoin at @stable_summit in Cannes with fellow panelists, and thank you @ivangbi_ for moderating (lobster hat and all 🦞)
Launching a stablecoin isn't just a technical problem anymore. The harder question is distribution and demand: thinking through the why, what, and who before you launch. Work with infrastructure that abstracts away the technical complexity, find your distribution channels, then focus on the product features that actually differentiate you.
Liquidity follows from that, not the other way around.
If you missed it, check it out here https://t.co/jT3x1HXU0H
Stablecoin liquidity does not scale if markets stay fragmented.
Ben Haslam, Phil Fogel (@Philfog), Lorenzo Romagnoli (@zerolore), Jackie Zhang (@Stablecoin), and ivangbi (@ivangbi_) on connecting liquidity across chains, venues, and issuers:
Headed to EthCC? So are we.
Catch Jackie Zhang @agaperste, Issuance & Crypto Data Lead, speaking on stablecoin issuance at EthCC (Mar 27–28)
Nikhil Joseph speaking at DeFi Day by Aave (Mar 30) — sponsored by Bridge
https://t.co/jnAt7FVOED
Stable Summit (Mar 27–28) — sponsored by Bridge
https://t.co/y91Cldpd15
Join the waitlist for dinner at La Lumière w/ @Privy & @Wirex (Mar 31)
https://t.co/DXcpSS43ie
Two competing thoughts lately:
- "I've lost the ability to read." I now feed Claude entire threads, PDFs, and docs just to get the takeaways🥲
- "I have a 24/7/365 thinking partner that's nearly omniscient".. well, within the training data realm ✨
Best of times, worst of times
It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.
Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes.
As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now.
It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.