TRU - Uni v3 Liquidity

Summary:
Fyde integrated TRU into its liquid vault earlier this year when there was sufficient Uni v3 liquidity and a reliable price oracle.

Currently, we are sitting with around $100k in TRU deposits which are now quarantined as we can not price TRU reliably. If we are unable to price TRU, we can no longer support it in our vault and will need to sell out of the position. This is not the ideal scenario.

Our protocol uses Uni v3 TWAP oracle to price assets in the vault effectively. Recently TrueFi removed available Uni v3 liquidity leading to an oracle error which forced us to quarantine the asset.

We would like to continue supporting TRU and request that Uni v3 liquidity be increased to make the oracle more reliable.

Implementation:
Deploy 100k WETH and 100k TRU into the TRU/ WETH Uni v3 Pool.

Benefits
Concentrated liquidity.
Improved price oracle.
Flexible fees.

Considerations
The position needs to be actively managed.

3 Likes

This is the only existing external utility for $TRU token.

It is imperative for either DAO to provide liqudity via “Liquidity Multisig” model or for community members to deploy Univ3 positions.

2 Likes

Hi @the.root

Please note that TrueFi is currently undergoing an important governance revision.

1 Like

Hey @kaimi
Just thinking for the easiest route forward do you perhaps know a couple of community members who could be open to adding to the pool?

Thanks @StrategoHoldings, I understand this is not the best time to take things further through governance. Will keep an eye on governance revisions.

1 Like

@the.root is it technically possible for Fyde to Integrate stkTRU tokens instead of TRU tokens and peg stkTRUprice to the price of TRU within Fyde. As its already currently pegged, not sure if needs pegging from Fyde side.

1 Like

stkTRU is not possible - it is not transferrable.

1 Like

Well, Fyde will just have to delist TRU and sell all of it if someone will not start to LP very soon.

1 Like
1 Like

IMO Deploying 200k of resources for a 100k token allocation seems a little out of balance. Going forward, what do you expect TRU TVL to be on your platform if this is implemented?

2 Likes