[ECO Bounty] iopay Incorrect EVM Address Labeling and Formatting
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description In the Wallets management screen, addresses are labeled with an "EVM:" prefix; however, the strings displayed following this prefix are Bech32-formatted addresses (starting with bc1...) rather than standard Hexadecimal EVM addresses (starting with 0x...). Specifically, the app shows "EVM:bc1p..." for multiple wallets, including "Cryptotestnet" and "UNIJAYCHIE". This is technically contradictory as the EVM standard requires a 42-character hexadecimal string. Displaying a Bitcoin-style Bech32 address next to an "EVM" label may cause users to send incompatible assets to the wrong network, potentially resulting in a total loss of funds. Steps to Reproduce Open the ioPay application. Navigate to the Wallets management screen (often via the top-left menu or wallet selector). Observe the labels and address formats under each wallet name (e.g., "Wallet 3", "UNIJAYCHIE"). Actual Result Wallets display a prefix of "EVM:" followed by a non-EVM, Bech32 (bc1...) address string. Expected Result If the wallet is displaying an EVM-compatible address, it must start with 0x. If the wallet is displaying a native IoTeX or Bitcoin-style address, the label should be updated to reflect the correct network (e.g., "IOTX:" or "BTC:") rather than "EVM:".
cryptotestnet About 9 hours ago
[ECO Bounty] iopay Incorrect EVM Address Labeling and Formatting
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description In the Wallets management screen, addresses are labeled with an "EVM:" prefix; however, the strings displayed following this prefix are Bech32-formatted addresses (starting with bc1...) rather than standard Hexadecimal EVM addresses (starting with 0x...). Specifically, the app shows "EVM:bc1p..." for multiple wallets, including "Cryptotestnet" and "UNIJAYCHIE". This is technically contradictory as the EVM standard requires a 42-character hexadecimal string. Displaying a Bitcoin-style Bech32 address next to an "EVM" label may cause users to send incompatible assets to the wrong network, potentially resulting in a total loss of funds. Steps to Reproduce Open the ioPay application. Navigate to the Wallets management screen (often via the top-left menu or wallet selector). Observe the labels and address formats under each wallet name (e.g., "Wallet 3", "UNIJAYCHIE"). Actual Result Wallets display a prefix of "EVM:" followed by a non-EVM, Bech32 (bc1...) address string. Expected Result If the wallet is displaying an EVM-compatible address, it must start with 0x. If the wallet is displaying a native IoTeX or Bitcoin-style address, the label should be updated to reflect the correct network (e.g., "IOTX:" or "BTC:") rather than "EVM:".
cryptotestnet About 9 hours ago
[ECO Bounty] iopay Missing Quest, Task, and Rewards Features
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The current user interface across all primary tabs—Wallet, Markets, Trade, and Discover—completely lacks any entry points or modules for Quests, Tasks, or Rewards. For a Web3 wallet aimed at ecosystem growth, the absence of a loyalty or incentive layer significantly hinders user retention and participation in network activities. Steps to Reproduce Open the ioPay app. Navigate through the bottom menu: Wallet, Markets, Trade, and Discover. Search for any "Gift," "Star," or "Task" icon typically associated with reward programs. Check the Discover tab and the browser sub-sections (News, DePINscan) for any quest-related dApps or banners. Actual Result There is no dedicated section, banner, or icon indicating a reward system or active tasks for users to complete. Expected Result The app should feature a visible Quest/Rewards Center, likely within the Discover tab or as a prominent top-level icon in the Wallet view, allowing users to track points, complete ecosystem tasks, and claim rewards.
cryptotestnet About 11 hours ago
[ECO Bounty] iopay Missing Quest, Task, and Rewards Features
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The current user interface across all primary tabs—Wallet, Markets, Trade, and Discover—completely lacks any entry points or modules for Quests, Tasks, or Rewards. For a Web3 wallet aimed at ecosystem growth, the absence of a loyalty or incentive layer significantly hinders user retention and participation in network activities. Steps to Reproduce Open the ioPay app. Navigate through the bottom menu: Wallet, Markets, Trade, and Discover. Search for any "Gift," "Star," or "Task" icon typically associated with reward programs. Check the Discover tab and the browser sub-sections (News, DePINscan) for any quest-related dApps or banners. Actual Result There is no dedicated section, banner, or icon indicating a reward system or active tasks for users to complete. Expected Result The app should feature a visible Quest/Rewards Center, likely within the Discover tab or as a prominent top-level icon in the Wallet view, allowing users to track points, complete ecosystem tasks, and claim rewards.
cryptotestnet About 11 hours ago
[ECO Bounty] iopay.me Lack of Versioning in APK Download Filename
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description When a user clicks the "Download APK" button on the official iopay.me homepage, the resulting file is downloaded with a generic name (e.g., iopay.apk or app-release.apk) that does not include the specific version number. This creates several issues for users and developers: Identification: Users cannot easily verify which version they have downloaded (e.g., v5.3.1 vs v5.2.0) without installing the file. Overwriting: On many Android devices, downloading a second version with the same name will either fail or overwrite the previous file, preventing users from keeping a local archive of different versions for testing or rollback purposes. Security/Trust: Without versioning in the filename, users may be less certain if they are installing the latest security patch or a legacy build. Steps to Reproduce Navigate to iopay.me. Scroll to the footer or the "Get Started" section. Click the "Download APK" button. Observe the filename in the browser’s download manager. Actual Result The file is saved as a generic iopay.apk, lacking any build or version identifiers. Expected Result The download should use a standard semantic versioning format in the filename, such as: ioPay_v5.3.1_release.apk ioPay-5.3.1-3973.apk
cryptotestnet About 11 hours ago
[ECO Bounty] iopay.me Lack of Versioning in APK Download Filename
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description When a user clicks the "Download APK" button on the official iopay.me homepage, the resulting file is downloaded with a generic name (e.g., iopay.apk or app-release.apk) that does not include the specific version number. This creates several issues for users and developers: Identification: Users cannot easily verify which version they have downloaded (e.g., v5.3.1 vs v5.2.0) without installing the file. Overwriting: On many Android devices, downloading a second version with the same name will either fail or overwrite the previous file, preventing users from keeping a local archive of different versions for testing or rollback purposes. Security/Trust: Without versioning in the filename, users may be less certain if they are installing the latest security patch or a legacy build. Steps to Reproduce Navigate to iopay.me. Scroll to the footer or the "Get Started" section. Click the "Download APK" button. Observe the filename in the browser’s download manager. Actual Result The file is saved as a generic iopay.apk, lacking any build or version identifiers. Expected Result The download should use a standard semantic versioning format in the filename, such as: ioPay_v5.3.1_release.apk ioPay-5.3.1-3973.apk
cryptotestnet About 11 hours ago
[ECO Bounty] iopay BTC Price and Valuation Data Not Displaying
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The Wallet dashboard currently fails to fetch and display the market price and total balance valuation for BTC. While other assets like IOTX, ETH, and POL correctly display their current unit price and total value in USD, the BTC row shows null indicators ($ --) for both the unit price and the total value, despite the asset being correctly identified and listed. Steps to Reproduce Open the ioPay application and ensure you are on the Wallet tab. Scroll to the TOKEN list section. Observe the data fields for BTC compared to other listed assets like IOTX or ETH. Actual Result The BTC row displays $ -- instead of the current market price (e.g., ~$70,000) and valuation. This prevents the user from seeing their total portfolio value accurately. Expected Result The application should successfully pull the latest BTC market data from its price oracle and display the unit price and balance valuation in USD, consistent with other assets in the list.
cryptotestnet About 12 hours ago
[ECO Bounty] iopay BTC Price and Valuation Data Not Displaying
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The Wallet dashboard currently fails to fetch and display the market price and total balance valuation for BTC. While other assets like IOTX, ETH, and POL correctly display their current unit price and total value in USD, the BTC row shows null indicators ($ --) for both the unit price and the total value, despite the asset being correctly identified and listed. Steps to Reproduce Open the ioPay application and ensure you are on the Wallet tab. Scroll to the TOKEN list section. Observe the data fields for BTC compared to other listed assets like IOTX or ETH. Actual Result The BTC row displays $ -- instead of the current market price (e.g., ~$70,000) and valuation. This prevents the user from seeing their total portfolio value accurately. Expected Result The application should successfully pull the latest BTC market data from its price oracle and display the unit price and balance valuation in USD, consistent with other assets in the list.
cryptotestnet About 12 hours ago
[ECO Bounty] iopay Lack of Minimum Value Constraint for Slippage (Set slip point)
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description In the Swap customization settings, the "Set slip point" (Slippage) field lacks a defined minimum threshold or "No Minimum" protection. A user can input an extremely low value, such as 0.000001%, without receiving a warning or error message. In decentralized trading, such a low slippage tolerance almost guarantees transaction failure due to standard price fluctuations, leading to wasted gas fees for the user. Steps to Reproduce Open the ioPay app and navigate to the Trade (Swap) tab. Select a pair (e.g., ETH to CEEK) and click the Settings icon to adjust slippage. Select the Customization tab under Set slip point. Manually enter a value significantly below the 0.5% standard (e.g., 0.000001). Observe that the "Confirm" button remains active and no warning is displayed. Actual Result The interface accepts near-zero slippage values without validating if the value is realistic for a successful transaction on the blockchain. Expected Result Validation Warning: The app should display a "Slippage too low" warning for values below a safe threshold (e.g., 0.01% or 0.1%). No Minimum Guardrail: If the user intends for zero slippage, a toggle or specific "No Minimum" indicator should be used, accompanied by a risk disclaimer.
cryptotestnet 2 days ago
[ECO Bounty] iopay Lack of Minimum Value Constraint for Slippage (Set slip point)
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description In the Swap customization settings, the "Set slip point" (Slippage) field lacks a defined minimum threshold or "No Minimum" protection. A user can input an extremely low value, such as 0.000001%, without receiving a warning or error message. In decentralized trading, such a low slippage tolerance almost guarantees transaction failure due to standard price fluctuations, leading to wasted gas fees for the user. Steps to Reproduce Open the ioPay app and navigate to the Trade (Swap) tab. Select a pair (e.g., ETH to CEEK) and click the Settings icon to adjust slippage. Select the Customization tab under Set slip point. Manually enter a value significantly below the 0.5% standard (e.g., 0.000001). Observe that the "Confirm" button remains active and no warning is displayed. Actual Result The interface accepts near-zero slippage values without validating if the value is realistic for a successful transaction on the blockchain. Expected Result Validation Warning: The app should display a "Slippage too low" warning for values below a safe threshold (e.g., 0.01% or 0.1%). No Minimum Guardrail: If the user intends for zero slippage, a toggle or specific "No Minimum" indicator should be used, accompanied by a risk disclaimer.
cryptotestnet 2 days ago
[ECO Bounty] iopay Lack of Visual Feedback and Icons in Trade Navigation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The top-level navigation menu within the Trade tab—specifically the Swap, Perp, and Buy IOTX headers—lacks descriptive icons and sufficient visual state feedback. Currently, the active state is only indicated by a thin white underline. The inactive tabs are rendered in a low-contrast gray font, making them difficult to distinguish from the background and reducing the overall "tappability" of the interface. Steps to Reproduce Open the ioPay application. Navigate to the Trade tab in the bottom menu. Observe the header navigation containing Swap, Perp, and Buy IOTX. Compare the visual contrast between the active selection and the inactive options. Actual Result No Icons: The headers rely purely on text, which can slow down navigation compared to icon-assisted menus. Low Contrast: Inactive text is dim and lacks a clear "interactive" look. Expected Result Iconic Support: Integrate relevant icons for each trade type (e.g., a "two-way arrow" for Swap, a "leverage" or "recurring" icon for Perp, and a "plus/credit card" icon for Buy IOTX). Enhanced Visual State: Use a bolder font weight or a color change for the active tab to provide a more definitive "button-pressed" feel.
cryptotestnet 6 days ago
[ECO Bounty] iopay Lack of Visual Feedback and Icons in Trade Navigation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The top-level navigation menu within the Trade tab—specifically the Swap, Perp, and Buy IOTX headers—lacks descriptive icons and sufficient visual state feedback. Currently, the active state is only indicated by a thin white underline. The inactive tabs are rendered in a low-contrast gray font, making them difficult to distinguish from the background and reducing the overall "tappability" of the interface. Steps to Reproduce Open the ioPay application. Navigate to the Trade tab in the bottom menu. Observe the header navigation containing Swap, Perp, and Buy IOTX. Compare the visual contrast between the active selection and the inactive options. Actual Result No Icons: The headers rely purely on text, which can slow down navigation compared to icon-assisted menus. Low Contrast: Inactive text is dim and lacks a clear "interactive" look. Expected Result Iconic Support: Integrate relevant icons for each trade type (e.g., a "two-way arrow" for Swap, a "leverage" or "recurring" icon for Perp, and a "plus/credit card" icon for Buy IOTX). Enhanced Visual State: Use a bolder font weight or a color change for the active tab to provide a more definitive "button-pressed" feel.
cryptotestnet 6 days ago
[ECO Bounty] ioPay Missing Interactive Checkboxes for Terms Confirmation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: Lack of Interactive Checkboxes in "Welcome to MegaBanX" Modal Description: The onboarding screen requires users to confirm four distinct legal and age-related conditions, but it does not provide individual, interactive checkmark boxes to acknowledge each point separately. Observed Behavior: The "Welcome to MegaBanX" modal lists four critical conditions (age verification, residency status, risk acknowledgment, and agreement to terms) using only bullet points. There is no physical checkbox (input field) next to each item for the user to manually click or "check off." The "I confirm" button appears to be active or the primary driver of consent without ensuring the user has explicitly interacted with each requirement. Expected Behavior: Each of the four listed conditions should be accompanied by an interactive checkbox. For legal compliance and enhanced user awareness, the "I confirm" button should remain disabled (greyed out) until every checkbox has been individually selected by the user. Impact: High (Compliance/UX). The absence of explicit interaction for legal terms can lead to accidental confirmation and may not meet standard regulatory requirements for "informed consent" in financial or crypto applications.
cryptotestnet 6 days ago
[ECO Bounty] ioPay Missing Interactive Checkboxes for Terms Confirmation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: Lack of Interactive Checkboxes in "Welcome to MegaBanX" Modal Description: The onboarding screen requires users to confirm four distinct legal and age-related conditions, but it does not provide individual, interactive checkmark boxes to acknowledge each point separately. Observed Behavior: The "Welcome to MegaBanX" modal lists four critical conditions (age verification, residency status, risk acknowledgment, and agreement to terms) using only bullet points. There is no physical checkbox (input field) next to each item for the user to manually click or "check off." The "I confirm" button appears to be active or the primary driver of consent without ensuring the user has explicitly interacted with each requirement. Expected Behavior: Each of the four listed conditions should be accompanied by an interactive checkbox. For legal compliance and enhanced user awareness, the "I confirm" button should remain disabled (greyed out) until every checkbox has been individually selected by the user. Impact: High (Compliance/UX). The absence of explicit interaction for legal terms can lead to accidental confirmation and may not meet standard regulatory requirements for "informed consent" in financial or crypto applications.
cryptotestnet 6 days ago
[ECO Bounty] iopay UI Text Overlap in Market Details View
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description In the Market Details section of a specific asset (e.g., IOTX), the numerical value for the "Total Transaction volume (24 h)" is improperly rendered, causing it to overlap with the descriptive text label. Specifically, the numerical string (e.g., "3.2404 Million") is displayed directly on top of the "h" and following characters of the "24 h" label, making both the label and the data difficult to read. Steps to Reproduce Open the ioPay app. Navigate to the Markets tab. Select an asset (e.g., IOTX) to view its Market Details. Scroll down to the Market Details card and observe the "Total Transaction volume (24 h)" row. Actual Result The data value is not correctly aligned to the right or spaced away from the label, resulting in a text-on-text overlap that compromises the professional appearance of the financial data. Expected Result The numerical value should be right-aligned with adequate padding from the label, similar to the "Circular supply" and "All-time high" rows, ensuring no overlap occurs.
cryptotestnet 7 days ago
[ECO Bounty] iopay UI Text Overlap in Market Details View
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description In the Market Details section of a specific asset (e.g., IOTX), the numerical value for the "Total Transaction volume (24 h)" is improperly rendered, causing it to overlap with the descriptive text label. Specifically, the numerical string (e.g., "3.2404 Million") is displayed directly on top of the "h" and following characters of the "24 h" label, making both the label and the data difficult to read. Steps to Reproduce Open the ioPay app. Navigate to the Markets tab. Select an asset (e.g., IOTX) to view its Market Details. Scroll down to the Market Details card and observe the "Total Transaction volume (24 h)" row. Actual Result The data value is not correctly aligned to the right or spaced away from the label, resulting in a text-on-text overlap that compromises the professional appearance of the financial data. Expected Result The numerical value should be right-aligned with adequate padding from the label, similar to the "Circular supply" and "All-time high" rows, ensuring no overlap occurs.
cryptotestnet 7 days ago
[ECO Bounty] iopay Lack of Visual Feedback for Wallet Address Copy Action
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description When a user attempts to copy a wallet address from the Receive screen, the interface provides inconsistent and insufficient visual feedback. While a "Copied!" toast message occasionally appears at the bottom of the screen, the copy icon itself does not change state (e.g., to a checkmark), and there is no persistent visual indicator to confirm which specific address was successfully copied. This can lead to user uncertainty, especially when managing multiple chain addresses (IoTeX, Ethereum, BTC, etc.) in a single view. Steps to Reproduce Open the ioPay app and navigate to the Receive screen. Click the Copy icon next to any wallet address (e.g., IoTeX, Ethereum, or a specific BTC format like Legacy or Native Segwit). Observe the behavior of the copy icon and the presence of any confirmation messages. Actual Result No Icon State Change: The copy icon remains static after interaction, providing no immediate "button-press" or "success" feedback. Subtle Toast Message: A small "Copied!" toast message appears briefly at the bottom but may be overlooked by the user. Expected Result Dynamic Icon Feedback: The copy icon should instantly transform into a success icon (e.g., a green checkmark) for 1–2 seconds to confirm the specific action. High-Visibility Confirmation: A more prominent "Wallet Address Successfully Copied" notification should be displayed to ensure the user is aware of the successful operation.
cryptotestnet 7 days ago
[ECO Bounty] iopay Lack of Visual Feedback for Wallet Address Copy Action
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description When a user attempts to copy a wallet address from the Receive screen, the interface provides inconsistent and insufficient visual feedback. While a "Copied!" toast message occasionally appears at the bottom of the screen, the copy icon itself does not change state (e.g., to a checkmark), and there is no persistent visual indicator to confirm which specific address was successfully copied. This can lead to user uncertainty, especially when managing multiple chain addresses (IoTeX, Ethereum, BTC, etc.) in a single view. Steps to Reproduce Open the ioPay app and navigate to the Receive screen. Click the Copy icon next to any wallet address (e.g., IoTeX, Ethereum, or a specific BTC format like Legacy or Native Segwit). Observe the behavior of the copy icon and the presence of any confirmation messages. Actual Result No Icon State Change: The copy icon remains static after interaction, providing no immediate "button-press" or "success" feedback. Subtle Toast Message: A small "Copied!" toast message appears briefly at the bottom but may be overlooked by the user. Expected Result Dynamic Icon Feedback: The copy icon should instantly transform into a success icon (e.g., a green checkmark) for 1–2 seconds to confirm the specific action. High-Visibility Confirmation: A more prominent "Wallet Address Successfully Copied" notification should be displayed to ensure the user is aware of the successful operation.
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Passkey Support for Wallet Creation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: No Option to Create or Import Wallet Using Passkeys Description: The "Add Wallet" interface does not offer Passkey technology as a method for wallet creation, storage, or recovery. Observed Behavior: The current wallet creation options are limited to traditional methods: mnemonic phrases, private keys, and AA (Account Abstraction) wallets. There is no integration for biometric-backed Passkeys (FIDO2/WebAuthn), which would allow users to secure their wallets using device-native hardware (FaceID, TouchID, or Android Biometrics) without managing physical seed phrases. Expected Behavior: The "Create wallet" section should include a "Create with Passkey" option. This would enhance security by eliminating the risk of lost or stolen seed phrases while significantly improving the user experience through one-touch authentication.
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Passkey Support for Wallet Creation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: No Option to Create or Import Wallet Using Passkeys Description: The "Add Wallet" interface does not offer Passkey technology as a method for wallet creation, storage, or recovery. Observed Behavior: The current wallet creation options are limited to traditional methods: mnemonic phrases, private keys, and AA (Account Abstraction) wallets. There is no integration for biometric-backed Passkeys (FIDO2/WebAuthn), which would allow users to secure their wallets using device-native hardware (FaceID, TouchID, or Android Biometrics) without managing physical seed phrases. Expected Behavior: The "Create wallet" section should include a "Create with Passkey" option. This would enhance security by eliminating the risk of lost or stolen seed phrases while significantly improving the user experience through one-touch authentication.
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Visual Feedback and Copy Confirmation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: Lack of Visual Feedback and Copy Confirmation for Wallet Address Description: The interface for recovering an AA wallet lacks sufficient visual feedback when a user interacts with the wallet address. Specifically, there is no distinct icon to signify that a copy action has occurred, and the "Success" toast notification is generic rather than explicitly confirming the address was copied to the clipboard. Observed Behavior: In the "Recover AA wallet" screen, an address (e.g., 0x8281...2528051d) is listed with a standard copy icon next to it. Upon tapping the copy icon, a generic "Success" toast notification with a camera icon appears at the bottom of the screen. There is no change to the copy icon itself (e.g., switching to a checkmark) to provide immediate, localized visual confirmation of the specific action. The text "Success" does not clarify what was successful (e.g., it should ideally say "Address Copied!"). Expected Behavior: The copy icon should briefly change to a checkmark ($\checkmark$) upon a successful tap to provide localized feedback. The toast notification should explicitly state "Wallet Address Copied" to confirm the exact action performed. The icon within the success toast should be relevant to the action (a clipboard or checkmark) rather than a camera icon.
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Visual Feedback and Copy Confirmation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: Lack of Visual Feedback and Copy Confirmation for Wallet Address Description: The interface for recovering an AA wallet lacks sufficient visual feedback when a user interacts with the wallet address. Specifically, there is no distinct icon to signify that a copy action has occurred, and the "Success" toast notification is generic rather than explicitly confirming the address was copied to the clipboard. Observed Behavior: In the "Recover AA wallet" screen, an address (e.g., 0x8281...2528051d) is listed with a standard copy icon next to it. Upon tapping the copy icon, a generic "Success" toast notification with a camera icon appears at the bottom of the screen. There is no change to the copy icon itself (e.g., switching to a checkmark) to provide immediate, localized visual confirmation of the specific action. The text "Success" does not clarify what was successful (e.g., it should ideally say "Address Copied!"). Expected Behavior: The copy icon should briefly change to a checkmark ($\checkmark$) upon a successful tap to provide localized feedback. The toast notification should explicitly state "Wallet Address Copied" to confirm the exact action performed. The icon within the success toast should be relevant to the action (a clipboard or checkmark) rather than a camera icon.
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Line Numbering for Recovery Phrase Input
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: Lack of Sequential Numbering in Mnemonic Input Field Description: When importing an existing wallet using a recovery phrase, the text input area does not provide sequential numbering (1-12 or 1-24) for the entered words. Observed Behavior: The interface presents a blank text box for the user to type or paste their recovery phrase. There are no visual indicators or numbered slots to help the user track the specific position of each word (e.g., which word is #7 vs #8). Expected Behavior: The input field should feature automatic numbering or distinct numbered boxes for each word in the seed phrase. This ensures the user maintains the correct sequence, which is mandatory for successful wallet restoration.
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Line Numbering for Recovery Phrase Input
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: Lack of Sequential Numbering in Mnemonic Input Field Description: When importing an existing wallet using a recovery phrase, the text input area does not provide sequential numbering (1-12 or 1-24) for the entered words. Observed Behavior: The interface presents a blank text box for the user to type or paste their recovery phrase. There are no visual indicators or numbered slots to help the user track the specific position of each word (e.g., which word is #7 vs #8). Expected Behavior: The input field should feature automatic numbering or distinct numbered boxes for each word in the seed phrase. This ensures the user maintains the correct sequence, which is mandatory for successful wallet restoration.
cryptotestnet 7 days ago
[ECO Bounty] iopay Lack of Visual Feedback for Invalid Private Key
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: No Error Icon or Immediate Visual Feedback for Invalid Private Key Description: The "Import wallet with private key" interface fails to provide immediate visual feedback or a specific error icon when a user enters an incorrectly formatted or invalid private key. Observed Behavior: When a user inputs a string that does not meet the technical requirements of a private key (e.g., incorrect length or characters), the UI does not show a real-time error icon (such as a red "X" or exclamation mark) inside the text field. The user may have to attempt to proceed before receiving any notification, leading to a "guessing game" regarding whether the pasted key was captured correctly. Expected Behavior: The input field should perform real-time validation. If the key is invalid, a red error icon should appear within the field along with a clear descriptive message: "Invalid Private Key format".
cryptotestnet 7 days ago
[ECO Bounty] iopay Lack of Visual Feedback for Invalid Private Key
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: No Error Icon or Immediate Visual Feedback for Invalid Private Key Description: The "Import wallet with private key" interface fails to provide immediate visual feedback or a specific error icon when a user enters an incorrectly formatted or invalid private key. Observed Behavior: When a user inputs a string that does not meet the technical requirements of a private key (e.g., incorrect length or characters), the UI does not show a real-time error icon (such as a red "X" or exclamation mark) inside the text field. The user may have to attempt to proceed before receiving any notification, leading to a "guessing game" regarding whether the pasted key was captured correctly. Expected Behavior: The input field should perform real-time validation. If the key is invalid, a red error icon should appear within the field along with a clear descriptive message: "Invalid Private Key format".
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Web3 Auth Integration for Wallet Creation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: No Option to Create Wallet via Social Logins (Google/Apple) Description: The "Add Wallet" interface lacks modern Web3 onboarding options such as creating a wallet using a Google or Apple account. Observed Behavior: Currently, users are restricted to traditional methods: creating a wallet with a mnemonic phrase, a private key, or setting up an AA (Account Abstraction) wallet via standard steps. There is no social authentication (Google/Apple) integration visible in the "Create wallet" or "Import wallet" sections. Expected Behavior: The application should include social login options (e.g., "Continue with Google" or "Continue with Apple") to streamline the onboarding process for non-technical users. This would leverage MPC (Multi-Party Computation) or similar technology to allow wallet creation without the immediate need for manual seed phrase management.
cryptotestnet 7 days ago
[ECO Bounty] iopay Missing Web3 Auth Integration for Wallet Creation
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Issue: No Option to Create Wallet via Social Logins (Google/Apple) Description: The "Add Wallet" interface lacks modern Web3 onboarding options such as creating a wallet using a Google or Apple account. Observed Behavior: Currently, users are restricted to traditional methods: creating a wallet with a mnemonic phrase, a private key, or setting up an AA (Account Abstraction) wallet via standard steps. There is no social authentication (Google/Apple) integration visible in the "Create wallet" or "Import wallet" sections. Expected Behavior: The application should include social login options (e.g., "Continue with Google" or "Continue with Apple") to streamline the onboarding process for non-technical users. This would leverage MPC (Multi-Party Computation) or similar technology to allow wallet creation without the immediate need for manual seed phrase management.
cryptotestnet 7 days ago
[ECO Bounty] DePINscan Missing "Sign in with Apple" Authentication Option
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The current login and registration interface in ioPay does not offer "Sign in with Apple" as an authentication method. While the app provides "Continue with Google" and traditional email/password fields, the absence of Apple ID integration creates a friction point for iOS users and Android users who prefer Apple's privacy-focused sign-in service. Steps to Reproduce Open the ioPay app on a mobile device. Navigate to the https://depinscan.io/developer/settings/profile Login. Observe the available "Continue with" social login buttons. Actual Result Only the Google social login option is displayed alongside standard email fields. Expected Result A "Continue with Apple" button should be available to provide a consistent and cross-platform authentication experience, especially to satisfy App Store guidelines for apps offering social login.
cryptotestnet 7 days ago
[ECO Bounty] DePINscan Missing "Sign in with Apple" Authentication Option
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The current login and registration interface in ioPay does not offer "Sign in with Apple" as an authentication method. While the app provides "Continue with Google" and traditional email/password fields, the absence of Apple ID integration creates a friction point for iOS users and Android users who prefer Apple's privacy-focused sign-in service. Steps to Reproduce Open the ioPay app on a mobile device. Navigate to the https://depinscan.io/developer/settings/profile Login. Observe the available "Continue with" social login buttons. Actual Result Only the Google social login option is displayed alongside standard email fields. Expected Result A "Continue with Apple" button should be available to provide a consistent and cross-platform authentication experience, especially to satisfy App Store guidelines for apps offering social login.
cryptotestnet 7 days ago
[ECO Bounty] iopay Absence of Integrated Community Discussion & Support Channels
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The ioPay mobile wallet lacks a dedicated section or direct links for community discussion, real-time support, or social engagement within the primary user interface. While the app facilitates technical transactions and market tracking, users have no clear path to join community dialogues (e.g., Discord, Telegram, or X) or access live help from within the "Wallet" or "Discover" tabs. This isolation forces users to leave the app to find support, which can lead to a fragmented user experience and decreased trust. Steps to Reproduce Open the ioPay application to the Wallet home screen. Navigate through the bottom menu (Wallet, Markets, Trade, Discover). Search for a "Community," "Social," or "Live Chat" button or menu item. Observe the lack of direct integration for user-to-user or user-to-developer discussion. Actual Result The interface is focused purely on financial metrics and asset management. There are no visible entry points for community forums or real-time discussion groups. Expected Result Community Hub: A dedicated section under "Discover" or the "Settings" menu featuring links to official community channels. Live Support Integration: A "Help" or "Discussion" icon on the main dashboard to facilitate immediate feedback and troubleshooting.
cryptotestnet 7 days ago
[ECO Bounty] iopay Absence of Integrated Community Discussion & Support Channels
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The ioPay mobile wallet lacks a dedicated section or direct links for community discussion, real-time support, or social engagement within the primary user interface. While the app facilitates technical transactions and market tracking, users have no clear path to join community dialogues (e.g., Discord, Telegram, or X) or access live help from within the "Wallet" or "Discover" tabs. This isolation forces users to leave the app to find support, which can lead to a fragmented user experience and decreased trust. Steps to Reproduce Open the ioPay application to the Wallet home screen. Navigate through the bottom menu (Wallet, Markets, Trade, Discover). Search for a "Community," "Social," or "Live Chat" button or menu item. Observe the lack of direct integration for user-to-user or user-to-developer discussion. Actual Result The interface is focused purely on financial metrics and asset management. There are no visible entry points for community forums or real-time discussion groups. Expected Result Community Hub: A dedicated section under "Discover" or the "Settings" menu featuring links to official community channels. Live Support Integration: A "Help" or "Discussion" icon on the main dashboard to facilitate immediate feedback and troubleshooting.
cryptotestnet 7 days ago
[ECO Bounty] iopay Lack of Visual Feedback and Icons for Market Filters
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The secondary navigation menu for market filters—specifically Watchlist, Hot, Gainers, and Losers—lacks descriptive icons and high-contrast visual state indicators. While the "Hot" tab is currently active (indicated by a white underline and brighter text), the inactive tabs (Watchlist, Gainers, and Losers) are rendered in a dim, low-contrast gray font that blends into the black background. Additionally, the interface relies solely on text labels without accompanying icons, which slows down user recognition of these core filtering features. Steps to Reproduce Open the ioPay app and navigate to the Markets tab. Locate the filtering row below the "Spot/Perp/Predict" headers and featured asset cards. Observe the visual presentation of the Watchlist, Hot, Gainers, and Losers labels. Actual Result Icon Absence: These categories are represented by text only, providing no symbolic cues for the user. Low Visibility: Inactive tabs use a dark gray font that has poor legibility against the black theme, making the navigation options less prominent. Expected Result Iconic Representation: Each filter should feature a distinct icon (e.g., a star for Watchlist, a flame for Hot, an upward arrow for Gainers) to aid in rapid identification. Improved Contrast: Inactive tab text should be brightened to ensure it is clearly readable while still being distinguishable from the active state. Consistent Design: This row should match the quality of the "Network" filters below it (e.g., BSC, Solana, ETH), which are enclosed in clearer button-like containers.
cryptotestnet 8 days ago
[ECO Bounty] iopay Lack of Visual Feedback and Icons for Market Filters
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The secondary navigation menu for market filters—specifically Watchlist, Hot, Gainers, and Losers—lacks descriptive icons and high-contrast visual state indicators. While the "Hot" tab is currently active (indicated by a white underline and brighter text), the inactive tabs (Watchlist, Gainers, and Losers) are rendered in a dim, low-contrast gray font that blends into the black background. Additionally, the interface relies solely on text labels without accompanying icons, which slows down user recognition of these core filtering features. Steps to Reproduce Open the ioPay app and navigate to the Markets tab. Locate the filtering row below the "Spot/Perp/Predict" headers and featured asset cards. Observe the visual presentation of the Watchlist, Hot, Gainers, and Losers labels. Actual Result Icon Absence: These categories are represented by text only, providing no symbolic cues for the user. Low Visibility: Inactive tabs use a dark gray font that has poor legibility against the black theme, making the navigation options less prominent. Expected Result Iconic Representation: Each filter should feature a distinct icon (e.g., a star for Watchlist, a flame for Hot, an upward arrow for Gainers) to aid in rapid identification. Improved Contrast: Inactive tab text should be brightened to ensure it is clearly readable while still being distinguishable from the active state. Consistent Design: This row should match the quality of the "Network" filters below it (e.g., BSC, Solana, ETH), which are enclosed in clearer button-like containers.
cryptotestnet 8 days ago
[ECO Bounty] iopay Lack of Visual Feedback and Icons for Market Navigation Tabs
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The navigation menu for market categories (Spot, Perp, and Predict) lacks descriptive icons and sufficient visual state feedback. While the "Spot" tab is currently active (indicated by a white underline), the inactive "Perp" and "Predict" tabs are rendered in a low-contrast gray font that makes them difficult to read against the black background. Furthermore, the reliance on text-only labels without accompanying icons reduces the intuitive "at-a-glance" navigation expected in a mobile financial application. Steps to Reproduce Open the ioPay application and navigate to the Markets tab at the bottom. Locate the top navigation bar containing Spot, Perp, and Predict. Observe the visual distinction between the active and inactive tabs. Actual Result No Icons: The tabs use text only, missing an opportunity for faster visual recognition. Low Contrast: Inactive tab text ("Perp", "Predict") has poor visibility against the dark theme. Expected Result Iconic Support: Each market category should feature a relevant icon (e.g., a simple chart icon for Spot, a gear or recurring icon for Perp). Enhanced Contrast: Text for all tabs should be bright enough to ensure accessibility and clear legibility. Improved Active State: Use a more prominent highlight (e.g., color change or bolder font) to confirm the active selection.
cryptotestnet 8 days ago
[ECO Bounty] iopay Lack of Visual Feedback and Icons for Market Navigation Tabs
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The navigation menu for market categories (Spot, Perp, and Predict) lacks descriptive icons and sufficient visual state feedback. While the "Spot" tab is currently active (indicated by a white underline), the inactive "Perp" and "Predict" tabs are rendered in a low-contrast gray font that makes them difficult to read against the black background. Furthermore, the reliance on text-only labels without accompanying icons reduces the intuitive "at-a-glance" navigation expected in a mobile financial application. Steps to Reproduce Open the ioPay application and navigate to the Markets tab at the bottom. Locate the top navigation bar containing Spot, Perp, and Predict. Observe the visual distinction between the active and inactive tabs. Actual Result No Icons: The tabs use text only, missing an opportunity for faster visual recognition. Low Contrast: Inactive tab text ("Perp", "Predict") has poor visibility against the dark theme. Expected Result Iconic Support: Each market category should feature a relevant icon (e.g., a simple chart icon for Spot, a gear or recurring icon for Perp). Enhanced Contrast: Text for all tabs should be bright enough to ensure accessibility and clear legibility. Improved Active State: Use a more prominent highlight (e.g., color change or bolder font) to confirm the active selection.
cryptotestnet 8 days ago
[ECO Bounty] iopay Inadequate Visual Confirmation for Copy Action
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description When a user clicks the copy icon next to their email address in the DePINscan Profile settings, the visual feedback is insufficient. The icon briefly changes to include a small checkmark, but there is no prominent notification, toast message, or color change to clearly confirm to the user that the information has been successfully copied to the clipboard. Steps to Reproduce Navigate to the DePINscan Developer Profile settings. Locate the email address under the Profile section. Click the Copy icon to the right of the email. Observe the lack of high-visibility confirmation. Actual Result The only feedback is a subtle icon change that is easily missed, especially on mobile devices with smaller viewports. Expected Result The system should provide clear, multi-modal feedback: Toast Notification: A temporary popup message (e.g., "Email copied to clipboard!"). Color Change: The copy icon should change to a distinct success color (e.g., green) for a longer duration.
cryptotestnet 10 days ago
[ECO Bounty] iopay Inadequate Visual Confirmation for Copy Action
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description When a user clicks the copy icon next to their email address in the DePINscan Profile settings, the visual feedback is insufficient. The icon briefly changes to include a small checkmark, but there is no prominent notification, toast message, or color change to clearly confirm to the user that the information has been successfully copied to the clipboard. Steps to Reproduce Navigate to the DePINscan Developer Profile settings. Locate the email address under the Profile section. Click the Copy icon to the right of the email. Observe the lack of high-visibility confirmation. Actual Result The only feedback is a subtle icon change that is easily missed, especially on mobile devices with smaller viewports. Expected Result The system should provide clear, multi-modal feedback: Toast Notification: A temporary popup message (e.g., "Email copied to clipboard!"). Color Change: The copy icon should change to a distinct success color (e.g., green) for a longer duration.
cryptotestnet 10 days ago
[ECO Bounty] iopay NFT Search Function Failure for Verified Assets
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The search functionality within the NFT asset section is currently non-functional. Users attempting to search for specific verified NFTs (e.g., "BucketNFT") are met with a "No tokens added yet" empty state, even when the asset is correctly indexed and verified on the network. This prevents users from managing or viewing specific collections within their wallet interface. Steps to Reproduce Open the ioPay app and navigate to the Wallet tab. Click on the NFT category in the asset navigation bar. Click the Search icon (magnifying glass) on the right side of the screen. Enter the name of a known, verified NFT (e.g., "BucketNFT") into the search bar. Observe the search results. Actual Result The app displays a "No tokens added yet" message with an empty-state graphic, failing to pull up the verified NFT associated with that string. Expected Result The search should query the user's wallet and the network's verified registry to display the matching NFT(s) immediately.
cryptotestnet 10 days ago
[ECO Bounty] iopay NFT Search Function Failure for Verified Assets
Wallet Address Reporter: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren App Version: ioPay v5.3.1 (3973) Device: Redmi Note 10 Pro (Android 13) Description The search functionality within the NFT asset section is currently non-functional. Users attempting to search for specific verified NFTs (e.g., "BucketNFT") are met with a "No tokens added yet" empty state, even when the asset is correctly indexed and verified on the network. This prevents users from managing or viewing specific collections within their wallet interface. Steps to Reproduce Open the ioPay app and navigate to the Wallet tab. Click on the NFT category in the asset navigation bar. Click the Search icon (magnifying glass) on the right side of the screen. Enter the name of a known, verified NFT (e.g., "BucketNFT") into the search bar. Observe the search results. Actual Result The app displays a "No tokens added yet" message with an empty-state graphic, failing to pull up the verified NFT associated with that string. Expected Result The search should query the user's wallet and the network's verified registry to display the matching NFT(s) immediately.
cryptotestnet 10 days ago