Feature Requests

Currently only blockscout/blockscout provide arm64 image, others like blockscout/frontend does not have any arm64 images. Would you please also provide arm64 docker images for all the images? Thanks

Objective: Enhance the Block Explorer application by introducing the capability to configure and utilize multiple RPC (Remote Procedure Call) endpoints simultaneously. This feature aims to address potential limitations, such as API rate limits and downtime, by allowing parallel requests to different RPC servers. Additionally, it provides a mechanism for automatic failover and backup in the event of an RPC server becoming unavailable. Proposed Features: 1. Multi-RPC Configuration: - Allow users to set up and configure multiple RPC endpoints within the Block Explorer application. - Provide a user-friendly interface for managing and prioritizing these RPC servers. 2. Parallel Request Handling: - Implement the ability to send requests simultaneously to multiple configured RPC servers. - Introduce intelligent load balancing to distribute queries efficiently among the specified RPC endpoints. 3. Automatic Failover: - Detect and handle RPC server failures in real-time. - Implement an automatic failover mechanism to redirect requests to available RPC servers when one or more become unreachable. 4. Backup RPC: - Allow users to designate certain RPC servers as backup options. - When a primary RPC server is down, seamlessly switch to a backup RPC to ensure continuous Block Explorer functionality. 5. Status Monitoring: - Provide a dashboard or status page to monitor the health and availability of configured RPC servers. - Enable notifications or alerts for users/administrators when an RPC server is experiencing issues. 6. Expected Benefits: Improved overall reliability and uptime of the Block Explorer application. Mitigation of potential API rate limit issues through parallel request handling. Enhanced fault tolerance with automatic failover and backup RPC functionality. Additional Information: Consideration should be given to the implementation details, potential user configurations, and the impact on application performance. Collaboration with the community for testing and feedback is encouraged to ensure the success of this feature.

add gas tracker with table high and low gas history

Currently, Blockscout does not provide a way to distinguish between L2 and L3 rollups in its UI and metrics. Many teams deploying rollups, would benefit from this distinction to ensure accurate labeling and a better UX. Feature Request: Add a way to classify rollups as either L2 or L3. Update relevant UI elements and metrics that currently use "L1/L2" to support "L2/L3" where applicable.

Enable a CSV file to be downloaded for all transaction history to assist with tax returns

Details: Currently, the Blockscout frontend is available only in English, which limits usability for non-English speaking users and for networks targeting global audiences. Implementing internationalization would significantly improve accessibility and adoption, especially for chains targeting multilingual communities. Use cases and benefits: Enhances user experience for international users. Improves accessibility and inclusion. Helps chains localize their user interfaces for specific markets (e.g., LATAM, Asia, EU). Enables network operators to present Blockscout as a fully localized explorer. Priority: Medium to High — depends on target user demographics, but very valuable for global adoption.

We're having trouble to place the frontend behind a reverse proxy, in a way that we can redirect from the proxy to different Blockscout deployments. We're using paths (e.g. /blockscout-01 ) to do this redirection, which the frontend doesn't like because it will return a hardcoded link based in / (e.g. <hostname>/assets/(...) , instead of <hostname>/blockscout-01/assets/(...) ) with no possibility to change it. Is there a way we're missing to do this, or is the frontend not capable of doing this at the moment? And if that's the case, is it a feature you feel you want to add? Thanks in advance!

Requesting support explorer.inkonchain to display Uniswap V3 Factory contract addresses deployed on Ink by Relay Protocol/Reservoir Tools. https://gov.uniswap.org/t/rfc-deploy-uniswap-v3-on-ink/25080 Tokens deployed using the V3 NPM address do not show up on https://explorer.inkonchain.com/pools?query=0x87b1bfd2f6d737c416c515de9038d307456e961b and therefore are not recognized anywhere.

make the pfp wallet with nft we got from testnet, or buying, it make character about their wallet

Currently, Blockscout supports Solidity, Vyper and Styus contracts. I would like to add support for Huff contracts. The verification process would be very similar to any other. One might argue that Huff is only slightly more readable than the bytecode. While that may be true, having named constants, macros and jump labels as well as comments in the code can be a significant win for readability of Huff code bases