This check is here, because of issue#3490, that was happening due to different
messages' order (received from status go). We were emitting always a message on
index 0, what in some cases was not the reply message (doesn't contain "responseTo"
value). This should be handled in status-go but since that part is used by mobile
also and it is working for them, change is applied here.
Fixes: #3490
* refactor: move eth logic out of libstatus wrapper
* move signing phrases out of status go wrapper (libstatus)
* move logic related methods out of libstatus
move logic related methods out of libstatus
move logic related methods out of libstatus
fix sorting
Deserialization was attempting to deserialize via snake case, however the `json` definitions in status-go are using camel case.
The odd thing here is that when *serializing*, status-go expects the fields to be snake cased. Ideally, these should be consistent so that we can use both `Json.encode` and `Json.decode`.
