Subtensor read compatibility reminders for validator helper teams
Some post-upgrade reviews focus less on staking behavior and more on whether a validator helper still reads the network cleanly after an SDK bump. This page looks at the read side of the transition, especially when older code assumes get_subnets semantics that no longer line up with the supported Subtensor surface.
When this note is relevant
Use this page when the helper still boots but subnet inspection or lookup helpers need a compatibility review. The point is to document read-path expectations and outline what belongs in a broader service migration checklist, not to describe every runtime or staking concern tied to the release.
Review steps
- Map every direct
get_subnetscall to the current abstraction used by the service. - Check whether helper wrappers normalize network reads in one place.
- Run a smoke test that covers startup plus one successful subnet discovery path.
- Record any read-side assumptions that should move into migration notes.
Scope boundary
A compatibility memo like this is intentionally narrower than a full operational migration guide. It addresses read-path expectations and migration bookkeeping, while leaving wallet flow, typed amounts, and broader adapter restructuring to separate notes.