Deniz Mert Edincik

it seems like there is also 140M registers ( ~ 4 per account ) used by flow-go, ( account status, keys etc ) maybe it can be good to consider...

I think main problem here is: ``` .borrow()! .balance ``` and ``` .borrow() !.balance ``` technically different things but they result in same outcome. I think `!.` operator is unnecessary....

@peterargue thanks a lot for this, btw do we have archive nodes still ? last time I tried to work on this I was failing at that. Also if someone...

I think we need to fix also register requests part, I messed up there before because of flow-archive versioning problems. ( I can make a PR for it, or contribute...

ok I updated https://github.com/onflow/flow-emulator/pull/433 with required changes, which required a PR on flow-archive ( for conflicting go versions ) https://github.com/onflow/flow-archive/pull/143

This feels a bit wrong. ( according to https://github.com/onflow/flow-go-sdk/tree/master/access ) > Each implementation (currently grpc and http) include the following parts: Base Client is the client that implements the client...

seems like a Chrome issue with getting projects ( it is failing for me also when deploying contract )

I think 7702 here is the best way for compatibility. I don't believe we need multiple coa using single eoa. ( but below logic also allows that ) I am...

I think the best way would be to wrap those resources into something. LegacyResource resource, LegacyType type, etc.

More I learn about the evm, I am more convinced that COA was a design flaw tbh. ( or hype directed development ) Any chance you can share with me...