Consider implementing DSProof subscription on non-transaction states.

[monsterbitar]

I would like to have blockchain.address.dsproof.subscribe, blockchain.scripthash.dsproof.subscribe and blockchain.mempool.dsproof.subscribe.

The address/scripthash level would monitor for DSP on transactions relating to that specific address/scripthash. I can use this to resolve an edge-case while doing clustering of multiple servers and potentially also to reduce the number of subscriptions I would be tracking.

The mempool level would monitor for all DSPs, regardless of what transaction/address etc, and would be useful for tools that present information about the blockchain or bitcoin cash network, rather than working with specific addresses or wallets.