Long loading times or not loading (Staking.wetrust.io)

[bagelcodr]

The section for "Most Staked Causes" and "Nominated Causes" continually shows the moving loading circle as in the picture above. This is likely because I am using Safari (no Metamask). Possibly a UX issue, we should instead notify the user that they are using Safari and it's not supported

On Chrome with Metamask, it took about 5-6 minutes to load

For this section, i know that it is currently waiting for the minimum verifications on Ethereum network, but for the average user they might not know (the loading circle is usually for internet connection, slow computer, etc).

We should change this to give some indicator such as "Waiting for minimum x verification on the network". Maybe include something like, "Slow wait times? Ethereum network might be congested." Check your tx (here) or check the ethereum network status here (https://etherscan.io/txsPending)

@yutai-trst what do you think about the UX stuff? (also applies to Crypto Unlocked when making a contribution)

[yutai-trst]

We have a lot of thoughts already documented on the subject.

For the staking hub, and for CryptoUnlocked, the priority had been placed on expediency of engineering execution.

For the staking hub, i think it might be ok to let that be for a minute while we see its overall interest from the ETH saavy. That makes sense since users who are not that familiar with MetaMask transactions are not very likely new users to the staking hub.

For contributing, it is definitely worth going back to examine the blockchain user flow now that the initial pushes are getting finished.

[sihoang]

There are two parts that slow:

1. The "write to blockchain" operations (i.e. Stake Now and Claim). We cannot do much because it relies on the network, gas fees and miners. Normally, dapps just thank users and tell them to come back later.

2. The "read data from blockchain" operations (i.e Leaderboard, Your Stakes). The latest release v1.3.9 implements client-side caching and enhances the data loading process. It's a lot faster after the first visit. On first visit, it'll take quite a bit to cache but still faster than other version prior to v1.3.9