[ECO Bounty] Mimo Exchange Missing "Do Not Show Again" Option for Delisted Assets Warning Modal

Description When selecting delisted assets like USDC, USDT, WETH, or WBTC for bridging: Warning modal displays: "Assets IOTX, USDC, USDT, WETH and WBTC have been delisted. Delisted assets have no security guarantee..." Options available: X (Close) or View Official Notice No "Do Not Show Again" option to suppress future warnings for informed users Orange arrows in the screenshot highlight the Connect Wallet button and X close button, emphasizing repetitive dismissal frustration. Steps to Reproduce Open mimo.exchange in mobile browser Navigate to Bridge section Select a delisted asset (e.g., USDC, USDT, WETH, WBTC) for "You Pay" or "You Receive" Attempt to proceed → Warning modal appears Dismiss with X Repeat steps 3-4 → Warning reappears every time Expected Behavior Warning modal includes "☑️ Do Not Show Again" checkbox/toggle If checked and dismissed, warning is suppressed for future sessions (via localStorage or account preference) UX allows power users to bypass repetitive warnings after acknowledgment Actual Behavior Warning reappears on every asset selection/bridge attempt Users forced to tap X repeatedly with no suppression option No persistence of user acknowledgment Suggested Fix Add "☑️ Do Not Show Again" checkbox at bottom of modal On dismiss with checkbox → set localStorage: localStorage.setItem('delistedAssetsWarningDismissed', 'true') Before modal trigger → check storage: if true, skip modal Optional: Per-asset toggles or account-based persistence Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 1 hour ago

[ECO Bounty] ioTexScan Recent Search History Not Persisting/Saving in Search

Description When interacting with the global search bar at the top of the IoTeX Scan explorer: Expected: Recent searches (addresses, transaction IDs, or block numbers) should be saved and displayed as suggestions when the search bar is tapped or typed into again Actual: No recent search history is displayed; the search bar appears empty or shows placeholder text only each time it is accessed The keyboard shortcut button (⌘K) is visible next to the search bar, suggesting there should be search functionality/history available Steps to Reproduce Open a web browser on mobile device Navigate to iotexscan.io Tap on the search bar (labeled "Search by Address / Txn I...") Enter a valid Address or Transaction ID Submit the search and view results Return to the main page or tap the search bar again ➡️ Recent searches do not appear below or inside the search field Expected Behavior Recent searches (addresses, TX hashes) should be cached locally or linked to the user's session When tapping the search bar, a dropdown of recent searches should appear for quick re-access Users should be able to clear search history if desired Recent searches should persist across page reloads (if using local storage) Actual Behavior Search bar always appears empty with only placeholder text No recent search dropdown is displayed Users must manually re-type addresses or TX IDs each time No visual indication of search history functionality being present Suggested Fix Implement localStorage or sessionStorage to cache recent searches on the client side Add a dropdown UI below the search bar showing the last 5-10 recent searches Include a "Clear History" option for user control Ensure recent searches persist across page navigation within the same session Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 5 hours ago

[ECO Bounty] iopay Infinite Loading on Staking Confirmation

Description The application enters an infinite loading state when a user attempts to confirm a staking action. Despite the interface correctly identifying a validation error (the minimum staking amount of 100 IOTX is not met), the "Confirm" button triggers a persistent loading spinner that does not resolve or allow the user to return to the previous state without a force-close or manual interruption. Steps to Reproduce Open the ioPay app and navigate to the Stake section. Select a delegate (e.g., mrtrump). Enter a Staked Amount below the required minimum (e.g., 0.62 IOTX, while the balance is 0.6262 IOTX). Observe the red error message: "The minimum amount is 100". Tap the Confirm (purple) button. Observe the persistent loading spinner that appears over the button and does not stop. Expected Result The app should prevent the "Confirm" button from being clickable if the minimum amount requirement is not met. If clicked, it should provide a static error alert rather than initiating a network request or a loading state. Actual Result The app initiates a loading cycle that never ends, effectively freezing the transaction flow. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 7 hours ago

[ECO Bounty] iopay 5-Minute Candlestick Chart Displaying Incorrect / Inconsistent Time Intervals

Description Upon selecting the 5mins tab in the chart timeframe selector, the X-axis timestamps shown are: Timestamp Shown 03/06 07:40 03/08 20:53 03/07 14:16 03/10 03:30 These timestamps span across multiple days (March 6 – March 10), which is inconsistent with a 5-minute interval chart. A 5-minute chart should only display a short window of intraday data (e.g., a few hours of 5-min candles), not days apart. Additionally: The volume bars at the bottom also reflect irregular spikes inconsistent with a 5-min timeframe The timestamps appear out of chronological order (03/08 shown before 03/07) The chart data does not match the selected 5mins timeframe Steps to Reproduce Open the ioPay app Navigate to IOTX / IoTeX token detail page Scroll to the Chart section Tap on 5mins timeframe tab Observe the X-axis timestamps and candlestick intervals ➡️ Chart shows multi-day data instead of 5-minute interval data Expected Behavior The chart should display short-term 5-minute candlestick data X-axis should show time labels within the same day (e.g., 10:00, 10:05, 10:10...) Volume bars should reflect 5-minute trading volume, not daily spikes Timestamps should be in correct chronological order Actual Behavior Chart X-axis shows multi-day timestamps (03/06 to 03/10) Timestamps are out of order (03/08 appears before 03/07) Chart appears to be rendering daily or multi-day data regardless of the 5mins selection Volume spikes are inconsistent with a 5-minute view Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 8 hours ago

[ECO Bounty] ioPay Community Tab Missing from Bottom Navigation Bar

Summary "Community" section/tab is missing from the application's bottom navigation bar or expected location. Description The Community feature/tab is not visible or accessible within the app. Based on the current UI, the bottom navigation bar only displays the following tabs: 🔵 Wallet (active) 📊 Markets 🔄 Trade 🧭 Discover The Community tab/section is absent from the navigation, which may indicate: It was removed in a recent update It is not rendering due to a UI bug It is hidden behind a feature flag or permission issue Steps to Reproduce Open the ioPay app Observe the bottom navigation bar Look for a Community tab or section ➡️ Community option is not found Expected Behavior A Community tab or section should be visible and accessible within the app navigation, allowing users to access community features (forums, social feeds, discussions, etc.). Actual Behavior No Community tab or entry point exists anywhere in the visible UI. Possible Impact Users cannot access community features Reduced engagement and social interaction within the app May affect user retention Suggested Fix Verify if the Community tab was intentionally removed or is a regression bug Restore the Community section in the bottom navigation bar or add an entry point under Discover Ensure feature flags are correctly configured for all user segments Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 8 hours ago

[ECO Bounty] ioTex Hub Inconsistent Icon Coloring in IoTeX Hub Tools

Description The "Tools" dashboard on the IoTeX Hub features an inconsistent color palette for its functional icons. While the "Address Convert" and "Requirement Request" icons utilize a multi-colored, branded theme, the icons for "Deployed Contracts" and "Add Stake to Bucket" are rendered in a flat, grayscale/monochrome style. This lack of color uniformity makes the interface appear incomplete or "Beta" in a way that may confuse users regarding which tools are active or fully developed. Steps to Reproduce Navigate to the IoTeX Hub Tools page. Scroll through the available tool cards. Compare the vibrant, blue/green icons of "Address Convert" and "Requirement Request" against the gray icons for "Deployed Contracts" and "Add Stake to Bucket". Actual Result The icons for "Deployed Contracts" and "Add Stake to Bucket" lack the color depth and branding seen in the other dashboard elements. Expected Result All tool icons should follow a consistent "modern style" color scheme to ensure a unified and professional user experience across the IoTeX Hub ecosystem. Suggested Fix Update the SVG or image assets for the grayscale icons to match the blue and green gradient theme used elsewhere on the page. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 10 hours ago

[ECO Bounty] DePINscan Missing Token/Project Logos in News Feed

Description In the "News" section of DePINscan, project tags (such as TAO and GRASS) are missing their respective graphical logos. These tags appear as plain text labels with price performance data, but the circular placeholder where a token logo typically resides is empty or missing, which detracts from the professional visual identity of the platform. Steps to Reproduce Navigate to the DePINscan News page. Scroll through the news articles (e.g., "Top 10 DEPIN Projects Revealed by LunarCrush"). Observe the project asset tags located below the article titles. Actual Result Project tags like TAO and GRASS are displayed with text and percentage changes only, lacking their official brand logos. Expected Result Each project tag should feature the official token or project logo next to the ticker symbol for easier visual identification by users. Suggested Fix Ensure the news feed component is correctly pulling asset icons from the DePINscan image manifest. Implement a fallback generic icon if a specific project logo is not found in the database. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 11 hours ago

[ECO Bounty] ioTexScan Missing Digit Grouping (Commas) for Staked IOTX

Description The IoTeX block explorer is failing to use digit grouping (commas) for large numerical values in the "Staked IOTX" data block. While other metrics on the dashboard use commas (e.g., "213,194,125 Transactions"), the raw amount of staked tokens is displayed as a continuous string of digits, making it difficult for users to read at a glance. Steps to Reproduce Navigate to iotexscan.io. Locate the "Staked IOTX" card on the main dashboard. Observe the green numerical value representing the total staked amount. Actual Result The value is displayed as 3717669956.85. Expected Result The value should follow standard financial formatting with commas for readability: 3,717,669,956.85. Suggested Fix Apply a standard locale-based number formatter (e.g., toLocaleString() in JavaScript) to the "Staked IOTX" value to ensure consistency with the "Transactions" and "Blocks" cards already present on the dashboard. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet About 11 hours ago

[Eco Bounty] ioPay Balance Text Unclickable in Stake Screen (No Auto-Fill)

App: ioPay Version: v5.2.0 (3970) Feature: Stake → Enter Amount Field Severity: High (Core UX Broken - Common Pattern Missing) Device: Android Balance: 28.59 IOTX 📝 Description The "Balance 28.59 IOTX" text/link in the Stake screen is non-interactive. Tapping it does nothing—no auto-fill of the amount field, no "Max" selection, no feedback. This breaks standard wallet UX where balance links auto-populate the input. 🔁 Steps to Reproduce Navigate to Stake → New Stake from Wallet. Locate "Enter amount of IOTX" field. Tap "Balance 28.59 IOTX" text (highlighted orange in screenshot). Observe: No change in input field, no visual feedback. ✅ Expected Result Tapping "Balance X IOTX" should: Auto-fill amount field with available balance (e.g., 28.59). Account for gas fees (e.g., 28.5 leaving buffer). Show ripple/tap effect and optional toast ("Max amount set"). ❌ Actual Result Zero response—field remains empty/unchanged. User must manually type balance value. 💡 Suggested Fix Add Click Listener: textView.setOnClickListener { amountEditText.setText(balance.toString()) }. Deduct Gas: Calculate availableBalance = totalBalance - estimatedGas. Visual Affordance: Underline text, add (tap for max) label, or blue color. Accessibility: Support long-press for "Max - Gas" vs. "Exact Max". Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 2 days ago

[ECO Bounty] Price Oracle/Routing Exploit in IOTX Swap

Description A critical vulnerability has been identified in the OKX DEX Aggregator routing logic for the IOTX/ioUSDT pair. The system is miscalculating market depth, leading to an inverted price impact or an arbitrage loop that allows for significant "risk-free" profit due to incorrect oracle data or pool weighting. The Exploit / Impact Inverted Value Logic: The UI warns of a 25.18% loss, but the smart contract execution path is potentially pulling from a desynced liquidity pool where the exchange rate is significantly higher than the global market average. Arbitrage Opportunity: Users can exploit the difference between the OKX Aggregator's quoted rate and the actual on-chain liquidity (e.g., on Mimo or Quicksilver) to execute swaps at a massive premium. Protocol Risk: This suggests a "stale price" bug where the OKX DEX is not updating fast enough to reflect the actual token values following the recent IoTeX bridge events. Technical Breakdown Faulty Aggregation: The aggregator is prioritizing a "broken" route that misrepresents the token value. Oracle Desync: The price feed for ioUSDT (IoTeX-bridged USDT) is likely disconnected from the 1:1 peg within the OKX interface, allowing swaps at "discounted" rates that don't exist in the real market. Execution: If the swap is confirmed despite the "loss" warning, the user receives an amount of tokens far exceeding the initial market value of the input. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 2 days ago

1

[ECO Bounty] ioPay QR Code "Receive" Screen Lacks Automatic Screen Brightness Increase

Summary The ioPay "Receive" screen does not automatically increase the device's screen brightness when displaying a QR code. This makes it difficult for other devices to scan the address, especially in low-light environments or for users with low battery-saving brightness settings. Description When a user navigates to the "Receive" section to show their QR code for a transaction, the app maintains the current system brightness. Standard industry practice for finance and wallet apps is to temporarily force the screen to 100% brightness (or a high threshold) while on this specific screen to ensure maximum scannability. Without this feature, QR code scanners often fail to read the code quickly, leading to a poor user experience. Steps to Reproduce Set device brightness to a low level (e.g., 10-20%). Open the ioPay application. Navigate to Receive. Observe that the screen brightness remains low, making the QR code dim and hard to scan. Move away from the screen and observe that there is no toggle or automatic trigger to brighten the display. Expected Behavior Upon entering the "Receive" screen, the app should programmatically request maximum screen brightness. When navigating away from the "Receive" screen, the brightness should automatically revert to the previous user setting. (Optional) Provide a small "Brighten" toggle icon if automatic adjustment is not preferred by the user. Actual Behavior The screen remains at the system-defined brightness level. The user is forced to manually pull down their notification shade and increase brightness to facilitate a successful scan. Suggested Fix Brightness API Integration: Use the Android/iOS Window Manager API to set the screenBrightness parameter to 1.0 (maximum) when the ReceiveFragment or ReceiveActivity is in the foreground. Permissions: Ensure the app has the necessary manifest permissions to adjust display settings temporarily. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 2 days ago

[ECO Bounty] iopay Lack of Input Validation for Slippage Tolerance (100% Allowed)

Summary The "Set slip point" (Slippage Tolerance) input field allows users to enter and confirm a value of 100%. This is a critical edge case that should be restricted to prevent users from potentially losing their entire transaction value to MEV bots or extreme price fluctuations. Description In the Swap interface, the customization tool for "slip point" does not have a maximum threshold or a warning system for extremely high values. Setting slippage to 100% essentially means the user is willing to accept 0 tokens in return for their trade. This is highly dangerous and typically used by malicious actors (front-running/sandwich attacks) to drain user funds. Steps to Reproduce Navigate to the Swap tab in the ioPay app. Click on the slippage settings icon (usually a gear or percentage icon). Select the Customization tab under "Set slip point". Manually enter 100 into the percentage input field. Observe that the Confirm button remains active and the value is accepted. Expected Behavior The app should impose a logical limit on slippage (e.g., maximum 49% or 50%). If a user enters a high value (e.g., above 5%), a prominent warning should appear: "Your transaction may be front-run." If a user enters 100%, the Confirm button should be disabled, or a "Force Confirm" prompt with a clear explanation of the risk should be required. Actual Behavior The system accepts 100% slippage without error or high-risk warnings. The user can click "Confirm," potentially exposing them to a total loss of funds during the swap. Suggested Fix Hard Cap: Implement a hard limit on manual slippage input (e.g., max 25-50%). Dynamic UI Feedback: Change the input text color to red when slippage exceeds 5%. Confirmation Modal: If a high slippage is set, require the user to type "confirm" or "I understand the risk" before saving the setting. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 2 days ago

[ECO Bounty] iopay Missing Live Chat Support Feature

Summary The ioPay mobile application (v5.2.0) appears to be missing a Live Chat support option, which is a standard feature expected in modern crypto wallet applications for real-time user assistance. Description Upon reviewing the ioPay app interface, there is no visible Live Chat support option in the main menu or settings area. While there is a "User Feedback" option under "ioPay Settings," this does not provide the immediate, real-time assistance that a Live Chat feature would offer. For a cryptocurrency wallet handling financial transactions, the absence of instant support could lead to user frustration and potential security concerns. Steps to Reproduce Open the ioPay application Navigate to the main menu/settings screen Observe the available options under "ioPay Settings" Note that there is no "Live Chat" or "Support Chat" option available Expected Behavior A "Live Chat" or "Chat Support" option should be available in the settings menu or accessible via a floating chat icon, allowing users to: Connect with support agents in real-time Get immediate help with transaction issues Receive guidance on security concerns Resolve account-related queries promptly Actual Behavior No Live Chat option is present in the interface Only "User Feedback" is available, which typically implies a one-way communication or email-based system rather than real-time chat Users must rely on documentation or external support channels for immediate assistance Suggested Fix Implement a Live Chat widget accessible from the main menu or as a floating action button Integrate with a customer support platform (e.g., Zendesk, Intercom, or Freshdesk) Add a "Support" or "Help Center" section with Live Chat as a primary option Consider adding in-app chatbots for 24/7 basic assistance when live agents are unavailable Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 2 days ago

[ECO Bounty] ioTexScan Missing "IN" (Incoming) Transactions in Address History

Platform: IoTeXScan URL: https://iotexscan.io/address/0x5d9d12c6d996cce9b6b4aadd8d3d4f81b0465e8d Severity: High (Critical for wallet balance verification & tax reporting) Date: March 8, 2026 Reporter: User Wallet Address 0x5d9d12c6d996cce9b6b4aadd8d3d4f81b0465e8d Issue Summary: The transaction history page for address 0x5d9d...5e8d only displays OUT (outgoing) transactions. All IN (incoming) transactions are missing from the list, despite the address having received transfers (as evidenced by non-zero balance or expected receipts). This creates a false impression that the wallet only sends funds and never receives them. Steps to Reproduce: Navigate to https://iotexscan.io/address/0x5d9d12c6d996cce9b6b4aadd8d3d4f81b0465e8d Scroll to "Transactions" tab/section Observe the transaction list Issue: Only "OUT" transactions appear (send operations) Missing: All "IN" transactions (receive operations) are absent Cross-check: Verify on alternative explorer (e.g., https://iotexscout.io/) or check wallet balance to confirm incoming txs exist Expected Behavior: The transaction history should display a complete chronological list including: IN transactions: Incoming transfers, token receipts, staking rewards, airdrops OUT transactions: Sends, contract interactions, staking actions SELF transactions: Self-transfers, contract deployments Filter options: Toggle between All / IN / OUT / Token Transfers / NFTs Actual Behavior: Only OUT transactions are indexed and displayed IN transactions are completely missing from the UI No filter option to view incoming history Users cannot verify receipt of funds via explorer Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 2 days ago

[ECO Bounty] iopay Critical Price Discrepancy & Transaction Logic Failure

Critical Price Discrepancy (Swap Interface) In the "Swap" interface, the displayed USD values for assets are mathematically inconsistent and decoupled from market reality. Observation: The interface shows 28,000 IOTX valued at ~$144.06, while 0.09888 ETH is valued at ~$288.13. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 2 days ago

[ECO Bounty] mimo Exchange Missing Community & Social Media Links

Description The Mimo Exchange landing page and footer currently lack any links to official community channels or social media platforms (e.g., X/Twitter, Telegram, Discord). For a decentralized exchange (DEX), the absence of these links significantly impacts user trust and prevents users from accessing official support or community discussions. Impact Reduced Trust: Users are less likely to interact with a DeFi platform that does not provide a direct link to its social presence or community verification. Community Fragmentation: New users cannot easily find official channels, making them vulnerable to "fake" support groups or phishing scams on social media. Steps to Reproduce Navigate to mimo.exchange. Scroll to the footer of the page. Examine the header and menu options for any social icons (bird, paper plane, or discord logos). Observe that no such links or icons are present. Expected Result The website should feature a dedicated section or footer icons linking to: X (formerly Twitter): For real-time updates. Telegram/Discord: For community support and governance discussions. Medium/Blog: For technical updates and project roadmap details. Suggested Fix Integrate standard social media icons in the global footer. Add a "Community" or "Help" dropdown in the main navigation bar that includes links to these social platforms. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 3 days ago

[Eco Bounty] mimo exchange Hamburger Menu UI Clipping and Visual Feedback Failure

1. Description When clicking the hamburger menu on the right side of the header in the mimo v3 mobile interface, the menu overlay displays significant formatting and layer issues: Background Transparency: The menu background is fully transparent or dark, causing the menu text (e.g., "Swap," "Pools," "Bridge") to blend into the main app background, making it difficult to read. UI Clipping: The menu appears to be "cut off" at the top, with the "Important" notice banner overlapping or sitting awkwardly behind the first menu items. Sticky Header Conflict: The wallet address and network icons remain visible and layered incorrectly over the menu options. 2. Steps to Reproduce Open mimo v3 in the ioPay mobile browser. Click the hamburger menu icon (two horizontal lines) located in the top right corner. Observe that the menu opens but fails to provide a solid background or a clear "Close" (X) transition that is easily distinguishable from the rest of the UI. 3. Actual Result The menu opens as a transparent overlay where the menu items are barely readable against the DApp's background elements. The layout appears "broken" because the header icons and the notification banner do not clear properly when the menu is active. 4. Expected Result The menu should open as a solid, high-contrast overlay that completely covers or dims the background content to ensure readability. Navigation items should be clearly separated from header icons. ### Suggested Fixes Overlay Opacity: Increase the opacity of the.menu-overlay background to 1.0 or add a high-blur backdrop filter to separate the menu from the Swap interface. Z-Index Correction: Adjust the z-index of the navigation menu so it sits above the "Important" notice banner and the wallet/network icons. Close Button Logic: Ensure the "X" button replaces the hamburger icon clearly and has enough padding to prevent accidental clicks on the icons behind it. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 3 days ago

[Eco Bounty] ioPay Missing "Recent Transactions" or "Recommended Addresses" in Send Screen

Description The "Send" interface does not display any recommended or recently used addresses, despite the user having a significant history of transactions. The area below the "Amount" input (highlighted in the provided screenshot) remains empty. Steps to Reproduce Open the ioPay app. Ensure the account has a history of multiple outgoing transactions. Navigate to the Send screen. Observe the section below the "Amount" field. Actual Result The space remains blank. No historical data is surfaced. ### Suggested Fixes To resolve this and improve the user experience, I suggest the following implementation: Local History Caching: Implement a local cache that stores the last 5–10 unique recipient addresses. This ensures that even if the blockchain indexer is slow, the UI can instantly populate "Recent" addresses from local storage. Toggle/Tab Interface: Add a small tabbed section in that empty space labeled "Recents" and "Address Book." Frequency Algorithm: Instead of just "last sent," rank addresses by frequency. If a user sends to the same exchange or friend 10 times, that address should be pinned to the top as a "Recommended" shortcut. UI Placeholder: If there truly are no transactions, display a "No recent contacts found" message or a button to "Add from Address Book" to confirm the feature is working but empty. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 3 days ago

[Eco Bounty] Depinscan Token Prices Displaying as $0 (Missing Real-Time Price Data)

App: ioPay Version: v5.2.0 (3970) Feature: DePIN → All Map View → Token Price Tab Severity: High (Critical - Price Data Inaccuracy) Device: Android 📝 Description In the DePIN section under All Map View → Token Price tab, multiple project tokens (Tomi, ApeX, Roko Net, Drift, Gamin, etc.) display prices as $0 despite having visible market caps and activity higher in the interface. This indicates a failure to fetch or display accurate real-time token prices from price oracles/market APIs. 🔁 Steps to Reproduce Open ioPay app. Navigate to DePIN → DePIN News (or directly to DePIN dashboard). Switch to All Map View. Tap the Token Price tab. Observe prices for listed projects (e.g., Tomi, ApeX, Roko Net, etc.). ✅ Expected Result Each token should display its exact current market price (e.g., $0.00123 for Tomi) fetched from a reliable source like CoinGecko, CoinMarketCap, or ioPay's integrated oracle. Prices should update in real-time and match external market data. ❌ Actual Result All tokens show $0 (e.g., Tomi $0, ApeX $0, Roko Net $0, Drift $0, Gamin $0, Solochain $0). This is incorrect and misleads users on token valuation, especially when market caps are visible elsewhere (e.g., $3.53M+). 💡 Suggested Fix Verify Price Feed Integration: Check API connections to price providers (CoinGecko, Jupiter, etc.) for DePIN tokens. Fallback Handling: Display "Loading..." or last-known price if fetch fails, rather than defaulting to $0. Token Symbol Mapping: Ensure correct symbol-to-price API mapping for niche DePIN projects (e.g., TOMI, APEX, ROKO). Caching/Refresh: Add manual refresh button and improve caching to prevent stale $0 displays. Logging: Add error logging for failed price fetches to diagnose network/oracle issues. Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 3 days ago

[ECO Bounty] Outdated Snapshot Data & Incorrect Proposal Links on Governance Page

Issue Summary: Clicking the → arrow next to proposals (e.g., IIP-56) redirects to the general IoTeX Network page on Snapshot.org (https://snapshot.box/#/s:iotex.eth) instead of the specific proposal. Snapshot data is stale/outdated, showing mismatched vote counts, wrong proposals (e.g., IIP-40 instead of recent IIPs), and incorrect statuses compared to IoTeX Hub. Steps to Reproduce: Visit https://hub.iotex.io/governance/proposals Locate IIP-56 Deprecation of All Networks (shows "Active", 24 votes, period 03/05-04/02) Click the → arrow next to it Redirected to https://snapshot.box/#/s:iotex.eth On Snapshot: Shows IIP-40 ("Deprecate 101 Address", #937 by dev, 140 votes) as latest Mismatch: No IIP-56/55/52 visible; data not updated Expected Behavior: Arrow links to specific proposal page on Snapshot (e.g., https://snapshot.org/#/proposal/0xabc...) Snapshot data matches IoTeX Hub in real-time (votes, status, periods) Users see live, accurate voting info without discrepancies Actual Behavior: Links to generic space page (/s:iotex.eth) Snapshot shows outdated proposals (IIP-40 prominent, recent IIPs missing) Vote counts/status/periods do not sync (e.g., Hub: 24 votes Active → Snapshot: absent) Confuses users during active voting periods Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren Device & Environment: -Operating system: Android 13 -Device model: Redmi Note 10 Pro

cryptotestnet 3 days ago