Thesimple_cache_middleware is probably too aggressive (no cache expiry) and will affect freshness of queried prices etc.

Perhaps look into some of the more sophisticated caching methods? Or we might just want to inform users how to do this themselves in the docs by constructing a custom web3 with a caching layer of choice.

Edit: It seems you can provide arpc_whitelist which could safely have thechainID RPC call in it, that would be an ideal solution!

good call@ErikBjare , adding changes

added changes, looking for any commentary

Codecov Report

Base:84.56% // Head:84.13% // Decreases project coverage by-0.42%⚠️

Coverage data is based on head(bd1f168) compared to base(ff26afb).
Patch coverage: 83.33% of modified lines in pull request are covered.

@@            Coverage Diff             @@##           master     #276      +/-   ##==========================================- Coverage   84.56%   84.13%   -0.43%==========================================  Files          10       10                Lines        1030     1040      +10     ==========================================+ Hits          871      875       +4- Misses        159      165       +6

☔ View full report at Codecov.
📢 Do you have feedback about the report comment?Let us know in this issue.

Thanks for this@PawlowskiAdrian :)