Pull Request: Add Arbitrum One Plugin

[dudkitt]

Summary

This pull request introduces a new plugin for the Arbitrum One network.
It enables ZenMoney to retrieve balances and transactions for one or multiple wallet addresses using the Arbiscan API.
Features

Integration with the Arbiscan API

Fetching:

    Native ETH balance

    ERC‑20 token balances

    Native transactions (txlist)

    ERC‑20 token transfers (tokentx)

Multi‑address support:

    preferences.account accepts one or several addresses separated by commas

    Balances and transactions are aggregated across all provided addresses

Conversion of API responses into ZenMoney account and transaction formats

Type definitions for API responses and plugin preferences

Implementation Notes

The API client includes request queueing to avoid rate‑limit issues

Pagination and block‑based filtering are handled in fetchTxPages

Native and token transactions are normalized before conversion

The plugin follows the structure and conventions of existing ZenPlugins

Testing

Verified with multiple real Arbitrum addresses

Confirmed correct behavior for:

    Native ETH balances

    ERC‑20 token balances

    Native transactions

    Token transfers

    Empty transaction histories

    Multiple addresses

Ensured compatibility with ZenMoney’s expected data format

Why This Matters

Arbitrum One is one of the most widely used L2 networks.
This plugin allows ZenMoney users to track their assets and activity on Arbitrum directly within the app.

[skvav]

@dudkitt Hi! Thanks for your contribution. Please fix the code to pass all tests.

[dudkitt]

Runtime fix for Arbitrum One plugin:

This patch fixes the runtime error "cannot convert BigInt to number" by coercing bigint/string/number inputs in the converter. It also normalizes ETH/token amounts to micro-units (µ = 1e-6), fixes wei→ETH conversion to preserve fractional fees, supports both micro characters (μ/µ), and includes preferences.xml translation to English plus minor lint fixes.

Verification: ran yarn test arbitrum_one locally — 5 suites, 14 tests passed. Branch was rebased onto upstream/master and force-pushed to update this PR.

[dudkitt]

@dudkitt Hi! Thanks for your contribution. Please fix the code to pass all tests.

@skvav исправлены ошибки, подготовлено к повторному тесту.

[skvav]

@dudkitt It looks like you’re using https://api.etherscan.io/v2/api as the main api. We already have an Etherscan plugin (https://github.com/zenmoney/ZenPlugins/tree/master/src/plugins/etherscan
) that works with the same API.

Could you please consider extending the existing etherscan plugin to support your target chain instead of creating a separate implementation?

[dudkitt]

Could you please consider extending the existing etherscan plugin to support your target chain instead of creating a separate implementation?

Adding the Arbitrum One network to the existing Etherscan plugin implementation was my "Plan A," which I spent some time developing. Unfortunately, my technical skills weren't sufficient to integrate support for another network without completely redesigning the Etherscan plugin. There were some technical limitations related to the Etherscan plugin being originally written for the older APIv1, which only supported Ethereum. Additionally, we're limited by the free Etherscan API plan.

If needed, I can try integrating the new network into the old plugin again.

[skvav]

@dudkitt Maybe the previous developers of the Etherscan plugin can help: @dzhiriki @stek29 @Cr0WD