Control API passes addresses in stringified format #2980
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I realize we have to parse addresses in control API just because we have string representations being used in the protocol.
Describe the solution you'd like
Use good old bytes, it's protobuf anyway. 32 for OID. 32 for CID. 64 for address.
Describe alternatives you've considered
Keeping as is, it works with some slight overhead.