Hey everyone, I have been testing custom automated execution scripts to help monitor Balancer pool states and simulate rebalancing triggers in a local testbed, but I keep encountering consistent provider injection errors. Whenever the execution environment hooks into the browser session, the injected Web3 provider seems to disconnect or return intermittent RPC timeout errors before the contract calls can be validated.
For instance, while inspecting how custom environments handle memory calls—taking this setup as an example—the local sandbox appears to suppress the window.ethereum events entirely. Has anyone here resolved similar hook conflicts when building test scripts for Balancer SDK integration, or is there a safer standard way to handle headless transaction signing without running into provider masking issues?