Skip to main content
$TURTLE is the utility token that powers the Turtle liquidity protocol, aligning users, partners, and contributors under a shared network of onchain liquidity distribution. At launch, holders can stake TURTLE for sTURTLE, gaining the ability to delegate and vote on governance proposals that shape the protocol’s future. Core Utility
  • Governance: stake TURTLE → receive sTURTLE → delegate or vote directly on proposals.
  • Contribution Incentives: receive token grants or rewards for verifiable liquidity contributions and integrations.
  • Alignment Mechanism: demand for influence and participation drives TURTLE’s core utility across the network.
Value Drivers
  • Governance Demand: holders seeking to influence treasury management, protocol direction, and integrations.
  • Ecosystem Growth: incentives for contributors, LPs, and partners participating in campaigns and integrations.
  • Network Effects: as the protocol routes more liquidity, demand for influence and participation naturally increases.
Future Utility At launch, $TURTLE functions primarily as a governance and alignment token. Over time, its utility will expand based on community and governance decisions to reflect the evolving needs of the Turtle ecosystem. Future utilities may include:
  • Expanded access to liquidity opportunities
  • Fee discounts and yield boosts across core products
  • Protocol buybacks or redistributive mechanisms
  • Enhanced staking tiers and governance modules
Ultimately, governance will define the future of $TURTLE, shaping how it evolves to sustain alignment, value, and long-term participation across the network.

Governance System

Purpose

Turtle governance will use Tally’s tooling to simplify the governance process. To begin, the system will use the out-of-the-box governance framework provided by the Governor contract. Find all details below. The governance system for Turtle focuses on keeping the network aligned with the best interests of its stakeholders.

Stakeholders

Turtle governance entities include a variety of stakeholders with different functions, powers, and responsibilities.
User Types:
  • TURTLE Holders – holders of the TURTLE token. These users have the opportunity to stake for sTURTLE and delegate their stake to themselves or a qualified delegate.
  • sTURTLE Holders – holders who have staked their TURTLE. These users still need to delegate to themself or a Turtle delegate to activate their voting power.
  • Turtle Delegates – any user on the Internet can sign up to Tally and campaign as a Turtle Delegate. These users can delegate sTURTLE to themself, or campaign to gather delegated voting power from others.
  • Turtle DAO – the Turtle DAO includes the larger network of all token holders, partners, users, and builders.
  • Turtle Core Team – Due to the nature of the protocol, Turtle’s Core Team will be responsible for implementing governance decisions as they progress through the process.
  • Canceller – the address associated with the power to cancel a proposal in the governance system.

Process

  1. Creation: Turtle delegates with the defined limit (proposalThreshold) of sTURTLE voting power have the opportunity to create governance proposals. 
  2. Voting: once a proposal voting process begins, a snapshot of all sTURTLE holders and amount of sTURTLE in circulation defines the weights of all voting participants and the quorum amount needed to pass.
  3. Execution: due to the nature of the protocol,Turtle’s governance leverages onchain voting and offchain execution by Core Team or Foundation to enact.

Voting Parameters

The governance contract utilizes Open Zeppelin’s Governor contract. Token holders will be able to stake any amount of TURTLE to receive sTURTLE and then must delegate to utilize their voting power (note: sTURTLE holders can self-delegate if they want to vote on their own). Once a delegate is chosen, the address commits their total sTURTLE voting power to that delegate. If the user delegating their vote increases or decreases their staked amount, the sTURTLE voting power given to their delegate will change accordingly. Parameters:
  • Proposal threshold (1.5M)
This is the minimum amount of voting power a user must be delegated in order to create a proposal. If someone does have sufficient power delegated to them, they cannot submit a proposal to be voted on. Quorum (4% of sTURTLE) This defines the minimum number of votes that must be cast for a proposal to be considered valid. If the quorum is not reached, the proposal fails regardless of the voting outcome. Voting delay (4 days) This defines the waiting period between when a proposal is created and when voting can officially begin. It ensures that all community members have time to review the proposal before voting starts. Voting period (2 weeks) This defines the duration during which Turtle delegates can cast their votes on a proposal. Once this time expires, the voting ends and the outcome is finalized. Timelock Delay (NA) The timelock delay is the minimum amount of time between when a proposal passes and when it can be executed. This parameter is only relevant for proposals that require onchain execution. 
I