Proposal #11: v0.5 Frontend code updates and upgrades

This proposal introduces updates and upgrades to the frontend (β€œUI”) of the Panther Protocol version 0.5, known as Advanced Staking. A comprehensive list of the introduced changes can be found below in the Annex.

Background

Through PIP-9 and PIP-10, the Panther Protocol version 0.5 was deployed and activated. After the launch of version 0.5, users witnessed minor frontend (UI) related issues. After the launch, contributors to the Protocol prepared, tested and published source code of the new frontend version that resolves found issues and optimizes performance.As discussed by the community on the Panther’s Discourse forum, the community recommends using the v0.5 upgraded frontend instead of the previous one.In order to have a user-friendly URL pointing to the v0.5 upgraded frontend, and also to safeguard access to the correct link/app, the community requests and makes a recommendation to configure the pantherprotocol.eth ENS domain namespace in such a way that the user-friendly link https://ipfs.io/ipns/pantherprotocol.eth will point to the v0.5 upgraded frontend (dApp) deployed frontend.

Proposed actions

The following action(s) are proposed:

  1. Allocate the unused 2,000 $ZKP out of 4,000 $ZKP previously allocated in accordance with the PIP-9 for front-nd deployments, to be used for rewards to a community member who will have build and deploy the v0.5 upgraded frontend on IPFS.

  2. Configure the PantherProtocol.eth ENS domain namespace so that the URL https://ipfs.io/ipns/PantherProtocol.eth will point to the v0.5 upgraded frontend (UI) deployed on IPFS.

Participation

Please vote to accept or reject the proposed actions detailed above. Voting power is calculated by Snapshot taking a Snapshot of the number of $ZKP tokens staked per holder at the block within which the proposal was created.

Annex: Frontend updates

Following changes are introduced by the new frontend (dApp) version:

  • Optimize UI performance if multiple stakes (40+) are created by a user.

  • Correct the broken layout for the AssetsCardRow on mobile.

  • Show an error notification card when there is an error refreshing the balance.- Show APR when the user is disconnected.

  • Correct Balance card layout, when the user is disconnected.

  • Correct the link on the Staking page/ Staking tab/Privacy Reward Points field tooltip and introduce other text fixes for clarity.

  • Update the MATIC balance upon the refresh button push. The source code is available on GitHub.

Full proposal details

The full details of this proposal are visible in raw Markdown format on IPFS.

Snapshot

PIP 11 Snapshot.

Last updated