Turtle

Staking → governance power: Holders stake TURTLE to receive sTURTLE, which carries voting and delegation rights. Proposal creation requires meeting a defined sTURTLE threshold; votes are counted against a published quorum, with a time-boxed delay before voting starts and a fixed voting period.

Policy & parameter setting: sTURTLE is used to approve or reject protocol upgrades, configuration changes, integration parameters and programme allocations that shape how liquidity campaigns are run.

Access to participation features: Stakers gain access to governance interfaces (proposal creation, signalling, delegation management) and to gated, non-financial utilities that improve coordination (e.g., allowlists for pilots, advanced dashboards, contributor workflows).

Ecosystem coordination: TURTLE powers the rules by which the protocol tracks wallet-level activity and recognises contributions across supported chains and integrations, enabling fair distribution frameworks for campaigns and partner programmes.

Non-financial nature of utilities: Holding or staking TURTLE does not confer ownership of the protocol entity, profit-share, fee rights, redemption rights, guarantees of value or counterparty obligations. Any financial rights would require explicit future introduction via governance and contract changes.

Operational model: The protocol is non-custodial. Liquidity remains in users’ chosen venues; Turtle focuses on integrations, attribution and governance rather than holding assets.

Security & operations: Contracts use established standards (ERC-20/BEP-20) with an audited governance stack. Multisig/DAO controls are disclosed, and external audits are planned/published via official channels. Cross-chain operation is supported through interoperability tooling, with deployments on Ethereum, BNB Smart Chain and Linea enabling consistent attribution and governance across supported networks.