Thanks, yeah, i think that is still not ideal but has nice properties where you can basically subscribe to different rpc calls by different method names or even parameters. Having full expressiveness of json for both request and response would be great though. Was there any discussion about this? What confuses me is wording of nip01 (“New NIPs may add new optional (or mandatory) fields and messages and features to the structures and flows described here.”).

Anyway, in comming days i will hack something together. I like the idea of having dedicated nostr rpc relay.