Marek

> I'm not sure why the tests were hanging Resolved in [3a66152](https://github.com/ZcashFoundation/zebra/pull/8425/commits/3a66152d9e21c980ecace1a1ce55ea37bfd78dc9).

@arya2, what issue is this PR supposed to fix?

@mpguerra could you add the resources you used to compose the lists of the RPCs?

@conradoplg I noticed you tried running https://github.com/nighthawk-apps/zcash-explorer locally. It should use this tool https://github.com/nighthawk-apps/zcashex as a middleware between the explorer and full node. It looks like it should be sufficient...

(So I think you don't need to list the RPCs manually.)

I extracted the RPCs from https://github.com/nighthawk-apps/zcashex/blob/main/lib/zcashex.ex: - getblockchaininfo - getmempoolinfo - gettxoutsetinfo - getinfo - getmemoryinfo - getmininginfo - getnetworkinfo - getpeerinfo - getbestblockhash - getblockcount - getdifficulty - getblock...

Here's a list of RPCs from Conrado which splits them according to what Zebra does and doesn't implement: Zebra has: getblockchaininfo getinfo getmininginfo getpeerinfo getbestblockhash getblockcount getdifficulty getblock getblocksubsidy getnetworksolps...

Yes, I would like to look into this.

The conclusion is that we can read the state similarly to how we're going to do it in the scanner.

I'm getting the same error on Framework 13 AMD.