Greg

@vishalchangrani is that true for the JS generated client as well? I think we should focus on JS client and anyway we should support correct formatted IDs and then also...

> @sideninja What version of Node is installed on both systems? Latest. For the x86 it might have been cpu resources issue (running in cloud you never know). For arm...

but do you have an M1?

We shouldn't change APIs just to facilitate an issue with transaction iD. As soon as I finish some work on the playground I will help you solve the transaction ID...

@sukantoraymond I don't think we need both. In any way that's a different topic, we can discuss changing the API as part of the https://github.com/onflow/flow-cli/issues/493 but again I don't think...

Yep. Let's discuss it. We plan to add new tools to the CLI soon. Can you explain what would the bootstrap involve?

Nice! It's funny how size almost 1:1 correlates with speed for this one.

I would say that once we have the service layer mocked out you can to an exact string match, since the result from the service layer will be predictable you...

> create a http backend, like ./pkg/flowkit/gateway/grpc.go I would rather refactor that to not be protocol specific as it's already abstracted in the flow go SDK as seen here: https://github.com/onflow/flow-go-sdk/tree/master/access...

> For the magic part, I meant something like this: ( it was for a smarter way to detect protocol from host, instead of query each time ) I see,...