<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Current [Ventures]</title>
        <link>https://paragraph.com/@current-ventures</link>
        <description>Building the internet’s next layer — autonomous, intelligent, on-chain.</description>
        <lastBuildDate>Sat, 09 May 2026 04:30:40 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Current [Ventures]</title>
            <url>https://storage.googleapis.com/papyrus_images/67f29e5913e781ea6781f5eb2b6c36cec7e2bb54df3ddc1ddababb4ca2bb8bfc.png</url>
            <link>https://paragraph.com/@current-ventures</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Introducing Current [Ventures]]]></title>
            <link>https://paragraph.com/@current-ventures/introducing-current-ventures</link>
            <guid>MjJirLqkfDx9qX4q7HvA</guid>
            <pubDate>Mon, 12 May 2025 11:34:12 GMT</pubDate>
            <description><![CDATA[The noise in crypto is louder than ever — but the signal is still forming. New chains launch weekly. L2s promise infinite scalability. Tokens pump, crash, and repeat. Meanwhile, AI headlines dominate — and every Web3 project suddenly claims to be “AI-powered.” But most of it is noise. We’re here for the quieter layer. The systems, protocols, and primitives that actually move things forward. We don’t believe crypto needs AI right now. But we do believe AI might need crypto. The future we care ...]]></description>
            <content:encoded><![CDATA[<p>The noise in crypto is louder than ever — but the signal is still forming.</p><p>New chains launch weekly. L2s promise infinite scalability. Tokens pump, crash, and repeat. Meanwhile, AI headlines dominate — and every Web3 project suddenly claims to be “AI-powered.”</p><p>But most of it is noise.<br>We’re here for the quieter layer.<br>The systems, protocols, and primitives that actually move things forward.</p><p>We don’t believe crypto needs AI right now.<br>But we do believe AI might need crypto.</p><p>The future we care about isn’t driven by chatbots or wrappers — it’s shaped by autonomous systems: software that thinks, decides, and acts.<br>To do that, it needs rails — for value, coordination, and trust.</p><p>That’s where crypto comes in.</p><p>We started <strong>Current Ventures</strong> to support the infrastructure this future requires.Not because it&apos;s trending, but because it’s necessary.</p><p>We’re not here to play the cycle. We’ve seen enough of them.</p><p>This time, we’re going deeper — not wider.</p><p>Closer to the metal.</p><p>Closer to the builders.</p><h3 id="h-from-apollo-to-now" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">From Apollo to Now</h3><p>Before Current, we ran a small early-stage fund called <strong>Apollo</strong>, backing projects across DeFi, infrastructure, tooling, and social from 2019 to 2022.</p><p>We invested early in the teams that shaped key layers of Web3. It gave us breadth, perspective, and a front-row seat to how fast the surface moves — and how slow the foundations shift underneath.</p><p>By 2022, we started spending less time chasing deals and more time helping teams build.</p><p>That shift led directly to <strong>Current Ventures</strong> — a tighter, thesis-driven effort focused on the infrastructure we believe is missing.</p><p>We’re not interested in noise.</p><p>We’re interested in leverage.</p><p>And leverage often starts quietly.</p><h3 id="h-what-we-do" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">What We Do</h3><p>Current is a venture studio.</p><p>We build our own products, and we back others doing the same.</p><p>Sometimes that means investing.<br>Sometimes that means working alongside teams on product, infrastructure, or launch.<br>Sometimes it&apos;s both.</p><p>We focus on the foundational layers — systems, tools, and protocols that enable autonomy, coordination, and execution.</p><ul><li><p><strong>Invest</strong> — early capital for ideas we believe in</p></li><li><p><strong>Build</strong> — internal R&amp;D and hands-on support for projects in motion</p></li><li><p><strong>Accelerate</strong> — launch strategy, token design, KOLs, exchange access</p></li><li><p><strong>Scale</strong> — help teams grow with context, not just capital</p></li></ul><p>We’re here early, and we stay close.</p><p>That’s the structure we’ve built around.</p><p>thesis, showing your conviction in AI × crypto, and ending with a natural invitation to builders.</p><hr><h2 id="h-why-crypto-needs-ai-and-why-ai-might-need-crypto" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Why Crypto Needs AI (and Why AI Might Need Crypto)</h2><p>We don’t think crypto needs AI just to sound futuristic.It doesn’t need a chatbot bolted onto a token dashboard.</p><p>It doesn’t need prompts wrapped around smart contract audits.</p><p>But when you flip the question — <strong>what could AI do if it had crypto infrastructure?</strong> — things get more interesting.</p><p>Most people still think of AI as text generators. But the real shift is toward systems that can act.</p><p><strong>Agents</strong> that make decisions, manage tasks, interact with protocols, and coordinate across networks.</p><p>Systems that don’t just analyze — they operate.</p><p>To do that, AI needs a few things:</p><ul><li><p><strong>Stablecoins</strong> to hold and move value</p></li><li><p><strong>Smart contracts</strong> to trigger execution</p></li><li><p><strong>Wallets</strong> to manage identity and permissions</p></li><li><p><strong>Protocols</strong> to serve as composable backends</p></li><li><p><strong>Data</strong> that is verifiable and accessible</p></li></ul><p>Crypto provides those rails.Without them, AI agents stay stuck in sandbox mode.With them, they become autonomous economic actors.</p><p>That’s the kind of future we’re building toward.</p><hr><h2 id="h-what-needs-to-be-built" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What Needs to Be Built</h2><p>Today’s infrastructure wasn’t designed for autonomous systems.</p><p>We still rely on dashboards, multisig approvals, and manual interactions.Agents don’t have standardized permissions, access models, or a unified execution layer.</p><p>If we want agents to act on behalf of users — move tokens, vote in DAOs, bridge assets, subscribe to services — we need to rethink how value and logic are structured on-chain.</p><p>There’s no shortage of ideas. But the infrastructure needs work.</p><p>That’s where we focus:</p><ul><li><p>Wallet-level agent permissioning</p></li><li><p>Execution frameworks that don’t rely on humans-in-the-loop</p></li><li><p>SDKs that abstract complexity</p></li><li><p>AI-native data layers</p></li><li><p>Protocols designed to be composable and machine-readable</p></li></ul><p>We’re building and backing the teams working on these problems.</p><hr><h2 id="h-where-were-active" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Where We’re Active</h2><p>Some of the projects we’ve supported — like <strong>Hybrid</strong>, <strong>Bubblemaps</strong>, and <strong>Aethir</strong> — are pushing in these directions.</p><p>In each case, our role has varied: sometimes as investors, sometimes as advisors, sometimes as embedded support.</p><p>But the throughline is always the same: early, focused, and aligned.</p><p>We’re not looking for momentum plays.</p><p>We’re looking for infrastructure that unlocks new capabilities — for AI, for agents, and for users.</p><hr><h2 id="h-what-we-look-for" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What We Look For</h2><p>We don’t care much for hype.</p><p>We care about leverage.</p><p>And leverage usually looks quiet at first.</p><p>We back teams with technical depth, a long view, and a bias toward systems thinking.</p><p>People who want to build things that run without them.</p><p>Founders who are less interested in announcements — and more interested in coordination, scale, and autonomy.</p><hr><h2 id="h-why-now" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Why Now</h2><p>AI is moving fast. Crypto is still maturing.The window to connect the two — in a way that doesn’t get captured — is open, but not forever.</p><p>Without the right rails, we get more silos.</p><p>More centralized orchestration.</p><p>More “AI as a service” — but never really yours.</p><p><strong>Crypto offers something different:</strong></p><ul><li><p>Ownership</p></li><li><p>Programmability</p></li><li><p>Interoperability</p></li><li><p>Trustlessness</p></li></ul><p>But it’s only useful if we build the right bridges now.Before someone else builds a version you don’t control.</p><hr><h2 id="h-to-the-builders" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">To the Builders</h2><p>If you&apos;re building something real — something protocol-level, agent-facing, or automation-first — let’s talk.</p><p>Whether you’re ten commits in or mid-launch.<br>Whether you need capital, context, or just someone to think through the hard parts with you.</p><p>This is what we care about.<br>And we’re building for the long game.</p><hr><p><strong>Current Ventures</strong><br><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="mailto:hello@currentventures.xyz">hello@currentventures.xyz</a> <br><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://currentventures.xyz">https://currentventures.xyz</a></p>]]></content:encoded>
            <author>current-ventures@newsletter.paragraph.com (Current [Ventures])</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/91eadb31bc9ef58d0eab57d60e430f19bc3810da6b21aca2864bddedcc9726b0.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>