Clafiry binary format of the public keys #64

New issue

Open

opened 2025-12-28 18:12:21 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:12:21 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Apr 7, 2022).

There are several fields of "binary public key" type, for example:

session_key field of the session.SessionToken message
key field in refs.Signature message

In current implementation the format is not specified, which on the one hand gives some flexibility to client applications, on the other hand makes decoding undefined.

I propose to clarify binary format of these fields (in Signature message we can specify per-scheme format).

Originally created by @cthulhu-rider on GitHub (Apr 7, 2022). There are several fields of "binary public key" type, for example: - [session_key](https://github.com/nspcc-dev/neofs-api/blob/431335054c3bd2fcff52226e04175b443bcb8a1e/refs/types.proto#L105) field of the `session.SessionToken` message - [key](https://github.com/nspcc-dev/neofs-api/blob/431335054c3bd2fcff52226e04175b443bcb8a1e/refs/types.proto#L105) field in `refs.Signature` message In current implementation the format is not specified, which on the one hand gives some flexibility to client applications, on the other hand makes decoding undefined. I propose to clarify binary format of these fields (in `Signature` message we can specify per-`scheme` format).