A comprehensive list of the introduced changes can be found below in the Annex.
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 front-end (UI) related issues. After the launch, contributors to the protocol prepared, tested and published source code of the new front-end 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 front-end instead of the previous one.
In order to have a user-friendly URL pointing to the v0.5 upgraded front-end, 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 front-end (DApp) deployed front-end.
The following action(s) are proposed:
Allocate the unused 2,000 $ZKP out of 4,000 $ZKP previously allocated in accordance with the PIP-9 for front-end deployments, to be used for rewards to a community member who will have build and deploy the v0.5 upgraded front-end on IPFS.