failed to decrypt rmb response in the dashboard

[Omarabdul3ziz]

with both rmb clients (ts,go) connections from specific twin (ops wallet) to specific node (1,10,...) failed.

ashraf/hanafy suspect that the pk of the caller twin was corrupted at sometime and called the node, which cached this pk and it will never invalidate it, so after the pk fixed again the node still encrypt the response with the corrupted pk. and so we can't decrypt the response in the client side.

• reproduce and validate that it is the invalid cache
• could the pk change? should we invalidate?

[Omarabdul3ziz]

debugging this we faced two other issues:

• some nodes gives an error send on closed channel when calling from sdk v0.16.0 works fine with v0.15.18
• there is a conflict in the dep go-subkey between the sdk repo and the chain client. Using v1 and v2.

I will open separate issues for both problems

[Omarabdul3ziz]

• rmb call panics on some nodes on mainnet #1291
• dependency conflict in go-subkey versions #1290