• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
TarotTarotby0x5b0390bccCa1F040d8993eB6e4ce8DeD937217650x5b03…1765

TIP-008: Incentivize Ghost Reveries on Beethoven X

Voting ended about 4 years agoSucceeded

Author(s): @TigrisOfGaul

Summary

This proposal seeks to incentivize fBEETS holders to vote for Ghost Reveries (TAROT-FTM), the 80/20 weighted pool on Beethoven X.

Abstract

If adopted, this proposal allocates 25,000 TAROT and 5,000 USDC to incentivize fBEETS holders to vote for Ghost Reveries (TAROT-FTM). Ghost Reveries is the 80/20 weighted pool for TAROT/FTM on Beethoven X. The goal is to incentivize LPs to provide TAROT/FTM liquidity on Beethoven X with BEETS rewards.

The proposed incentivization model would allocate TAROT and USDC only to fBEETS holders who vote 100% for Ghost Reveries (TAROT-FTM) in the gauge vote. This novel approach mitigates whale vote-splitting and, at the same time, serves to reward true believers in Tarot.

Note: The gauge vote proposal for Beethoven X pools is ongoing and ends on February 20, 2022 at 5:00 PM GMT. You can find the proposal, and vote for Ghost Reveries, here:

  • Farming Incentive Gauge Vote (Round 4)

Motivation

There are many benefits to incentivizing TAROT/FTM liquidity on Beethoven X:

  • Creates an effective single-staking option for TAROT, which earns swap fees and BEETS farming rewards
  • Creates an additional venue for arbitrage opportunities, which rewards FTM-TAROT LPs across all DEXes with increased trading activity and swap fees
  • Strengthens our partnership with Beethoven X

A future proposal may seek to allocate liquidity to Ghost Reveries on Beethoven X. This would diversify Tarot protocol-owned liquidity, with passively-held TAROT and FTM used to generate additional rewards for the benefit of xTAROT holders.

Specification

Should we incentivize Ghost Reveries (TAROT-FTM) on Beethoven X?

Off-Chain Vote

Yes, incentivize Ghost Reveries
585.13K 89.6%
No, do not incentivize
68.09K 10.4%
Download mobile app to vote

Timeline

Feb 19, 2022Proposal created
Feb 19, 2022Proposal vote started
Feb 20, 2022Proposal vote ended
Oct 26, 2023Proposal updated