Determine what subset of zcashd wallet functionality will be required by users in a replacement wallet (independent of how it is accessed)

[nuttycom]

• what are the requirements from the mining community?
• what are the requirements from exchanges?
• what are the requirements for wallet data migration?

[str4d]

@hhanh00 posted this list of capabilities on the forum (most of which map to existing JSON-RPC methods, but the relevance to this issue is the functionality):

From the point of view of an dex dev, I’d like to mention the API/features that I’ve been relying on in zcashd:

• regnet with custom activation heights
• generate
• list accounts
• get new account
• get address for account
• get utxos
• get balance
• import address
• shield coinbase
• z send many
• get block count
• get block hash
• get block
• invalidate block
• reconsider block
• get transaction (with tx input address.& amount, insightexplorer=1)
• get raw transaction
• get raw mempool
• send raw transaction

[daira]

Some of the considerations in zcash/zcash#6690 might be relevant.