Proposal to add TOR-2pool to the Gauge Controller

Gauge Proposal Template:

Proposal to add TOR+2pool on Fantom to the Gauge Controller to enable users to assign gauge weight and mint CRV.

Describe what this proposal is about

References/Useful links:

Link to:

• Website: (main) | For TOR (

• Documentation:

• Github Page:

• Communities:

• Other useful links?

Protocol Description:
TOR is a truly algorithmic stable coin built on the Fantom Opera Chain. It has a dynamic supply which is determined by supply and demand which ensures it is always worth $1.

TOR is a stable coin that drives the hector finance token HEC forward as the world’s first deflationary rebase token. Every time TOR is minted the supply of HEC decreases leading to a greater value of HEC which is the utility token for the hector ecosystem. To learn more about how TOR works, please check out this short video.

Describe the proposed asset(s), the corresponding protocol(s), and historic prices of the token (price must come from the source of highest liquidity).


Curve is the ideal DEX for stable coins, given its like-pair swapping curve, and is the natural next step for TOR on Fantom.

We believe that:

  • Adding an incentivized pool for TOR on Curve would allow us to address the growing demand for minting TOR.
  • It would also provide low slippage transactions for those leveraging with TOR.
  • Adding rewards to TOR liquidity on Curve would help increase access to liquidity for native fantom assets.

Currently, TOR farm has reached $40M+ TVL and continues to grow. As a result, TOR would bring significant additional volume to Curve Fantom and create value for CRV holders.

Explain why this pool needs incentivization


You can view analytics for TOR on Defillama as well as our analytics page. To learn more about the protocol, please visit our official docs and our community.

Please answer in a short and clear manner.

  1. Governance: Provide current information on the protocol’s governance structure. Provide links to any admin and/or multisig addresses, and describe the powers afforded to these addresses. If there are plans to change the governance system in the future, please explain.
    Currently the code of all smart contracts has been placed under the multisig wallet on FTM (0x814750C7E8b575B2B3Da0D2F90eB689a1d665eB0). We do have a plan for a governance contract to vote for updates of the parameters for the protocol.

  2. Oracles: Does the protocol rely on external oracles? If so, provide details about the oracles and their implementation in the protocol.

  3. Audits: Provide links to audit reports and any relevant details about security practices.
    Audit: Hector Finance - CertiK Security Leaderboard

  4. Centralization vectors: Is there any component of the protocol that has centralization vectors? E.g. if only 1 dev manages the project, that is a centralized vector. If price oracles need to be updated by a bot, that is a centralized vector. If liquidations are done by the protocol, that is also a centralization vector.
    No. The dev team consists of 4 developers and the ownership of all smart contracts is placed under the multisig wallet.

  5. Market History: Has the asset observed severe volatility? In the case of stablecoins, has it depegged? In the case of an unpegged asset, have there been extreme price change events in the past? Provide specific information about the Curve pool: how long has it been active, TVL, historical volume?

Current TVL of TOR-2pool: 30million

You can also review the growth of TOR and our Curve Gauge DAI+USDC from links below: DAI+USDC RewardGauge Deposit

TOR Growth