Skip to content
This repository has been archived by the owner on Sep 26, 2024. It is now read-only.

Roll back the detailed balances on Explorer in favor of Wallet Profile link #464

Closed
3 of 5 tasks
frol opened this issue Oct 30, 2020 · 1 comment · Fixed by #494
Closed
3 of 5 tasks

Roll back the detailed balances on Explorer in favor of Wallet Profile link #464

frol opened this issue Oct 30, 2020 · 1 comment · Fixed by #494
Assignees

Comments

@frol
Copy link
Collaborator

frol commented Oct 30, 2020

Story

Based on the discussion here: #463

We decided to take a step back on the Explorer side to avoid the rabbit hole we can get trying to pull out all the balances the account may have in various contracts. Instead, Explorer is going to focus on the native NEAR network features and Wallet will provide the user-facing breakdown and control over the assets.

Acceptance Criteria

  • Account Details page only contains the Non-staked balance, Staked Balance, and Minimum Balance UPD: @khorolets and I decided to avoid any balances on Explorer side and only provide the link to Wallet Profile
  • Minimum Balance should be visually linked with the Storage Usage (since Minimum Balance is computed based on the Storage Usage and storage amount per byte) UPD: see above
  • There should be a link to the Wallet Profile page (`$[nearWalletProfilePrefix]/$[accountId]` -- add nearWalletProfilePrefix to the NEAR_NETWORKS configuration [let @frol know if you need help with understanding that configuration setup])
  • The link to the lockup account should remain (obviously, only when the lockup account exists for the account)
  • The lockup balances should be removed (we have issues with keeping them up to date, so we decided to contentrate our efforts on Wallet Profile page)
@frol frol assigned khorolets and unassigned icerove Nov 30, 2020
@frol frol changed the title Roll back the details balances on Explorer in favor of Wallet Profile link Roll back the detailed balances on Explorer in favor of Wallet Profile link Dec 3, 2020
@frol frol added Priority 1 and removed Priority 2 labels Dec 3, 2020
khorolets added a commit that referenced this issue Dec 4, 2020
@khorolets
Copy link
Member

@frol could you update Acceptance Criteria as we've changed them on the fly?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants