chore: track web3 v7 migration in ypricemagic (blocked on Brownie support) #1370
Description
Summary
This issue tracks the staged migration of ypricemagic from web3 v6 to web3 v7.
A prep branch has been created: web3-v7.
Current prep commit on that branch: 8662dd4ef09a673dfcd2c28b201c4acb6a1241a5.
Rationale
We need to remove legacy web3 v6 compatibility paths and move to web3 v7-native interfaces, but rollout is currently blocked by Brownie still targeting web3 v6 in the active dependency chain.
Details
What has already been adapted on web3-v7
- Removed v6/v7 split import path for PoA middleware in
y/utils/middleware.py. - Switched to v7-style middleware construction for getCode cache middleware (
Web3Middleware+ middleware-builder shape).
Migration work to complete in this repo
- Audit all web3 API touchpoints for v7-only compatibility:
- middleware APIs (
middleware_onion.add/injectexpectations) - attribute/property changes (for example, client/version access patterns)
- exception and response shape differences
- Add focused tests for each migrated call path (middleware setup, request execution, startup import path).
- Decide and implement dependency strategy:
- either full web3 v7 pinning for this branch
- or isolated compatibility wrappers if temporary dual-track is still needed during transition
- Update developer docs/runbooks to explicitly state web3 v7 branch expectations and current blocker.
External blocker
eth-browniecurrently operates on the web3 v6 stack in our active setup.- Because of that, this migration branch is not rollout-ready until Brownie supports web3 v7 (or we decouple critical runtime paths from Brownie).
Exit criteria for rollout readiness
- Brownie-side web3 v7 support is available and validated in our runtime.
ypricemagictests pass in the v7-target environment.- Remaining v6-specific behavior paths are removed or intentionally documented as temporary.