Runepool is an on-chain giveinfrastructure project that aims to connect pooled capital with autonomous AI agent execution, focusing on programmable liquidity, automated strategy runtime, and transparent on-chain settlement. The platform positions itself as a full-stack layer designed to autonomous strategies access to liquidity while managing funds and payouts via smart contracts. [1]
Runepool describes an infrastructure layer that bridges capital and execution for autonomous agents, with the objective of supporting persistent, on-chain strategy operation. The public materials emphasize three pillars: programmable liquidity provision to strategies from shared pools; continuous, automated execution without human intervention during runtime; and transparent, on-chain settlement with verifiable performance tracking. [1]
Published metrics on the project’s site (captured 2026-04-25) cite 5,000+ active strategies, 100+ integrated agents, and 15,000+ completed executions. The site also asserts smart-contract control over pooled funds and states that results are recorded and distributed on chain, but it does not provide contract addresses or detailed technical specifications in the captured content. [1]
Runepool’s described product set centers on enabling autonomous, agent-driven finance on chain. The platform’s core offerings include shared liquidity pools that provide capital to agent strategies; an execution environment to run such agents continuously; and on-chain settlement and performance tooling to record outcomes and distribute proceeds under smart-contract logic. Developer-facing components are indicated, with references to modular building blocks and a litepaper, though the litepaper was not included in the captured materials. [1]
In essence, the products aim to provide a lifecycle for agent strategies: request and receive programmable capital, operate autonomously with continuous execution support, and settle performance results transparently, all under an on-chain framework supervised by smart contracts. [1]
The platform features, as described by Runepool, include on-demand, programmable liquidity sourced from shared pools; continuous, autonomous execution designed to minimize or eliminate human intervention during active strategy phases; and transparent on-chain settlement with verifiable performance data. The architecture is framed as modular and composable, intended to accommodate different agent workflows and deployment patterns while maintaining smart-contract control over funds and automated capital flows. [1]
These features point toward an infrastructure that aims to decouple strategy development from capital acquisition and operational logistics. By concentrating liquidity in programmable pools and standardizing execution and settlement, the platform’s stated intent is to streamline how agents obtain and employ capital, while providing liquidity providers with a verifiable record of strategy performance. [1]
Runepool’s ecosystem is positioned around two principal participant groups. For developers, the platform aims to offer access to programmable liquidity, continuous execution, and composable components to assemble and deploy on-chain agent workflows, along with transparent settlement and performance monitoring. For liquidity providers, it aims to offer a way to allocate capital to autonomous strategies with smart-contract-managed custody and payouts, emphasizing visibility into on-chain performance. [1]
The described model implies interdependence between these groups: developers require pooled capital and standardized operations to scale strategies, while liquidity providers depend on the system’s automation and auditability to assess, fund, and be repaid by strategies. [1]
These use cases reflect the project’s focus on bridging capital and execution for agent strategies with on-chain settlement and monitoring. [1]
Runepool presents a modular, layered architecture comprising a funding layer (shared liquidity pools), an autonomous execution layer (continuous runtime for agent strategies that request and use capital), and a settlement layer (on-chain recordkeeping and distribution of proceeds), all coordinated under smart-contract management to control funds and automate flows. While the site asserts “full control” through smart contracts, the capture reviewed does not list contract addresses, supported networks, or detailed technical specifications. [1]
The funding layer is described as shared liquidity pools that aggregate user capital. Strategies request and receive allocation from these pools under programmable rules, positioning the system to channel capital dynamically to multiple agent workflows. This approach aims to support many strategies concurrently while centralizing risk management and allocation logic within the platform’s pool abstractions. [1]
The execution layer is framed as an environment where autonomous agents can operate continuously, with no human intervention during runtime. Agents are intended to access the pooled capital according to predefined parameters, execute strategy logic on chain, and report outcomes back to the settlement system. The objective is operational continuity—strategies run persistently, capital is made available programmatically, and system-level automation supervises lifecycle events. [1]
A settlement layer records performance outcomes and distributes proceeds on chain, with performance tracking positioned as verifiable by third parties. This layer uses smart contracts to enforce payout logic and to maintain an auditable trail of strategy actions and returns, aligning with the platform’s emphasis on transparent, on-chain accounting for both developers and liquidity providers. [1]
Runepool states that pooled funds are governed by smart contracts to enable automated capital flows and settlements. However, the captured materials do not include contract addresses, audit artifacts, or details regarding upgradability, key management, or role-based permissions. Those omissions limit external verification of specific control structures or security properties from the available sources. [1]
There is a separate, THORChain-native module called RUNEPool that differs in scope and implementation from Runepool (runepool.ai). RUNEPool is designed to allocate native RUNE deposits across all Protocol-Owned Liquidity (PoL)-enabled pools on THORChain, issuing RUNEPool Units (RPU) that represent proportional ownership of the aggregated exposure. It aims to create index-like exposure to RUNE plus PoL-enabled assets, with part of the position potentially held as standby RUNE to reduce impermanent loss at the expense of yield. [2]
The THORChain RUNEPool materials describe an index-style mechanism and associated accounting model, including ReserveUnits, PoolUnits, and PendingPoolUnits to track deployed and undeployed positions, as well as withdrawal guard logic “tied to network-level configuration that can prevent withdrawals under specified reserve conditions.” The module accepts only native RUNE deposits via specific transaction memos and exposes query endpoints for global and per-provider reporting. [2]
A complementary article states that RUNEPool is live on THORChain (as of July 31, 2024), supports single-asset entry in RUNE, and creates multi-pool Dual LP positions that diversify exposure across PoL-enabled pools. It also notes capacity constraints—deposits can remain pending when PoL capacity is unavailable—and a minimum deposit maturity parameter, initially equivalent to 90 days. The positions are described as “normal Dual LP deposit(s),” and deposits are “accepted only in RUNE on the THORChain network.” [3]
Across these THORChain sources, no operational tie, governance linkage, or formal integration is identified between THORChain’s RUNEPool module and Runepool (runepool.ai). The similarity of names can cause confusion; the available materials characterize them as distinct entities serving different objectives. [2] [1]
Runepool emphasizes the following operational characteristics. First, its liquidity is described as programmable and on-demand, suggesting capital can be allocated to strategies dynamically based on predefined conditions. Second, agent strategies are intended to run autonomously and continuously, reducing manual intervention. Third, settlement and performance are presented as on-chain and transparent, facilitating verification of outcomes by participants. Finally, smart-contract control of funds is highlighted, with automation handling capital flows and payouts. [1]
The platform’s materials underline composability across these characteristics, positioning the system to support varied agent designs and integration needs. However, in the absence of contract addresses, audits, or network details in the capture, external validation of these characteristics’ implementation specifics is not available from the listed sources. [1]
From an ecosystem standpoint, Runepool targets developers building autonomous agents and liquidity providers seeking passive exposure to agent strategy performance. Developers are promised access to pooled capital and continuous execution with transparent settlement reporting, while liquidity providers are promised smart-contract-managed custody and payout mechanisms with on-chain performance visibility. The ecosystem thus depends on standardized interfaces for agent capital requests, execution state, and settlement events. [1]
The balance of incentives is implicit: developers benefit from ready access to capital and infrastructure, and liquidity providers benefit from automation and transparency that ostensibly lower operational overhead and monitoring costs. The actual economic parameters—such as fee schedules, performance fee models, or risk controls—are not specified in the captured materials. [1]