Vishal
Vishal
Closing this since this has now been implemented
Is the ask here to provide the gRPC [getNetworkParameters](https://developers.flow.com/nodes/access-api#getnetworkparameters) call on the REST API?
QN confirmed they can do for the public access nodes using their middleware. The have the capability to shutdown the `SendTransaction` API while allowing traffic for the other APIs.
This PR https://github.com/onflow/flow-go/pull/5764 fixes the issue of EN1 missing events. Once the fix for that is rolled out, the client should not receive an error since EN1 will have all...
> * Use any EN with a receipt > * Use any preferred node not already selected > * Use any EN not already selected shouldn't the order be, 1....
> * Use any EN with a receipt > * Use any preferred node not already selected > * Use any EN not already selected You are right - I...
Streaming may be a better solution that pagination (as discussed earlier in the post mortem meeting)
Mainnet ran into this issue again today for transaction:`03aa46047cdadfcf7ee23ee86cd53064e05f8b5f8a6f570e9f53b2744eddbee4` error: code = Internal desc = failed to retrieve result from execution node: 3 errors occurred: * rpc error: code =...
Meeting notes from Today's discussion Short term solution - Will this be a problem in the upcoming multi-sign? - `rpc error: code = ResourceExhausted desc = grpc: trying to send...