Speak to agents, not humans

Portofino 🇮🇹

There is a recurring pattern in crypto markets.. A new primitive emerges quietly at the protocol layer, initially perceived as a niche innovation, and within a few years becomes the foundational infrastructure. Automated Market Makers did this for trading. Lending pools did this for on-chain credit intermediation. Ethereum is now converging toward a new primitive of similar magnitude: Permissionless, Programmable Vaults. @LidoFinance demonstrated that staking could operate at institutional scale. Lido V2 optimized capital efficiency through pooled exposure and abstraction of validator operations. However, this architectureintroduced structural limitations from an institutional standpoint: > capital was commingled, > risk was mutualized across participants, > and validator selection was abstracted away from the end allocator. This model maximizes efficiency, but does not align with institutional requirements around mandate control, counterparty selection, and risk isolation. Institutional allocators do not simply seek yield. They require granular control over exposure, clear segregation of risk across mandates, and enforceable constraints embedded within the investment structure itself. This is precisely where Lido V3 and stVaults represent a step-change. Instead of a monolithic staking pool, the system evolves toward a framework of dedicated, programmable staking vaults, where each vault can be configured with its own operational, financial, and governance parameters. At the vault level, participants can explicitly define: 1/ The validator set and infrastructure counterpartie 2/ The risk framework set by the curator 3/ And the access model, whether fully permissionless or restricted to a defined set of investors. This transition fundamentally redefines the nature of staking. Once staking becomes programmable at this level, a new set of institutional use cases naturally emerges. Segregated staking mandates can be constructed, allowing allocators to maintain direct control over counterparties and risk exposure. Staking positions can be integrated into broader capital structures, including collateralized financing strategies and balance sheet optimization frameworks. More importantly, staking yield itself becomes a predictable, modelable cash flow, enabling the development of on-chain credit products and structured yield instruments. The core shift is conceptual, but critical. Lido V2 made staking scalable and liquid. Lido V3 makes it programmable, segmentable, and structurally compatible with institutional capital.

Venezuela’s stock market is going vertical, 2,978% y/y and exploding in the last month, pricing in massive regime change and economic reboot after Maduro’s fall.🇻🇪

One of the boldest tokenomic experiments since Curve’s veToken model or OlympusDAO’s bonding. But, assume at $1B AUM, 4% yield, 50% to buybacks: $20M/yr buyback budget. > At avg FT price $0.05 → retire 400M FT/yr (4% of 10B). > At $0.10 → 200M FT/yr (2%). > At $0.20 → 100M FT/yr (1%). Takeaway: Early-stage buyback percentage impact is meaningful only if FT trades cheap. As price rises (success), buybacks retire less supply Also, ftUSD engaging in active delta-neutral strategies may be classified as a security no?

Totally get the pain. But if a hackathon burns $100K and only 2 devs stick around… the problem isn’t just the money. It’s deeper. Systemic. Strategic. Let’s break it down: ⚡️ —— 1/ Hackathons aren’t factories for unicorns. They’re not meant to create sticky, long-term projects from thin air. A good hackathon is a catalyst — a crash test for your stack, your infra, and your ability to attract builders. You should come out of it with bruises, feedback, and clarity. Not dreams. —— 2/ So yes — $100K is a lot. But maybe that’s the price they had to pay to finally realize: - Their tooling isn’t ready - The learning curve is too steep - Their docs are a maze - Their infra doesn’t play well with others Expensive? Yes. Useful? Definitely — if they do something with the insights. —— 3/ But let’s not kid ourselves — part of this is internal mismanagement. You don’t drop $100K on a hackathon without: - A follow-up plan - Post-hack support - Contributor funnels - Clear onboarding for promising projects - Ecosystem incentives If you skipped that? You didn’t run a hackathon. You hosted an expensive weekend getaway. —— 4/ Now zoom out. Look at the market. You’re trying to compete with ETHGlobal — which drops $800K+ on prize pools, has elite infra partners, and attracts top-tier devs with world-class vibes. Trying to “do the same” with $100K and hoping for sticky retention? You’re not in the same league. You’re playing chess on a Call of Duty map. —— 5/ And let’s talk tech. Because this is where most infra teams fool themselves. - You give away big prizes, but your SDK is buggy. - You’re not in prod (only in testnet). - You’ve got tech debt hidden like skeletons in the basement. - And your stack is an island — zero composability. You’re not offering a platform to build on. You’re offering a sandbox full of broken toys. —— 6/ And here’s the dangerous illusion: Non-dilutive prizes. You think you’re encouraging innovation. But often, you're attracting bounty hunters. No equity. No token exposure. No reason to stay. Dev wins $20K. They’ll take a screenshot for Twitter and then vanish. You didn’t invest in them — you paid them to leave. —— 7/ So what’s the real ROI of a hackathon? It’s not retention. Not directly. It’s learning: - What devs hate - Where your DX is broken - Who really cares about your mission - Which features actually matter If your team isn’t doing a post-mortem after every hackathon, you're burning money and calling it marketing.