snowball-finance/app-v2

app-v2's Issues

Enable Dark Mode

Currently some of our users are requesting dark mode on our website, we had one but disabled before the launch because it was not working correctly, the idea is to reenable it and make any changes needed for this to work.

[IMPROVEMENT] Add staking/unstaking QoL features

Add quality of life features to staking and unstaking into vaults, which will save a lot of users a lot of time:

1. Allow for partial withdrawals of vaults. This is useful for anyone trying to DCA their position out gradually
2. Allow for adding extra LP to vaults you are already in. This is useful for anyone trying to increase their position -- this is done now

When a wallet's pairs are retrieved, entered filters are invisibly reset

Tested on main and last dev build
On the compound and earn screen, the pairs can sometimes take quite a while to load.
It is possible to set filters on the list of pairs, before the wallets deposited pairs are retrieved causes them to be selected but not applied:

Steps to recreate:

1. Navigate to compound & earn tab
2. Type into pairs search filter (e.g. WBTC)
3. <>
   => List is sorted with wallet pairs at top (i.e. the LPs that the user has entered), and any selected filters are not applied.

Either we should be clearing any set filters upon wallet pairs retrieved
-or-
We should be reapplying filters after pairs are retrieved

Add Lotties to the Project

Add support for lotties in the project so we can use it for animations in dialog modals for example.

Test

test

Add Sherpa Climb to the Top NFT Support

We need to ensure that the new Sherpa NFT can be buyable.

WalletConnect support

More and more dApps in the Avalanche Ecosystem

• https://www.traderjoexyz.com/
• Pangolin pangolindex/interface#160

and wallets

• https://steakwallet.fi
• Trust Wallet

are starting to support WalletConnect. Would be awesome for Snowball to support this method of connecting wallets too.

Distribution Phase is Outdated

Please drop the distribution phase portion on the website. It is outdated and doesn't match the current emissions model.

Snowball Logo on the sidebar is not a high resolution image.

We should change the Snowball logo to a high Resolution one, preferably SVG.

Change for Infinite Approval

Most of users ask for us to use infinite approval when depositing to avoid needless calls and gas fees.

PopupInfo details

We need to separate props for the PopupInfo.
Now we need title + message in a string, but we need separate in:

Title: Claim Error
Title of Message: Error Claiming from Gauge
Message: Metamask Tx Signature: User denied transaction Signature

Adittional data:
Link (If transaction success) : Check on C-Chain Explorer

Route read-only calls to Snowball private node

Snowball deployed a load balancer with private RPC Nodes connected to Avalanche Blockchain, we should use this nodes for the readonly calls so we can avoid the problems of using a public RPC like high traffic.

[Improvement] Wallet Amounts not polled

Wallet balances are either not being polled or maybe it is just very slow.
When a user clicks deposit

The available number there will be out of date unless a manual refresh is done. Likewise any available LP in wallet won't be able to be staked if it was received after the page has been loaded.

It would be quite handy, and less disruptive to the servers, if we didn't have to manually force a refresh quite so often. User refreshing the entire website just to get their updated balances is probably causing a lot more web traffic (and associated fees) than is otherwise needed

Total Earned LP

The idea is to track the LP value the user deposited in the pool and show the difference with the compounding effect, this involves Backend, I tried to do it using Covalent queries, it worked for recent positions, but older positions the logic was not applied, which make me think Covalent has some kind of a hole on their old Avalanche data.

This is a feature that we will only be able to do when we rework our API so we can get this kind of stuff by querying directly the blockchain blocks instead of relying in another API.

[MINOR] FRAX Icon's transparency makes S4d vault clipped

FRAX's transparent icon makes this vault look odd.

If this is intentional, feel free to close.

Add frontend Interface for sherpa airdrop

We should have a button on the staking page so the user claim their Sherpa airdrop from the IDO.

[MINOR] Font too large on claim modal dialog

Tested on Firefox with 100% scaling and default settings (not a 4k monitor or any HiDPI settings on).

As you can see it looks a bit out of place the body text on this message. When a global receipt is received it is cliped and off screen.

Retrying failed deposit race-condition

It is difficult to reproduce, but i've had it happen a few times that after one of the two deposit operations have failed, for any reason, subsequent attempts fail with a JSON rpc error:

message: "Error: VM Exception while processing transaction: reverted with reason string 'ERC20: transfer amount exceeds allowance'" .

Icon missing for Sherpa in governance voting

The sherpa-avax pool is missing the sherpa icon when choosing it for governance voting

[IMPROVEMENT] Add new QoL Claim features

Add some new quality of life changes to make claiming easier:

1. Having a claim all button, would save a lot of time
2. Having a claim button on collapsed vaults is helpful when trying to figure out which pool you left has residual SNOB inside
3. Automatically claiming when leaving a vault likewise will save time

Rejecting approval via MetaMask does not NACK operation on website

Clicking reject on the approve transaction screen in metamask is not reflected on the webapp.

The processing operation toast notification at the bottom and the deposit modal dialog both show in progress despite reject has been triggered by the plugin:

Note: This functionality is working as expected when doing deposit steps.

Performance Fixes > single staking context

We want to have just one context for the staking page to maintain our pattern, also we can cut a lot of contract calls from the staking context, that are being loaded on the page opening.
Instead we should use this specific contract calls only when they're needed.