casperdash / casperdash-web Goto Github PK

Is your feature request related to a problem? Please describe.
As the NFT Holder, I would like to

• List my NFT
• Buy NFT

Describe the solution you'd like
Suggested Wireframe: https://app.moqups.com/GuICw1vYeLN7ytRDAVQRvOknDWgbGLP6/view?ui=0

Describe alternatives you've considered
N/A

Additional context
N/A

Issue Description:

In the context of the CasperDash marketplace, it is essential to provide users with clear and informative information about NFT. Currently, the metadata for CEP47 tokens may not always include the name. To enhance the user experience and ensure transparency, it is advisable to implement a feature that displays the collection name instead of name even when it is not explicitly defined in the CEP47 metadata.

The objective of this task is to implement the functionality that allows users to add a token to their account or wallet, enabling them to view the balance of that specific token within their account or wallet interface.

Before confirming a transaction to send CSPR to another wallet, it is important to check your account balance to ensure that you have enough funds to cover the transaction.

Confirm that your wallet has been successfully locked. This security measure ensures that your funds and transactions are protected from unauthorized access. To unlock your wallet, you will need to enter your password or another authentication method, which will grant you access to your funds and allow you to make transactions or manage your wallet.

Front End

• Build staging version to staging.casperdash.io which configuring to mainnet ENV
• Testing core features on staging.casperdash.io
• After testing on staging, inform to community to replace current web wallet with totally new product
• Production release on https://wallet.casperdash.io/
• After release testing

API/SC

• Release API if anys
• Release SC to mainnet

• Add legacy key from casper signer
• Add/edit account from hd wallet

Allow dApps to use the CasperDash Web wallet to sign transactions.

1. Overview
   As a non-custodial wallet we aim to provide users with uninterrupted access to their funds and basic wallet functionalities, regardless of their internet connectivity.
   By leveraging PWA, the wallet can be transformed into an installable web application that offers offline capabilities, ensuring a seamless user experience and data security.

2. Requirement
   Users should be able to launch the wallet application and access their account details, transaction history even without an active internet connection. Users can also access their wallet details e.g recovery phrase, create new account, sign transaction...

Issue Title: Allow Users to Filter Your NFTs Listed on Marketplace

Issue Description:
As an NFT creator and seller on the CasperDash marketplace, I've encountered challenges in efficiently managing my own NFT listings. With the growing number of NFTs in my portfolio, it's becoming increasingly challenging to monitor, update, or make informed decisions about my NFTs. To enhance the user experience for NFT creators and sellers, I propose the implementation of a feature that allows users to filter and manage their listed NFTs based on various criteria.

Feature Request:

1. Filter by NFT Status: Users should have the option to filter their NFTs based on their current status, such as listed for sale, sold, or expired. This would help creators keep track of their active and past listings.

2. Filter by Category or Collection: Organizing NFTs by categories or collections will enable users to easily manage and update NFTs within specific themes or groupings.

3. Filter by Listing Date: Allowing users to filter NFTs by the date they were listed would assist creators in tracking the performance of recent additions and make necessary adjustments.

4. Search by Keywords: Implementing a keyword search function for one's own NFTs will help users quickly locate specific assets within their portfolio.

Description

This task focuses on enabling users to join an airdrop program effortlessly, obtain rewards, and ensuring the absence of any user tracking or data collection during the process. Implementing this feature will encourage user engagement and contribute to the growth and success of the project.

hi a @duc-q , after finishing the EF Journey. Please help to review the CD Web App UI/UX. Cheers!

Issue Description

Currently, our Casper wallet stores transfer history and staking history in two separate local storage keys. This creates unnecessary complexity and increases the chances of data inconsistencies. This issue aims to improve the wallet by consolidating the storage of transfer and staking history into a single local storage key for a more efficient and reliable experience.

Current Behavior

Transfer history is saved in local storage under the key transaction_histories, and staking history is saved under the key staking_transaction_histories.

Desired Behavior

We want to merge the transfer and staking history into a single local storage key named transaction_histories. This will make it easier to manage and ensure that the data remains consistent and synchronized.

Steps to Reproduce

1. Open the CasperDash web wallet.
2. Navigate to the "Transfer History" tab.
3. Navigate to the "Staking History" tab.

Additional Context

This improvement will not only simplify the codebase but also enhance the user experience by reducing potential data discrepancies. It will make it easier for users to access their complete transaction history in one place.

Local Storage Keys

• Transfer History Key: transaction_histories
• Staking History Key: staking_transaction_histories

Proposed Solution

We propose refactoring the wallet to use a single key, transaction_histories, for both transfer and staking history. This will involve code changes in the storage and retrieval of transaction data.

Acceptance Criteria

• The Casper wallet should successfully store and retrieve both transfer and staking history using the new transaction_histories key.
• The user interface should be updated to reflect the changes and display all transaction history accurately.

Issue Description:

In the CasperDash platform, there is a need to improve the user experience for managing CEP78 tokens. CEP78 tokens often have associated metadata that may change or need updating over time. To make it more convenient for users and token creators to refresh this metadata, it is essential to implement a "Refresh Metadata" button in the user interface.

The objective of this task is to implement the functionality that integrates with Liquid from FriendlyMarket

Hi @djhahe , plz help to contact CA presentative to request them to audit our Web App. If you need any helps from my side, please DM me.

Cheers,

Issue Description:
The transaction processing experience on the CasperDash marketplace is a critical aspect of the user journey, impacting both buyers and sellers. Currently, there may be pain points and inefficiencies that hinder users from conducting transactions smoothly. To enhance the overall user experience and foster trust within the platform, it is essential to address these issues and make transaction processing more user-friendly.

Feature Request:

1. Clear Transaction Status Updates: Users should receive clear and real-time updates on the status of their transactions. This includes notifications for when a transaction is pending, confirmed, or if any issues arise.

2. Streamlined Checkout Process: Simplify the process of buying or selling NFTs, making it intuitive and easy to understand for users of all experience levels. Reducing the number of steps and providing clear guidance can help in this regard.

3. Transaction History: Implement a dedicated section for users to view their transaction history. This will help users track their past interactions, payments, and deliveries, improving transparency and accountability.

4. Transaction Confirmations: Ensure that users receive notifications once a transaction has been successfully completed. This will provide peace of mind to users.

5. Support and Help Resources: Offer accessible support resources and FAQs within the transaction process. This helps users resolve any issues independently and provides assistance when needed.

This issue aims to enhance the security of the CasperDash Wallet web by implementing several improvements. The following changes are proposed:

• 1. Hide/Show Copy Recovery Phrase: When the user views an existing account, the recovery phrase is displayed, posing a potential security risk. This issue suggests a feature to hide/show the recovery phrase, providing users better control over sensitive information.

• 2. Remove User Service on Wallet Lock: The current implementation of the CasperDash Wallet extension maintains a user service even when the wallet is locked. To improve security and minimize potential attack vectors, this issue proposes removing the user service entirely when the user locks the wallet.

• 3. Apply New v3 Validators (Matching Mobile Version): To ensure consistency and security across platforms, this issue suggests updating the CasperDash Wallet extension to use the new v3 validators, similar to the mobile version. Aligning the validators across platforms helps maintain a cohesive security standard.

• 4. Run "yarn audit" and Fix Dependencies: Running a security audit using "yarn audit" can help identify and address any vulnerabilities or outdated dependencies. This issue suggests running the audit and resolving any detected issues by updating dependencies to their latest secure versions.

• 5. Reset the clipboard to empty after copying the private key

• 6. Change type input secret key to password

• 7. Reset state to empty during componentDidMount (Early clear our sensitive data)

The objective of this task is to implement the functionality that allows users to delete their Casper Wallet, providing them with the ability to permanently remove their wallet and associated data from their device or account.

Description:

Currently, our system does not implement any account lockout mechanism when a user enters an incorrect password multiple times. It would be beneficial to introduce a feature that temporarily locks the user's account for 5 minutes if they enter an incorrect password more than a predefined threshold.

Steps to Reproduce:

1. Visit the login page.
2. Enter an incorrect password.
3. Repeat step 2 for a few more times, exceeding the defined threshold.

Expected Behavior:

After the user enters an incorrect password more than the defined threshold, their account should be locked for a period of 5 minutes. During this time, any login attempts with the correct or incorrect password should be denied, and an appropriate message should be displayed, indicating that the account is locked and will be accessible again after 5 minutes.

Additional Information:

• Operating System: [Enter your operating system]
• Browser: [Enter your browser name and version]
• Screenshots: [If applicable, add any relevant screenshots]
• Additional context or implementation details that might be helpful.

Telegram Group: https://t.me/JasperOfficialCommunity

The objective of this task is to implement the functionality that allows users to securely view their recovery phrase within the application or platform. The recovery phrase, also known as a mnemonic phrase or seed phrase, is a critical component of wallet security as it serves as a backup for wallet recovery and access.