Turtle Glossary
Key terms and definitions across the Turtle platformCore Users and Entities
Liquidity Provider (LP) Turtle’s userbase is made of liquidity providers who deposit into the selected list of vaults and liquidity campaigns brought by the Turtle network. Organization An organization describes a partner protocol, service provider, or distributor within Turtle’s ecosystem. Client (or Partner Protocol) Clients make liquidity campaigns with Turtle to attract liquidity by offering a combination of liquidity campaigns and/or leaderboards. Distribution Partner Partners who distribute liquidity campaigns on their frontend and earn revenue for the liquidity they provision. TurtleDAO The decentralized autonomous organization that encompasses all token holders, partners, users, and builders. Controls the treasury and protocol governance. TurtleDAO Treasury The protocol’s reserve of interest-bearing and yield-generating assets accumulated from partner protocol contributions and fees. Turtle.Club Association The legal entity (Swiss Verein in Zug) that operates the protocol and executes governance decisions.Products & Offerings
Webapp Turtle’s LP interface for liquidity management, depositing, diligence, and $TURTLE token management. Partner Portal Also known as the Client Portal or Dashboard, the Partner Portal encompasses Turtle’s B2B offering and includes incentive tools, distribution tools, outreach tools, and admin functions. Incentive Tools Turtle offers protocols incentive tools to attract liquidity. These tools include Products, Liquidity Campaigns, Streams, and Leaderboards. All tools include customizable parameters to define a campaign that meets their needs. Distribution Tools The distribution suite offers partners a dashboard and toolkit for those who want to earn a revenue share by attracting liquidity for Liquidity Campaigns. They do this by sharing a distributor link or integrating directly in their own frontend. Outreach Tools Turtle’s outreach tools include Turtle Chat, Turtle LP Search, Drip Campaign, and Turtle CRM. Product A Product details the high-level information of a liquidity offering. Products define the top-line explanation for a liquidity campaign and can hold one or more liquidity campaigns. Opportunity An Opportunity is a selected liquidity campaign, vault, smart contract, or token that generates rewards for LPs within the Turtle network. Leaderboard Turtle’s liquidity leaderboard offers a gamified UI that encourages LPs to compete against the rest to earn top place. These leaderboards often include customizable boosts for auxiliary activities, and they distribute extra incentives on top of the daily rewards included in a given opportunity. API Boost (Turtle Boosts) Turtle’s first core product. Structures additional token/point shares for Turtle users based on aggregate incentives, tracked via APIs and on-chain indexed data, without additional trust assumptions. Yield Opportunities Automated yield products that pool assets and route them into desired chains, markets, and dApps via selected infrastructure partners. Turtle Campaigns (Ecosystem-as-a-Service) Helps clients tap into Turtle’s network of stakeholders to structure ecosystems, lower cost of capital, and align stakeholders. Earn SDK A white-label product that allows distribution partners to showcase Liquidity Campaigns on their own frontends and earn a revenue share on user liquidity volumes. Attribution The process by which deposits are linked on-chain to the distribution partner that sourced them. Attribution is automatic and requires no manual reporting from the partner. Distributor ID / Distributor Link The unique identifier or referral link used by distribution partners to track liquidity they bring and earn revenue share. Liquidity Campaigns Selected yield opportunities available through the Turtle protocol. Each liquidity campaign has completed a TDC review and carries a published diligence report. Turtle Due Diligence Council (TDC) An independent body established to bring structured review standards to vaults and liquidity campaigns on the Turtle protocol. Where a TDC review has been completed a written diligence report is published. The TDC is actively expanding its coverage across the protocol.Incentives & Yield
Incentives Covers the span of rewards distributed for LPs to generate yield, including points, tokens, native yield, and additional rewards. Native Yield Comes from fees generated via protocol activity (like lending and trading). Additional Rewards Often defines a point or token reward distributed by a protocol. Streams A new way to distribute and track points or tokens directly via the Turtle platform. The system utilizes both onchain and offchain systems to define user holdings and USD value of specific ERC20 token contracts on a 12-hour basis. Liquidity Repurposing The ability for LPs to generate multiple contributions with the same liquidity by deploying across multiple partner protocols, triggering additional rewards at each layer. Turtle Referral Code Referral links that earn additional Turtle points for both the referrer and the referred LP.Streams Terms
These expand on the brief Streams entry under Incentives and Yield. For the product walkthrough see Streams Overview, and for request formats and parameters see the Streams API reference. Stream One incentive campaign. A stream pays a reward token or points to liquidity providers for the TVL they contribute or the deposits they commit, tracked continuously. A partner configures a stream once (reward base, reward type, mechanic, target, rate, duration) and LPs accrue and claim against it for its lifetime. “Campaign” is an acceptable synonym. Reward Type What a stream pays for, chosen at creation: TVL-Based (pays by token value held — holders earn continuously against their balance), Deposit-Based (pays by deposit characteristics — rewarding how long depositors commit through duration tiers that unlock at cliffs), or Airdrop (a one-time distribution defined by a recipient list). Older material may call deposit-based streams “Deposit Vesting” or “Vesting Bonus”. See Choosing a Reward Model. Mechanic (Stream Type) The rule that decides how much each LP earns within a reward type: Fixed Rate (tokens per 1,000 USD of TVL per day), Fixed APR (an annualized percentage converted to tokens at each snapshot), Daily Budget (a fixed daily pool split pro-rata), and the gap-fill rates Target APR and Reference APR. Deposit-based streams set their rate per duration tier. The mechanic is chosen at creation. See Choosing a Reward Model. Cliff The end of a duration tier’s window in a deposit-based stream. Each tier covers a consecutive window measured from the deposit, pays its rate over that window, and its rewards become claimable only at the cliff. Cliffs run in series and there is no mid-cliff claiming. Target Token The token whose on-chain balance is tracked to measure each wallet TVL contribution. The indexer watches holders of the target token, and the size of a wallet position determines its share of rewards. This is distinct from the reward token. Target tokens are supported on a broader set of chains than reward tokens. Reward Token The token actually paid out to LPs. For token streams this is a real ERC-20 transferred on-chain at claim time. Reward token selection at creation is currently supported on Ethereum, Base, Avalanche, BSC, and Sepolia, and the token must be an allowed reward token. Token Stream A stream whose rewards are a real ERC-20. The creating wallet holds enough of the reward token to cover the total plus the creation fee, and submits an on-chain createStream transaction to the StreamFactory. A stream is either token-based or point-based, never both. Point Stream A stream that pays off-chain points rather than tokens. Point streams are created instantly with no on-chain step, and points can convert to tokens at a future TGE. See Create a Point Stream. Snapshot A saved record of each wallet accrued rewards at a point in time. The reward updater writes snapshots so that accrual is preserved and auditable, and the latest snapshot is what gets committed on-chain. Reward Updater The off-chain job that computes accrued rewards. It runs about twice per day, reads each wallet TVL contribution and the stream rate, and saves the result as a snapshot. Computing rewards off-chain keeps stream types flexible while on-chain commitment keeps them verifiable. Merkle Root A single hash that summarizes the latest snapshot of all wallet balances. Turtle commits the Merkle root on-chain roughly every 12 hours, which makes the distribution verifiable without storing every balance on-chain. Merkle Proof The data an LP submits to prove their entry is part of the committed Merkle root. The proof lets the Stream contract confirm an amount is owed and release it. See Get Merkle Proofs. Cumulative Amount The total an LP is owed since the stream began, not the delta since their last claim. Because amounts are cumulative, a single claim transaction always pays the full outstanding balance and there is no need to claim from every snapshot. StreamFactory The on-chain contract that deploys a new Stream contract for each campaign. It also supports batch and delegated claiming. New chains go live by deploying a StreamFactory and configuring an indexer webhook. Contract addresses per chain are in Create a Stream. Stream Contract The per-campaign contract deployed by the StreamFactory. Each one holds its own funds, accepts Merkle root commitments from a restricted backend role, and exposes a permissionless claim that anyone can call to pay an owed LP. AccessManager The contract, owned by the Turtle multisig, that gates all admin operations across the Streams contracts. It is the control point for privileged actions. The contracts were audited in January 2026; see Audits. Boost Plugin (Adapter) An optional rule applied between base reward computation and the final Merkle tree to adjust who earns and how much. Six are live: Turtle User, X (Twitter), Telegram, Whitelist, Blacklist, and Forwarder. Plugins are configured through the adapters array; see Create a Stream. Forwarder A boost plugin that forwards rewards earned by a vault address to the underlying LPs of that vault, for example a Euler Earn Vault. It is used when the holder of the target token is a contract rather than the end depositor. Target APR A gap-fill mechanic. You set a target APR and the stream pays only the difference between that target and the vault’s native APY, measured against a trailing average over a lookback window (7 days, 1 month, 3 months, or 6 months) — a vault yielding 4 percent against a 4.75 percent target pays the gap, and a vault that meets or beats the target pays nothing (the boost is never negative). Supersedes the earlier names “Yield Floor” and “Guaranteed APR”. In the API it runs under theYield Match type with targetApy set. See Choosing a Reward Model.
Reference APR A gap-fill mechanic that tracks another vault’s rate plus an optional offset, paying only the shortfall between that reference and the target’s native yield. Supersedes the earlier name “reference rate” for this mechanic. In the API it runs under the Yield Match type with targetApy unset and an optional apyOffset. See Choosing a Reward Model.
Yield Match The API-level type (type = 5) under which both gap-fill mechanics run: Target APR (with targetApy set) and Reference APR (without). The configuration is locked at creation. See Create a Stream.
Claim The action an LP takes to receive owed rewards. The LP submits a Merkle proof to the Stream contract, which verifies it against the committed root and releases the tokens. Claims can be made anytime and are cumulative, so one transaction settles the full balance. See Claim Rewards.