Huge performance degradation in dApp and connected wallets due to excessive `eth_chainId` requests

[superKalo]

Bug Description

The dApp floods connected wallets with redundant eth_chainId requests (hundreds to thousands per interaction). This causes severe slowdowns and can crash wallet background/service workers due to request queue overload.

While testing, the app was observed sending ~500 requests/sec and up to 2200+ eth_chainId calls after entering a swap amount.

Steps to Reproduce

1. Open https://dapp.quickswap.exchange
2. Connect Ambire wallet (but observed with multiple wallets).
3. Enter a token amount for swap (example: POL).
4. Observe RPC traffic / wallet logs.
   

Expected Behavior
The dApp should not spam eth_chainId requests.
A single request (or occasional checks) should be enough, similar to behavior seen in other apps.

Additional Context

• The issue is reproducible across wallets (Ambire, MetaMask, Rabby).
• Requests stop only after wallet responses arrive.
• This creates unnecessary load and slows wallet ↔ dApp communication during transactions.
• In Ambire, this originally caused service worker crashes due to excessive promise queuing (fix applied wallet-side in our v5.38.4 onward as mitigation).
• Root cause appears to be on the dApp side due to redundant chainId polling.

Greetings from the Ambire team ✊

[sonytooo]

You can paste this script in the dApps console before connecting to easily test and monitor the number of requests made to the wallet:

(function() {
    if (!window.rabby) {
        console.warn("Rabby provider (window.rabby) not detected.");
        return;
    }

    const originalRequest = window.rabby.request;
    const methodCounts = {};

    // Override the request method
    window.rabby.request = async function(args) {
        const { method, params } = args;

        // Increment or initialize the count for this method
        methodCounts[method] = (methodCounts[method] || 0) + 1;

        console.group(`[Rabby Intercept] ${method} (#${methodCounts[method]})`);
        console.log("Parameters:", params);
        console.log("Full Call History:", methodCounts);
        console.groupEnd();

        try {
            return await originalRequest.apply(this, [args]);
        } catch (error) {
            console.error(`[Rabby Error] ${method}:`, error);
            throw error;
        }
    };
    console.log("Rabby request tracker active. Counting method calls...");
})();

you can also replace window.rabby with window.ambire if you prefer to test the performance with the Ambire Wallet