Leonid Tyurin

Sometimes, the following errors also pop-up ``` invalid argument ,0x9eebec6c5157bee13b451b1dfe1ee2cb40846323,0x8ce94b88cb2f21b59a690d08a9e7cb03d271c3fc,0x59c40304e8a428bf1d17f03a6ae84b635964db19 ``` ``` invalid argument 0xdd6e31a046b828cbbafb939c2a394629aff8bbdc,0xfcc6e37d254975d943113c0af89b60a41cf5ecbd,,0x8f561f022d59ee47399b33f693a892a911fa169c,0xb265461dde63914e4eb7f4c2b166fbf92e238b94 ``` In the first case the first address is missing (query starts with a comma)...

I suggest a new endpoint similar to `/api/v1/{chain_id}/addresses/{address}`, but protocol-centric. For example, `/api/v1/addresses/{address}?protocols={comma_sep_protocols}`. Also, a protocol-based variant of `/api/v1/{chain_id}/addresses:lookup` endpoint would be nice to have.

We should add a protocol-centric version of `/domains:lookup` endpoint as well

> Base64 encoding increases data size in bytes I guess it is possible to base64 encode the token as a structured array instead of an object. For example for object...