Fix the blob encoding type

[nazarhussain]

The blobs returned from the beacon-apis are the raw bytes not encoded into ssz.

Mentioning it as SSZ encoded cause confusion to decode the output from the API e.g. ssz.Blob.decode(api_response) which will not match with the actual blobs.

Some reference:

https://github.com/ChainSafe/lodestar/blob/ae984f0f6079f78c2445f36ae2ac09c9e868197e/packages/types/src/deneb/types.ts#L8

[nazarhussain]

@g11tech Please take a look at this small change.

[g11tech]

lgtm

[nflaig]

Mentioning it as SSZ encoded cause confusion to decode the output from the API e.g. ssz.Blob.decode(api_response) which will not match with the actual blobs.

What exactly are you trying to do? If you wanna decode the raw hex-encoded blob you can do ssz.Blob.fromJson()

[nflaig]

This is the hex encoded value sent over the wire, the blob is serialized using the ByteVector type, maybe we could slightly rephrase it

Edit: I think that "SSZ-encoded" is meant to refer to JSON mapping in the ssz spec, i.e. how the blob should be encoded over the wire in a JSON response.

[nazarhussain]

It's raw bytes which was sent from the sender of EIP4844 transaction. If we considered it SSZ-Serialized, one will try to deserialize to get the actual blob, which is not the case here.

The raw bytes sent in transaction are the exact bytes returned over the API, where this description is been used.