balancer/frontend-v1

Specific pool having an issue

Closed this issue · 1 comments

Expected behavior

Load the details of pool 0xa1Ec308F05bca8ACc84eAf76Bc9C92A52ac25415

Actual behavior

Has some kind of error and keeps spinning the loading circle forever.

Steps to reproduce the behavior

Visiting https://pools.balancer.exchange/#/pool/0xa1ec308f05bca8acc84eaf76bc9c92a52ac25415/ or searching for the pool in the pool explorer and then clicking it.

Thanks for the report, @jnapier-code! This is one of the broken TRB pools. See here for more info: https://twitter.com/WeAreTellor/status/1361390854578053122?s=20

What's happening is that it's impossible to load token data (name, symbol, decimals) from the TRB proxy contract because the implementation contract is not a token; it doesn't have any of these getters. I do consider it an issue that the UI spins forever in this case instead of just giving up and displaying N/A. However, we don't have much time to devote to V1 UI fixes right now, and arguably it doesn't do anyone any good to interact with these broken pools.

Tellor is migrating TRB to a new contract, and they are helping users to migrate their liquidity to new TRB tokens. They are covering the full value of the liquidity pool with newly minted TRB. For example, this pool contains 10% TRB, so if you have 100 old TRB locked in the pool, they will mint 1,000 new TRB and trade you for your BPT. Your only alternative is to try to withdraw single-asset liquidity from this pool (because you can't move the old TRB). This might get you more value depending on the price of TRB in the pool, but it is a game of musical chairs with high slippage which disadvantages those who withdraw last. Migrating is the most predictable move for all LPs. Read more here: https://medium.com/tellor/trb-migration-fd8ebe320b02