Skip to content

Conversation

@masih
Copy link
Member

@masih masih commented Apr 15, 2024

Remove GenerateKey API from gpbft.Signer interface, and change the signing backend implementations to expose this capability for testing purposes only.

This change reduces the surface of exported API at the core gpbft package.

Signing test suit is refactored to use testify built-in utilities and moved out of the production scope.

The default hasher for fake signing backed is also changed to SHA-256, a built-in hasher, in favour of reducing the dependency footprint.

Fixes #154

@masih masih requested a review from Stebalien April 15, 2024 17:11
@masih masih self-assigned this Apr 15, 2024
Remove `GenerateKey` API from `gpbft.Signer` interface, and change the
signing backend implementations to expose this capability for testing
purposes only.

This change reduces the surface of exported API at the core `gpbft`
package.

Signing test suit is refactored to use testify built-in utilities and
moved out of the production scope.

The default hasher for fake signing backed is also changed to
SHA-256, a built-in hasher, in favour of reducing the dependency
footprint.

Fixes #154
@masih masih force-pushed the masih/refctr-generate-key-api branch from ab52522 to 76d9a9c Compare April 15, 2024 21:04
@masih masih enabled auto-merge (squash) April 15, 2024 21:08
@masih masih merged commit fb1c6bf into main Apr 15, 2024
@masih masih deleted the masih/refctr-generate-key-api branch April 15, 2024 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove GenerateKey from top level GPBFT interface

3 participants