Publish necessary properties for external use of KZG commitment

[chiro-hiro]

This pull request was created to solve the issue that mentioned in #230

[han0110]

LGTM

[CPerezz]

Can we make getter functions instead of exposing the fields? The idea is that while we allow to retrieve this, we signal that they should not be edited.

Does it make sense?

[chiro-hiro]

Hi @han0110 and @CPerezz, thank for the reply.

I have a call with my teammate and I think they misunderstood between construction method and public properties. I changed back the accessibilities of properties to pub(crate) and add the construction instead.

[CPerezz]

LGTM.

Still not 100% convinced that this should be exposed. But anyways, don't see strong reasons to prevent it. Aside that users might get confused thinking that this is needed for anything if you want to use the crate on a normal way.