[Ethereum] Detecting `accountsChanged` and `chainChanged` with ethersjs

I had the same issue and using once for events filtering also didn't work. I had to stop provider from polling events.

You can do it like this:

bytesContract.provider.polling = false

This is what ethers documentation says about it

prototype.polling mutable

If the provider is currently polling because it is actively watching for events. This may be set to enable/disable polling temporarily or disabled permanently to allow a node process to exit.

Ethers Provider Polling Documentation

Worked for me. New provider has polling set to false and only when you filter for events or call transactions it will start polling.

From the Yellow paper documentation of the LOG opcodes the format is:

• stack[0] pointer memory
• stack[1] size memory
• stack[2] first topic
• stack[3] second topic & so on

From your capture the stack is reversed

  stack: [
    '0xd0e30db0',
    '0x3d2',
    '0x7a250d5630b4cf539739df2c5dacb4c659f2488d',
    '0xe1fffcc4923d04b559f4d29a8bfc6cda04eb5b0d3c460751c2402c5c5cc9109c',
    '0x20',
    '0x60'
  ],

• 0x60 points to 0000000000000000000000000000000000000000000000000de0b6b3a7640000
• 0x20 length = 32 bytes
• first topic 0xe1fffcc4923d04b559f4d29a8bfc6cda04eb5b0d3c460751c2402c5c5cc9109c
• second topic 0x7a250d5630b4cf539739df2c5dacb4c659f2488d (it will be padded to 32 bytes

If I'm not wrong memory 0x0-0x3f are scratch memory used by some solidity operations.

Memory at 0x40-0x5f is a pointer to free memory. In this case free memory starts at 0x60.

Also in newer solc versions memory address at 0x60-0x7f is zeroed on purpose, and the free memory starts at 0x80.

I think you are correct that accessing current contract you have to track those opcodes.