Agree. Hard to abstract away a 3-4 orders of magnitude latency difference. However, even the most obvious /absurd / ugly shell out to curl and hand parse result

Agree. Hard to abstract away a 3-4 orders of magnitude latency difference. However, even the most obvious /absurd / ugly shell out to curl and hand parse results like code, is going to get wrapped in a normal looking function. Maybe the solution is naming or tooling where: 1) it is easy for a developer to see if a network call exists anywhere in the stack and 2) it isn't possible to introduce a network call into an existing function without breaking contract. This could be as simple as a viral naming convention ("_rpc" suffix for example).